POST /messaging/v1/sms/messages/{messageKey}
Sends a message to a single recipient via a send definition using a messageKey path parameter.
Name | Type | | Description |
---|
messageKey | string | Required | Unique identifier used to track message status. The messageKey can be created automatically when you create a message, or you can provide it as part of the request. Can be up to 100 characters, and there are no restricted characters. Each recipient in a request must have a unique messageKey. If you use a duplicate messageKey in the same send request, the message is rejected. |
Name | Type | | Description |
---|
definitionKey | string | Required | Unique identifier of the definition. |
recipient | object | Required | Object that contains parameters and metadata for the recipient, such as send tracking and personalization attributes. Use this parameter to send to one recipient. Use either the recipient or recipients parameter, but not both. |
recipient.contactKey | string | | Unique identifier for a subscriber in Marketing Cloud. Each request must include a contactKey. You can use an existing subscriber key or create one at send time by using the recipient’s email address. |
recipient.to | string | Required | Channel address of the recipient. |
recipient.attributes | object | | Information used to personalize the message for the recipient. Written as key pairs. The attributes match profile attributes, content attributes, or triggered send data extension attributes. |
content.message | string | | Override for message content in the definition that you want sent with each message. Use substitution strings to personalize the content. |
Status | Name | Type | Description |
---|
202 | | | Request is accepted. Review example response. |
| requestId | string | The unique identifier of this request. |
| errorcode | string | Error code for the exception |
| messageKey | string | Unique identifier to track message send status. |
Response | Reason |
---|
202 Accepted | Request is accepted. Review example response. |
400 Bad Request | Invalid request |
401 Unauthorized | Failed to pass authorization |
403 Forbidden | Failed to pass authorization. |
500 Server Error | Internal error |