Prerequisites
- A Telnyx account
- A Messaging Profile with an MMS-enabled phone number
- An API key
How group messaging works
Group messaging builds on the MMS protocol to enable multi-party conversations:- You send a message to the
/v2/messages/group_mmsendpoint with multipletonumbers - Telnyx delivers the message to all recipients as a group MMS conversation
- When any recipient replies, all participants (including your Telnyx number) receive the reply
- You receive inbound group messages via webhooks with a
ccfield listing all participants
Group messaging constraints:
- Maximum of 8 recipients per conversation (plus the sender)
- MMS protocol only — all messages are billed at MMS rates
- US and Canada destinations only
- Requires a v2 webhook version on your messaging profile for inbound messages
- Charged per recipient — standard MMS rates plus carrier passthrough fees apply
Send a group message
Response
A successful response includes per-recipient status:id to correlate delivery webhooks with your group message.
Receive group messages
When someone replies to the group conversation, you receive amessage.received webhook. The cc field lists all other participants in the conversation:
Example inbound group message webhook
Example inbound group message webhook
| Field | Description |
|---|---|
from.phone_number | The participant who sent the reply |
to | Your Telnyx number(s) in the conversation |
cc | All other participants in the group conversation |
Webhooks and delivery tracking
Group messages generate individual webhook events and detail records for each recipient:- Per-recipient webhooks: You receive a separate
message.finalizedevent for each recipient with their individual delivery status group_message_id: A unique identifier returned in the API response, webhooks, and detail records that lets you correlate all individual records back to the original group message- Non-Telnyx recipient status: Handset delivery confirmation is not available for non-Telnyx recipients — their status will show as
unknown
Example delivery webhook
Example delivery webhook
Comparison with other providers
| Feature | Telnyx | Twilio | Vonage |
|---|---|---|---|
| Group MMS support | ✅ Native, single API call | ⚠️ Requires Conversations API | ❌ Not natively supported |
| Max participants | 8 + sender | 10 total | N/A |
| Dedicated endpoint | ✅ /v2/messages/group_mms | ❌ Requires Conversations setup | N/A |
| Setup complexity | Single POST request | Multi-step (create conversation, add participants) | N/A |
| Per-recipient tracking | ✅ Individual webhooks | ✅ Via Conversations events | N/A |
| US/Canada support | ✅ | ✅ | N/A |
Troubleshooting
Messages not delivered to all recipients
Messages not delivered to all recipients
- Verify all
tonumbers are valid US or Canadian wireless numbers - Group MMS requires MMS-capable handsets — landlines and some VoIP numbers won’t receive them
- Check that you haven’t exceeded the 8-recipient limit
Not receiving inbound group messages
Not receiving inbound group messages
- Ensure your messaging profile uses v2 webhook version — go to Messaging, edit your profile, and confirm the webhook version
- Verify your webhook URL is accessible and returning
200 OK
Status shows 'unknown' for recipients
Status shows 'unknown' for recipients
This is expected for non-Telnyx recipients. The MMS protocol does not reliably support delivery receipts across all carriers. Only Telnyx-to-Telnyx messages will show confirmed delivery status.