Sending SMS messages
Last updated
Was this helpful?
Last updated
Was this helpful?
In order to send a message, you must have an active SMS channel and perform a HTTP request to the following endpoint with a valid access key
When sending outbound messages as well as setting the receiver information you must set message body field in all cases except for sending a message template when you must only set the template field
Body
Template
All SMS channels support sending basic text based messages using SMS. The example below must be set in the message body field
To send an SMS text message set the message body as follows:
SMS channels that are installed with MMS capable numbers (currently numbers purchased for the United States and Canada) also support media messaging. You can also verify if the channel is MMS capable via the API as described here.
Single image message with text and title
When sending multiple image messages it is possible to send up to an array of 10 media URLs.
The examples below must be set in the message template field
Text templates will be sent as SMS messages and are compatible with all SMS channels
Using it is possible to create text and media templates that can quickly be reused to send to contacts. Templates must be active before they are used.
Send a message to a channel
/workspaces/{workspaceId}/channels/{channelId}/messages
The ID of the workspace
The ID for a channel
A reference to the message. This can be used to identify the message in the channel.
my-own-identifier
If set to true, the frequency capping settings of the platform will be used
to either allow or reject the message to a contact. Can only be set to true
if the message is sent to a contact and .meta.extraInformation.useCase
is marketing
.
If set to true and message is a test/campaign message, web tracking parameters will be appended to the links in the message.
If set to true, quiet hours settings will be ignored and the message will be sent as soon as possible.
Do not check if the recipient is part of global holdout. To be used to send transactional messages.
Tags to associate with the message. Tags are converted to lower case and tags that do not exist are automatically created. You can view your created tags in the UI. You can specify up to 10 tags per message.
SMS link shortening options. When using templates, please refer to
the template level shortLinks
instead.
Scheduled time to send message at. Must be formated as RFC3339 timestamp. When
set, the message status will be scheduled
until it's sent. Messages scheduled
for a time in the past or within 10 minutes of the request may be sent
immediately. Messages scheduled farther than 35 days will be rejected.
Validity determines for how many seconds a message is valid. If none is provided, the channel message type will be used to determine it. A promotional, conversational or transactional channel message is valid for 36 hours (129600 seconds). A message sent from a 2FA channel is valid for 10 minutes (600 seconds).