Receive an MMS Message
Overview
Get your message returned via SMTP or via a webhook URL that you provide.
Routing Address
When requesting routing for your MMS messages, you may either specify an MM4 (SMTP) or HTTP endpoint.
It’s possible to provide Basic authentication details with the routing address:
HTTP Routing Address
(http|https)://[<username>:<password>@]<hostname>[:<port>][/*<path>]
Examples
http://example.com/inbound_messages
http://username:password@example.com:8080/inbound_messages
https://johndoe:secret@example.com:8080/messages/mms/tsg_inbound
MM4 Routing Address
mm4://[<username>:<password>@]<hostname>[:<port>]
Examples
mm4://example.com:2526
mm4://johndoe:secret@example.com:2526
Webhook Format
All requests are made using the POST HTTP Verb to the specified endpoint.
Similar to the HTTP API, the webhook uses the very same format for delivering messages.
The request will include the following headers:
NOTE: additional headers may be included that are not listed here.
Webhook Response
When responding to the webhook request, respond with a 2xx status, more specifically:
200 OK
202 Accepted
204 No Content
Any of these statuses will be accepted as an acknowledgement of receive.
Otherwise the MMS system will assume delivery failed and will retry an additional 2 times within it’s current timeframe. If this fails once more, the message will be placed unto the retry and tried at a later time. The message will be retried a total of 20 times with an exponential backoff.
Once a message is received by the system and it’s routing is determined, it cannot be re-routed.
Note: All messages will keep their routing, changing a did’s routing will NOT affect messages already in-flight, this ensures that a message meant for an old endpoint will be delivered to that endpoint and nowhere else.
Example Response
Last updated