> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sendbaze.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Rate limits

> 100 requests per second per organisation, shared across all keys, with headers that tell you where you stand.

The API allows **100 requests per second per organisation**, counted across every key the organisation has. Above the limit the API answers `429 rate_limited` with a `Retry-After` header.

## Headers

Every response carries:

| Header | Meaning |
| - | - |
| `x-ratelimit-limit` | Requests allowed per second |
| `x-ratelimit-remaining` | Requests left in the current second |
| `retry-after` | On a 429 only: seconds to wait |
| `x-request-id` | Unique id of this request, for support |

## Staying under it

* **Use the batch endpoints.** `POST /v1/emails/batch` and `POST /v1/sms/batch` send up to 1,000 messages and count as one request.
* **Retry with backoff** on 429 and on connection errors, with the same `Idempotency-Key` so a retry never sends twice. The SDK throws `SendbazeError` with `status: 429` and `SendbazeConnectionError` for network failures.
* **Queue on your side.** For campaigns, pull from your own queue at a steady rate rather than firing thousands of parallel requests.

Need more? Email [support@sendbaze.com](mailto:support@sendbaze.com) with your expected peak and we will raise the limit for your organisation.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.