Skip to main content
POST
/
transactional_messages
/
send_mms
Send an MMS Message
curl --request POST \
  --url https://api.v3.tatango.com/transactional_messages/send_mms \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <api-key>' \
  --data '
{
  "phoneNumber": "5551234567",
  "webhookUrl": "https://yourpostbackaddress.com",
  "content": "Check out this amazing image!",
  "subject": "Amazing Image",
  "attachmentUrl": "https://tatango-mms-attachments-production.s3.us-west-2.amazonaws.com/example-image.jpg",
  "smsFailover": "See our amazing image at example.com"
}
'
{
  "message": "Request accepted, sending message to recipient",
  "transactionId": "019687e1-1b54-70f4-a68a-60af7fa776f4"
}
You can use any publicly accessible URL for attachments, or upload them to Tatango using the attachments page.File Size Limits:
  • Shortcodes: Images (1MB), GIFs (0.6MB), Videos (2MB)
  • 10DLC: All files (0.75MB)
Supported File Types: JPG, JPEG, PNG, GIF, WebP, MP4, MPEG, vCard

Authorizations

x-api-key
string
header
required

Your Tatango API key. This is required for all requests to the API. You can find your API key in the Tatango App under My Account -> API -> Create API Key.

Body

application/json

MMS message request

phoneNumber
string
required

The destination phone number. Can be provided in any format (e.g., +1 555-123-4567, (555) 123-4567, 5551234567) but must be a valid U.S. or Canadian phone number.

webhookUrl
string
required

URL where webhooks will be sent. Must be a valid HTTPS URL.

Maximum string length: 255
content
string
required

The MMS message content.

Maximum string length: 3500
smsFailover
string
required

SMS fallback message content used when primary delivery method fails. Must contain only GSM 7-bit characters.

Required string length: 1 - 160
subject
string

Optional subject line for the MMS message.

Maximum string length: 40
attachmentUrl
string

Optional URL of an attachment, hosted by Tatango or an external website.

Maximum string length: 255

Response

MMS message accepted

message
string
required

Success message indicating the request was accepted.

transactionId
string
required

Unique transaction identifier for tracking the message.