Understanding MMS Messaging
Important: To avoid having your MMS messages rejected, make sure you (1) keep your message size to 5MB or less for all attachments, and (2) check to make sure the URLs you use for your media go directly to the media file and the URLs are publicly accessible over the internet. All URLs must start with one of the following schemes: http://, https://, or cpaasmedia://. Check out Accepted Schemes for details.
Using Multimedia Message Service (MMS) messaging has similarities to sending SMS messages with a few exceptions.
Note: If the entire message is text, the message is sent as SMS. If there are attachments included, then the message is sent as MMS.
Initially, both SMS and MMS are sent using the same API endpoint:
https://api.intelepeer.com/_rest/v4/app/sms/send
Note: Multimedia Messaging Service (MMS) is available for SmartCommunicator™, SmartFlows™, SmartEngage™, and APIs. For more information, check out SMS / MMS Message Management.
While SMS messages use the following fields:
Field | Description |
---|---|
eid | The Customer ID |
from | The source telephone number (TN) in e.164 format |
to |
The destination TN in e.164 format |
text |
The message to be sent |
And take the following payload as in this example:
{
"eid": "1234567",
"from": "+14155551212",
"to": "+18145551212",
"text": "Thank you for your order!"
}
An MMS message uses each SMS field, with some changes, and adds the following additional fields:
Field | Description |
---|---|
media | The media array contains objects that describe the text, data, or links to send |
link |
The destination TN in e.164 format |
text |
An optional text-block can be used in place of a URL link or included in media; encoding is UTF-8 |
content-type |
An optional content-type; the default is default:<detect> |
filename |
An optional filename associated with the link; the default is default:<detect> |
data |
A data-block encoded using the method stated in the encoding field |
encoding |
The encoding of the data, supporting either base64 or raw; the default value is raw |
A sample MMS request would look like this :
{
"eid": "1234567",
"from": "+14155551212",
"to": "+18145551212",
"text": "Here are the pictures you requested.",
"media": [
{
"link": "https://i.imgur.com/faMls9L.png"
},
{
"link": "https://i.imgur.com/Kil4uKz.jpeg"
},
{
"link": "https://i.imgur.com/ofClDwt.jpg"
},
{
"link": "https://d2hmxmws0mtfmy.cloudfront.net/menus/menu-CO11.pdf"
},
{
"link": "https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcRY3A1R5TNEyYs_YYwXKarigeXmneFqU9LDeA&usqp=CAU"
}
]
}
Note: Review the Accepted Schemes section to help ensure your MMS messages will be accepted.
Limits
The following limits are in place for outbound MMS messages:
-
Maximum message size: 5 MiB
-
Maximum number of attachments: 5
Note: The single / multiple / total MMS attachment limit is 5 MiB.
-
Maximum number of links: 5
-
Maximum text size: 5,000 characters
-
Delivery Receipts (DLRs) are not supported for MMS messages
-
Messages may be rejected downstream by the carrier even if they meet IntelePeer’s criteria
Important: Messages that exceed the maximum message size are rejected.
Mobile Operator Limits
The following file sizes per carrier may also affect the delivery of your messages:
Mobile Operator | Maximum File Size |
---|---|
United States | |
AT&T |
1 MiB |
MetroPCS (GSM) |
1 MiB |
Sprint |
2 MiB |
T-Mobile USA |
1 MiB |
US Cellular |
500 KB |
Verizon Wireless |
1.2 MiB |
Canada |
|
Rogers Wireless / Rogers Wireless - Fido |
750 KB |
Telus Mobility |
750 KB |
Accepted Schemes
Review the following schemes to ensure your message content will be accepted.
Note: URLs and all content types are stored for approximately three (3) years.
URLs
-
https
-
http
-
cpaasmedia
Content Types
Note: Not all content types are supported by every device or carrier.
Applications
-
application/gzip
-
application/msword
-
application/pdf
-
application/rtf
-
application/smil
-
application/vcard
-
application/vnd.apple.pkpass
-
application/vnd.ms-excel
-
application/vnd.ms-powerpoint
-
application/vnd.openxmlformats-officedocument.presentationml.presentation
-
application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
-
application/vnd.openxmlformats-officedocument.wordprocessingml.document
Audio
-
audio/3gpp
-
audio/3gpp2
-
audio/L24
-
audio/QCELP
-
audio/SP-midi
-
audio/aac
-
audio/aac
-
audio/ac3
-
audio/amr
-
audio/amr
-
audio/amr-nb
-
audio/basic
-
audio/mid
-
audio/midi
-
audio/mp3
-
audio/mp4
-
audio/mp4
-
audio/mpeg
-
audio/ogg
-
audio/ogg; codecs=opus
-
audio/vnd.rn-realaudio
-
audio/vnd.wave
-
audio/wav
-
audio/webm
-
audio/x-wav
Images
-
image/bmp
-
image/dib
-
image/gif
-
image/jpe
-
image/jpeg
-
image/jpg
-
image/pjpeg
-
image/png
-
image/svg+xml
-
image/tif
-
image/tiff
-
image/vnd.microsoft.icon
-
image/webp
-
image/x-icon
-
image/x-ms-bmp
Text
-
text/calendar
-
text/csv
-
text/directory
-
text/plain
-
text/richtext
-
text/rtf
-
text/vcard
-
text/x-vcard
Video
-
video/3gpp
-
video/3gpp
-
video/3gpp-tt
-
video/3gpp2
-
video/3gpp2
-
video/H261
-
video/H263
-
video/H263-1998
-
video/H263-2000
-
video/H264
-
video/asf
-
video/h.263
-
video/h264
-
video/mp4
-
video/mp4
-
video/mp4-es
-
video/mp4v-es
-
video/mpeg
-
video/mpeg-4
-
video/quicktime
-
video/webm
-
video/x-motion-jpeg