Send SMS

Send a message to a subscriber of your service: a notification, a confirmation, a piece of content.

POST /api/sp/v1/dcb/sms

What to know before you use it

Messages are not split. One request is one message and one charge; anything longer than a single part is refused rather than divided. See Send an SMS.

Three separate budgets can refuse a send: the subscriber's daily content allowance, the short code's own allowance, and the service's permitted days of the week. All three exist to stop a runaway integration spending a subscriber's balance or a short code's capacity.

Legacy field names are refused rather than ignored. If you are migrating, msg and alphanumeric will fail validation on purpose.

Delivery is not the same as acceptance. A success means we accepted the message for sending. What happened to it afterwards reaches you through DataSync.