REST Notification SMS
- Andrew Hill (Deactivated)
- Jason Andrew
- Mickey Bushman
Resource URL Summary
Send an SMS-based notification
POST /up/v5/bns/sms
HTTP Headers
This API uses custom HTTP Headers:
| Header | Type | Required? | Description |
|---|---|---|---|
Authorization | string | Yes | The Authorization header for this API is the same as for the REST Integration Standard HTTP Headers. |
Content-Type | string | Yes | The |
To | string | Yes | The phone number that the SMS-based notification should be sent to, in E.164 format. |
From | string | Yes | Typically, this is the phone number that the SMS-based notification should be sent from, in E.164 format. This number must be provided by or ported to the underly SMS Messaging Provider. From A short code or unique Sender ID can also be used provided by the SMS Messaging Provider. |
API Specific Parameters
This API does not have any API specific parameters.
API Specifics
Send an SMS-based notification
This REST API will send an SMS notification, based on the details provided in the HTTP Headers and Body.
URL
POST /up/v5/bns/sms
HTTP Request Body
This REST API requires a body, limited to 1600 characters, containing the text-based content for the body of the SMS notification.
HTTP Response
Success
On success, an HTTP response code of 200 will be returned.
Error
Otherwise, on error, the API will:
- Return an HTTP response code of 400, if the request was invalid;
- Return an HTTP response code of 401, if the request was not authorized; or
- Return an HTTP response code of 500, if something else went wrong.
Both HTTP 400 and 500 responses will contain a REST Integration Standard Response Object with appropriate values for the Code and/or Message fields, describing the error, in the response body.