The sender object
The template object
Endpoints
From creation to sending
1
Create the sender
Call
POST /senders with provider, senderName and the profile recipients will see. The sender starts as pending.2
Wait for launch
The RCS platform and the carriers review the sender. Poll
GET /senders/{id}/status, which asks the platform for the current state and stores it.3
Send RCS
Once the sender is live, call
POST /messages with channel: rcs and the sender’s senderName as from.Stored and refreshed status
GET /senders, GET /senders/{id} and the template reads return the status stored on your account. The two /status endpoints ask the RCS platform for the current state, store it and return the updated object. Poll a /status endpoint while you wait for a launch or an approval, and use the plain reads everywhere else.
Fixed and editable fields
provider, senderName and hostingRegion are set when you create the sender and cannot be changed. Every other profile field can be updated with PUT /senders/{id}; send only the fields you want to change. Template type and content are passed to the RCS platform unchanged, so use the shapes the platform defines for the type you choose.
Pagination
GET /senders and GET /senders/{senderId}/templates take limit (1 to 100, default 20) and offset (default 0). Both return a bare JSON array with no total count; an empty array means you have reached the end.
Example
Refresh a sender’s launch status:cURL
Response
Related
- RCS senders guide - designing the profile and walking a sender through review.
- RCS channel - sending rich messages, suggestions and SMS failover.
- Send a message - the endpoint you send RCS through.
- RCS reachability - check whether a number can receive RCS from your sender.
- Errors - error responses and how to handle them.