Long SMS messages that exceed a route's segment limit now send successfully: enable automatic chunking on a messaging profile and Telnyx splits oversized messages into sequential chunks instead of returning an error.
40302 when the flag is off.auto_chunk_long_messages on any messaging profile with a single API call. The flag is profile-level, with no per-request parameter.parent_message_id and child_message_id, so you can correlate webhooks that arrive out of order.Most carriers reject concatenated SMS past 10 segments, which capped how much content you could reliably deliver. Handling that limit yourself means counting segments per encoding, choosing split points, queuing chunks, and matching receipts, and any mistake in that glue code shows up as fragmented or missing messages. Server-side chunking removes the custom code: long-form alerts, reminders, and notifications stay deliverable on capped routes while billing stays predictable, since each chunk bills only its own segment count.
40302.curl -X PATCH https://api.telnyx.com/v2/messaging_profiles/{id} \ -H "Authorization: Bearer $TELNYX_API_KEY" \ -H "Content-Type: application/json" \ -d '{"features": {"auto_chunk_long_messages": true}}'
Learn more in the SMS chunking docs and the message encoding guide.