Setting Up the SMS Channel
Hub supports two SMS configurations: Brazilian SMS managed by chatt2.me and a Twilio connection using your own credentials. Both send through POST /v1/communication/sms/message with the same base message shape.
Brazilian SMS
Choose Brazilian SMS when sending to Brazilian mobile numbers. In Hub, open Channels → SMS, choose the Brazilian option, and define the display name used to identify the channel. Provider credentials are managed by chatt2.me.
Brazilian SMS currently sends text messages. The recipient may include formatting or a leading +; Hub normalizes the number before submission.
{
"from": "My SMS channel",
"to": "+5511944574999",
"content": {
"text": "Your order has been confirmed."
}
}
For from, use the Application Channel ID or the Brazilian SMS display name configured for the same API-key application.
Twilio SMS and MMS
Choose Twilio to connect an Account SID, Auth Token, and sender phone number. Text messages are sent as SMS; a message containing a media URL is submitted as MMS where supported by the destination carrier.
{
"from": "+12025551234",
"to": "+12025559876",
"content": {
"text": "Check out our promotion!",
"imageUrl": "https://example.com/promo.jpg"
}
}
For from, use the Application Channel ID or configured Twilio sender number, with or without a leading +.
Incoming messages
For Twilio inbound SMS, configure the connected number's A message comes in webhook as an HTTP POST to:
https://app.chatt2.me/v1/communication/webhook/sms
Brazilian delivery updates are correlated automatically. Terminal provider failures are exposed in message-status webhooks through errorCode and errorMessage.
Twilio can send up to ten inbound media items. The normalized Hub message keeps the first URL in
content.mediaUrl for compatibility and also includes content.mediaUrls and
content.mediaAttachments, where each attachment carries its own url and mimeType.
MMS formats and limits
Twilio accepts up to 5 MB for the complete outbound MMS. JPEG, PNG and GIF can use that API ceiling; other accepted media are limited by the Hub to Twilio's documented 500 KB per-media ceiling. Carrier support can be narrower than Twilio's API support.
| Type | Explicit formats handled through Twilio MMS | Limit |
|---|---|---|
| Image | JPEG/JPG, GIF, PNG, HEIC, HEIF, TIFF, BMP; WebP input is converted to PNG | JPEG/JPG, GIF and PNG: 5 MB; other image MIME: 500 KB; 5 MB message total |
| Video | MP4/MPEG-4, MPEG, WebM, 3GP/3G2, H.261/H.263/H.264/H.265; QuickTime/MOV input is converted to H.264/AAC MP4 | 500 KB per media; 5 MB message total |
| Audio | OGG, MP3/MPEG, MP4/M4A, 3GP/3G2, WAV, AMR, AC3; WebM input is converted to M4A | 500 KB per media; 5 MB message total |
| Document/data | PDF, vCard, calendar, CSV, RTF and plain/rich text types accepted by Twilio MMS | 500 KB per media; 5 MB message total |
Brazilian SMS does not support media. The Hub converts WebP before sending it to Twilio. Microsoft Office documents are not listed as MMS formats in Twilio's current accepted-MIME table and should not be used.
Twilio does not publish an inbound MMS size limit. The Hub downloads inbound Twilio media with Account SID/Auth Token authentication, keeps up to ten attachments and applies a 2 GiB operational safety ceiling per download. This is a Hub protection, not a Twilio provider limit.
Content and responses
| Capability | Brazilian SMS | Twilio |
|---|---|---|
| Text | Yes | Yes |
| Image with text | No | MMS, carrier-dependent |
| Video, audio, document | No | MMS, carrier-dependent |
| Interactive, reaction, location, contact | No | No |
A successful submission returns messageId and status. sent means the provider accepted the message. An error response includes the available provider cause. Sending is also subject to the organization's SMS pricing and wallet balance.