Send Single MMS
Messages
Send Single MMS
Send a manual MMS message with media to a contact (live agent/human takeover)
POST
Send Single MMS
Send Single MMS
Send a manual MMS message with a media attachment to a contact within a campaign. This enables live agents to share images, documents, or other media with contacts.Authentication
Your API key
Request Body
The campaign ID containing the contact
The contact’s phone number (E.164 format recommended: +15551234567)
URL to the media file. Must be a publicly accessible HTTP/HTTPS URL - the carrier will fetch this URL directly to deliver the media.
Optional text message to accompany the media
Media URL Requirements
Recommended Storage Options:- Amazon S3 - Use public buckets or pre-signed URLs with long expiration
- Google Cloud Storage - Use public objects or signed URLs
- Azure Blob Storage - Use public containers or SAS tokens
- Cloudinary - Provides direct public URLs
- Any CDN - As long as the URL is publicly accessible
- URL must start with
http://orhttps:// - URL must not require authentication headers or cookies
- URL should remain accessible for at least 24 hours (carriers may retry)
- File must be within size limits (see table below)
Supported Media Types
| Type | Extensions | Max Size |
|---|---|---|
| Images | jpg, jpeg, png, gif | 5 MB |
| Video | mp4, 3gp | 10 MB |
| Audio | mp3, wav, ogg | 5 MB |
| Documents | 5 MB |
Response
Whether the MMS was sent successfully
Status message
The normalized phone number the message was sent to
The campaign ID
The media URL that was sent
Whether the conversation thread was marked as qualified
Whether AI follow-ups have been disabled for this contact
Indicates this was a human takeover action
Example Request
Example Response
Use Cases
- Product Images - Share product photos with interested leads
- Brochures/PDFs - Send informational documents
- Location Maps - Share directions or maps
- Promotional Content - Send special offers with images
Error Responses
Notes
Important: You are responsible for hosting and serving the media files. Store your media in cloud storage (S3, GCS, Azure, Cloudinary, etc.) and provide the public URL.
- Media URL must be publicly accessible - No authentication, API keys, or session cookies
- The media file is fetched directly by the carrier network to deliver to the recipient
- URLs should remain valid for at least 24 hours (carriers may retry failed deliveries)
- Some carriers may have additional size or format restrictions
- Like SMS, sending MMS disables AI follow-ups for the contact
- The contact must already exist in the specified campaign
Related Endpoints
- Send SMS - Send text-only message
- Get Campaign Messages - View conversation history

