MM7 Gateway Now Available for Telnyx MMS

Telnyx Messaging now supports MM7, the SOAP/XML standard used by carrier MMSCs and enterprise MMS platforms. Systems that already speak MM7 can send and receive MMS through Telnyx without rewriting to a JSON API.

What's new

• MM7 send: Post a standard MM7 SubmitReq to api.telnyx.com/v2/messaging/mm7/submit with your standard Telnyx API key; sender numbers just need to be on your account.
• MM7-native receiving: Opt in per messaging profile with mm7_metadata (mm7_webhook_url plus an optional failover URL) in the Profiles API. Inbound MMS then arrives as MM7 DeliverReq and reports as DeliveryReportReq; without the setting, events keep arriving as standard JSON webhooks.
• Webhook failover: If the primary MM7 webhook fails, delivery retries automatically to your secondary URL.
• Same pipeline: MM7 sends run through the same routing, anti-spam, and rate limiting as standard MMS. Media is re-hosted on Telnyx Storage; Telnyx Wireless numbers are supported.
• No gating: Available to all accounts, with 2 MB payloads on MM7 version 6.8.0.

Why it matters

Enterprise MMS platforms, carrier integrations, and legacy alerting stacks were built on MM7, and porting them to a REST API means rewriting working code. Supporting MM7 removes that migration tax: point your existing MM7 client at Telnyx and keep the interface. Because MM7 traffic rides the same carrier-owned pipeline as every other MMS message, those integrations also get Telnyx routing, anti-spam, and delivery visibility.

Example use cases

• Enterprise messaging platforms already integrated with carrier MMSCs over MM7 that want a second carrier path without a rewrite.
• Banks, utilities, and healthcare systems running MMS alerts from legacy stacks that speak MM7 natively.
• Teams consolidating vendors: keep the MM7 integration and move the number traffic to Telnyx.

Getting started

• Point your MM7 client at POST /v2/messaging/mm7/submit and authenticate with your standard Telnyx API key as a Bearer token.
• To receive inbound MMS and delivery reports over MM7, set mm7_metadata on your messaging profile via PATCH /v2/messaging_profiles/{id} with mm7_webhook_url and optionally mm7_failover_webhook_url.
• Without it, inbound messages and reports keep arriving as standard JSON webhooks.