Skip to main content

Response

200 with status: "pending". Delivery is asynchronous.
Poll GET /v1/sms/{id} or wait for sms.sent / sms.delivered / sms.failed / sms.blocked. Status path: pending → sent → delivered, or failed, or blocked. If no delivery report arrives within 72 hours the status becomes unconfirmed: delivery is not confirmed and the credit stays. A later report can still move it to delivered or failed. The GET response also carries a timeline of each hop with a reason and a refund flag; see Delivery timeline.

Sender ID

New workspaces send transactional SMS under their own approved sender ID. If the destination country offers custom sender IDs and the workspace has no approved name there, the send is refused before any charge:
The status is 422. Request a sender ID from the dashboard; see Sender IDs. OTP sends are not affected. Existing workspaces keep their current setup.

OTP bodies

OTP messages are composed by Robase (workspace language, or language on the send). You do not pass a message on POST /v1/otp/send. See message text.

Not in this API

There is no template_id, no scheduled send, and no /v1/sms/batch. Loop with idempotency keys if you need many destinations.