Rate Limits

To keep the platform stable, the API enforces limits on request frequency and the size of data transmitted.

Request rate

When the allowed request rate is exceeded, the server responds with 429 Too Many Requests. The correct response is to retry with exponential backoff: increase the pause between retries and avoid sending requests in a dense burst. Spread bulk operations out over time and reuse a single token sequentially rather than in parallel spikes.

Request body size

For regular REST requests, the JSON body size limit is 2 MiB. This is sufficient for any reaction configurations, collections, and settings. If the body is larger, split the operation into parts (for example, import reactions in batches).

Body size for imports

Import endpoints are designed for large bundles and have separate, higher limits: up to 64 MiB for data imports and up to 256 MiB for imports with embedded media. If the bundle is larger, split it into multiple imports.

Exceeding limits

• Rate limit exceeded: 429, retry with backoff.
• Body larger than allowed: the request is rejected (413 or 400 depending on the endpoint); reduce or split the payload.

What's next

• Errors: 429 and other codes.
• Import from SamBot: large import bundles.
• Interactive reference: per-endpoint limits.