Mobile Message API

This article introduces our Mobile Messa...

This article introduces our Mobile Message API. Below, we explain what it is, why it was developed, who it is for and how it simplifies messaging for our customers.

If you are already using another API of ours, there is no need to worry: We are not shutting down previous APIs – they will remain available as always.

1. What is the Mobile Message API?

We’ve given this API the name Mobile Mes...

We’ve given this API the name Mobile Message API as it is a solution for our customers focusing on sending messages to global mobile phone numbers identified by MSISDN.

The API is GatewayAPI’s latest REST API, designed to streamline and simplify messaging to phone numbers, starting with SMS and later expanding to Rich Communication Services (RCS) for Business (RBM). It removes the need to deal with technical details like message class, encoding and other complexities of SMS protocols.

2. Why the new API?

Our Mobile Message API was developed bas...

Our Mobile Message API was developed based on our company’s values where one key value is simplicity. It only operates with two message types: Standard SMS and Urgent SMS. It is also future-proof, as it is easily upgraded to RCS/RBM when available without needing major integration changes.

3. Who is it for?

Our Mobile Message API is designed for p...

Our Mobile Message API is designed for postpaid customers, as its pricing model aligns with this type of setup. Postpaid customers benefit from a flexible solution without needing to worry about the specifics of cost or delivery methods (e.g. SMS vs. RCS/RBM). Basically, with this API more of the technical details like message class and encoding are handled automatically and the price automatically adjusts based on these factors.

4. Is it suitable for everyone?

This API is not yet recommended for all ...

This API is not yet recommended for all new customers at this time, as we are still tweaking it, and as described above, it is only suitable for postpaid customers. However, both new and existing customers are welcome to explore its potential, and we can already promise that the Mobile Message API will be one of our main recommendations for which API to use in GatewayAPI in the near future.

5. Why choose the Mobile Message API?

The Mobile Message API represents the fu...

The Mobile Message API represents the future of GatewayAPI. It simplifies integration by requiring only one setup that can evolve over time as new technologies like RCS/RBM become available.

6. Additional information

For more details, check our documentatio...

For more details, check our documentation here: https://gatewayapi.com/docs/message/overview/

7. Questions?

If you have any questions or want more i...

If you have any questions or want more information about the Mobile Message API, feel free to reach out to our support team or check back in the Help Center for updates.

on this page