Send RCS message
Changed onThis endpoint is in beta and may change in future versions. Sends an RCS message to a single recipient.
The message can be text (content_type: text) or a single image or video (content_type: media). For media, we fetch the start of the file when you send the request, which can add up to 10 seconds. The request fails with 400 if the file isn't publicly reachable over https, redirects, doesn't respond in time, or has an unsupported, mismatched or oversized file type. Each problem is reported against content.media.file_url.
Request
- Base URLhttps://api.transmitmessage.com
- AuthAPI key in header x-api-key
Request body
Example request
{
"sender": "DemoSender",
"recipient": "447903749662",
"content_type": "text",
"content": {
"text": {
"message": "Hi Michael,\nJust a quick reminder. You are amazing!!\nReply STOP to opt out."
}
},
"message_ref": "order-12345"
}Response
OK
Example response
{
"data": {
"id": "6fdae71c-dad7-4c36-9734-a69693ecf3b4",
"message_ref": "order-12345",
"sender": "DemoSender",
"recipient": "447903749662",
"content_type": "text",
"content": {
"text": {
"message": "Hi Michael,\nJust a quick reminder. You are amazing!!\nReply STOP to opt out."
}
},
"created_at": "2021-01-01T00:00:00Z"
}
}Changes
- breaking
added the new required request property
////// - breaking
removed the required property
////////from the response with the status - warning
removed the request property
////// - info
added the required property
////////to the response with the status
- breaking
- breaking
added to the
//response propertyoneOflist for the response status - warning
added the new
mediaenum value to the//response property for the response status - info
added the new
mediaenum value to the request property - info
added to the
request propertyoneOflist
- breaking