Rate Limits and Sizes
Handle frequent requests and oversized files: 429 and 413 responses, request sizes, and import bundles.
في هذه الصفحة
If your program sends requests too often, the server may ask it to wait. If it sends too much data at once, the request is rejected. Here is how to handle both cases. Limits of the visual builder are described in Platform limits.
Request rate
When the allowed request rate is exceeded, the server responds with 429 Too Many Requests. Pause before retrying. If another request is rejected, increase the pause, for example from 1 to 2 and then 4 seconds. This is called exponential backoff (backoff). Spread bulk operations over time instead of starting many requests at once.
Request body size
For regular REST requests, the JSON body size limit is 2 MiB. If the body is larger, split the operation into parts (for example, import reactions in batches).
Body size for imports
Imports have separate limits: up to 64 MiB for a reaction archive, including its files, and up to 256 MiB for a conversation-history archive, including attachments. Both the uploaded archive and its total contents after extraction must fit the relevant limit. If an archive is larger, split the data into multiple imports.
Exceeding limits
- Rate limit exceeded:
429, retry with backoff. - Body larger than allowed: the request is rejected (
413or400depending on the endpoint); reduce or split the payload.
What's next
- Errors:
429and other codes. - Import from SamBot: large import bundles.
- Interactive reference: per-endpoint limits.