Sends a message to a single recipient using a send definition.
| Name | Type | Description |
|---|---|---|
messageKey | string | A unique identifier that you can use to track the status of the message. The key can contain up to 100 characters. There are no character restrictions. The message key that you provide must be unique among all of the keys used in your business unit over the last 2 days. |
| Name | Type | Description |
|---|---|---|
definitionKey | string | Required. The ID of the send definition. |
recipient | object | Required. An object that contains parameters and metadata for the recipient, such as send tracking and personalization attributes. If this object is present in the request, the recipients array (which is used to send messages to multiple recipients) can’t be included in the request. |
recipient.contactKey | string | Required. A unique identifier for the subscriber. You can create a contact key at send time if the contact isn’t already in Marketing Cloud Engagement. |
recipient.to | string | Required. The phone number of the recipient. |
recipient.attributes | object | Personalization information for the recipient, written as key-value pairs. The attributes must match existing profile attributes or content attributes. |
content.message | string | An override for the message content in the send definition. Use substitution strings to personalize the content. |
1Host: https://YOUR_SUBDOMAIN.rest.marketingcloudapis.com
2POST /messaging/v1/sms/messages/MESSAGE_KEY
3Content-Type: application/json
4Authorization: Bearer YOUR_ACCESS_TOKEN
5
6{
7 "definitionKey": "account-reset",
8 "recipient": {
9 "to": "15555551234",
10 "contactKey": "Astro25",
11 "attributes": {
12 "FirstName": "Astro",
13 "password": "1234567890ab"
14 }
15 },
16 "subscriptions": {
17 "resubscribe": true
18 }
19}The response includes a request ID. The responses array contains a messageKey value for the message. If a message was sent successfully, the array object doesn’t contain any additional information. If a message failed to send, the response includes an errorcode that describes the reason that the message failed. For a list of error codes that the API returns, see Transactional API Subscriber Error Codes and Transactional API Response Level Error Codes.
1HTTP/1.1 202 Accepted
2{
3 "requestId": "239a2bc3-bdcb-4f8a-9e08-28aff9f983b7",
4 "errorcode": 0,
5 "responses": [
6 {
7 "messageKey": "f4fe74b7-c3c0-4e5a-9f49-b63a641109a2"
8 }
9 ]
10}
j