Introduction

The Mobility Services APIs are built the cloud way, on the Cisco Mobility Services platform. Mobility Services lets you enhance and build products on top of modern APIs that give access to the subscriber's telco data. This documentation contains multiple APIs for Mobility Services. Using OAuth 2.0 the API platform lets you access individual subscriber's calling, SMS/MMS, data, roaming, and more.

Note: Currently only the SMS API is present, but expect more in the near future!

Use Cases

Using these APIs, you can build products that:

  • Monitor and analyze subscriber behavior
  • Forward SMS and call history to other services, like a CRM or email
  • Summarize voicemail messages and send them to yourself as SMS or email
  • Provision subscriber services, like call forwarding or voicemail

And much more. The APIs are built to be flexible and scalable, so you can build the product you want.

Developer Portal

By visiting Developer portal, you may create your product and corresponding OAuth 2.0 clients. You will also be able to add additional information such as contact details and product description.

Our APIs Are Built With gRPC

We had to build a high-performance, scalable, and efficient client-server architecture, and after exploring various options, we landed on gRPC. One of the reasons we chose gRPC is its use of a binary protocol for communication between the client and server, which results in improved performance compared to a text-based alternative, for example, REST.

Another key benefit of gRPC is its simple service definition, which is defined using the Protocol Buffers language. This makes it easy to define and maintain the contract between the client and server, allowing us to quickly and easily develop and deploy our APIs and services.

We also appreciate that with gRPC you can generate client libraries for multiple programming languages based on the service definition. This makes it easier for our teams and partners to consume our APIs in their preferred languages, saving everyone time and effort. Currently C++, Java, Python, Go, Rust, C# / .NET, Kotlin, Node and more are supported. A full list of currently supported languages is available under "Supported languages" on the gRPC documentation page.

Overall, we are using gRPC because of its great performance, simple service definition, cross-language support, and type safety. We believe that these benefits will help us deliver high-quality APIs with a great developer experience to our partners.