The Conversations API has a few limits that you should be aware of when building conversational messaging features.
|Conversation Participant||Identity||256 characters|
|Conversation Participant||MessagingBinding.Address||256 characters|
|Conversation Participant||MessagingBinding.ProxyAddress||256 characters|
A Conversation can have up to 50 non-Chat participants and up to 1000 Chat participants.
A Chat identity (Chat user) can be part of 1000 Conversations and Chat Channels. Adding a participant whose identity already belongs to 1000 or more Conversations/Chat Channels will result in an error.
Unlimited — each Service Instance can hold as many channels as you wish!
Any media file type of up to 150MB is supported between chat-based participants. The Chat client must contain logic for Chat members to consume media of the various types.
JPG, PNG, MP3, AMR, MP4 and PDF files with a filesize of less than 5MB will be delivered from Chat particpants to SMS. If a message originating from a Chat SDK client contains a media file that is greater than 5MB in size, it will not be fanned out as an MMS message. However, Chat SDK consumers will still be able to retrieve the media file.
WhatsApp messages are currently limited to media files of up to 16MB in size.
For non-Chat participants, the channel’s own limits apply. Examples of channels include MMS and WhatsApp.
A single MMS message can contain no more than ten media files, and the total size of all media within the message cannot exceed 5MB. Please see Accepted Content Types for Media to learn what media types are supported by MMS.
Any single file cannot exceed 2MB, but you should note that a carrier may impose additional limits on file size.
A single WhatsApp message may contain one piece of media, of maximum size 16MB. Supported filetypes include JPG, PNG, MP3, AMR, MP4 and PDF.
An action is an operation that mutates the state of a Conversation and other resources, such as sending a message, updating the
friendly_name of a Conversation, or adding/removing a participant, etc. Read actions are not limited under APS.
All operations are rate-limited with a default maximum set at 30 APS. Some operations are rate-limited globally, ie. per Service, while others are limited per conversation. Refer to the table below to see whether a given resource is limited per Service or per Conversation.