Introduction

Mobile API is a service for delivering pre-rendered SMS/MMS/RCS messages to mobile subscribers and for receiving and handling responses from those subscribers.

Mobile API is provided as a RESTful API with JSON payloads.

Mobile API uses webhooks (HTTP callbacks) to send customers critical data, like mobile-originated messages (MOs), delivery receipts (DLRs), and opt-outs as they are received.

RCS Overview: Rich Communication Services (RCS) is an IP-based messaging service accessible to mobile phone users through mobile operator networks. It facilitates both Person-to-Person (P2P) and Application-to-Person (A2P) communication. RCS enhances user communication experiences by offering dynamic features and interactivity. It empowers users with advanced capabilities and streamlines interactions. This service revolutionizes conversational engagement, enabling seamless connections with businesses and services.

Please contact your account manager for RCS set up instructions.

Division of responsibilities

The sending platform is responsible for:

• Forming the message completely.

• Determining the content and the recipient.

• Configuring a web service to respond to delivery receipt (DLR) events, to acknowledge receipt or failure to send.

• Configuring a web service to respond to mobile-originated (MO) events, to handle subscriber responses.

• Configuring a web service to respond to opt-out events, to honor subscriber intent.

Mobile API is responsible for:

• Ensuring timely and reliable delivery.

• Recording message delivery.

• Recording delivery status.

• Receiving mobile-originated (MO) SMS/MMS messages and forwarding them to the sending platform.

• Responding to a STOP keyword from a subscriber to record their opting out and forwarding these opt-out events to the sending platform.

Environments

We provide complete and separate environments for serving the US and North America market and for the UK and EU markets for GDPR data locality compliance.

Your accounts and resources will be hosted in one of the following environments as appropriate.

Access to the Swagger documentation is available as follows: