Skip to main content
The RCS API creates and fetches templates, sends messages, and reports what happened to each one. Everything is a JSON request over HTTPS, authenticated with your OneXtel API key, so it fits whatever your campaigns are already triggered from. Start by copying your API key from the portal. The endpoints below are the whole surface: templates, sends, and the callbacks that carry delivery status back.

Authentication

Every request is authenticated with your API key passed in the apikey request header:
JSON endpoints also require:

Base URL

Endpoints

Failures fall into two layers: OneXtel API validation errors are listed under Send messages, and errors raised downstream by the recipient’s operator are listed under RCS operator error codes.
The RCS Send Message API and Fetch Template API share the same endpoints as the other OneXtel channels (/oapi/send_sms, /oapi/templates/fetch). The channel is determined by the request body: RCS messages are wrapped in an rcs array, and template fetches set "channel": "RCS".

Message types

Every RCS message is classified with a messageType of Promotional, Transactional, or OTP. You can send two kinds of message bodies through the Send Message API:

Response format

The Send Message API returns an array with one result object per message:
string
Unique identifier for the submitted message. Use it to correlate delivery reports.
integer
Result code. 200 indicates the message was accepted.
string
Result status, e.g. success.