File Attachments and API Limits
Flex Conversations requires Flex UI 2.0. If you are on Flex UI 1.x, please refer to Messaging in Flex pages.
File Attachments and API Limits
For enabling file attachments on your Flex account, see "How do I enable and configure file attachments?" in the Conversations FAQ and Troubleshooting page.
|
Address Type |
Number of attachments |
Max File Size (bytes) |
Max Total File Size (bytes) |
Accepted Extensions |
|
web |
1 |
16777216 |
67108864 |
"jpg", "jpeg", "png", "amr", "mp3", "mp4", "pdf", "heic", "txt", "gif" |
|
sms |
1 |
2097152 |
5242880 |
"jpg", "jpeg", "png", "amr", "mp3", "mp4", "pdf", "heic" |
|
|
1 |
16777216 |
67108864 |
"jpg", "jpeg", "png", "amr", "mp3", "mp4", "pdf", "heic", "oga" |
|
|
10 |
157286400 |
157286400 |
"jpg", "jpeg", "png", "amr", "mp3", "mp4", "pdf", "heic", "txt", "gif" |
Conversations API Limits
See Conversations Limits for a detailed list on length, media, and other limits.
Interactions Endpoint Limits
GET actions are not accessible for the API endpoints.
Due to various limitations and concerns, Flex Conversations will constrain certain actions.
Rate limits on API endpoints
The Interactions API has a limit of 20 requests per second per endpoint per account. The API returns an HTTP 429 status when rate limits are exceeded and should be handled accordingly on the customer side.
Webchats Endpoint Limits
The Flex Webchat orchestrator currently has a rate limit of 5 requests per second beyond which the customer can get throttled. When exceeded, the API returns an HTTP 429.
Need some help?
We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd by visiting Twilio's Stack Overflow Collective or browsing the Twilio tag on Stack Overflow.
