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

# Rate Limits

> Understand rate limits and how to increase them for the Inbound API

The response headers describe your current rate limit following every request in conformance with the [sixth IETF standard draft](https://datatracker.ietf.org/doc/html/draft-ietf-httpapi-ratelimit-headers-06):

| Header name | Description |
| - | - |
| `ratelimit-limit` | Maximum number of requests allowed within a window. |
| `ratelimit-remaining` | How many requests you have left within the current window. |
| `ratelimit-reset` | How many seconds until the limits are reset. |
| `retry-after` | How many seconds you should wait before making a follow-up request. |

## Default Rate Limits

The default maximum rate limit is **100 requests per second per account**, shared across authenticated E2 API endpoints. This single budget covers:

* **Email sending endpoints**: 100 requests per second
* **Email management endpoints**: 100 requests per second
* **Domain/configuration endpoints**: 100 requests per second
* **All other authenticated E2 endpoints**: 100 requests per second

This number can be increased for trusted senders upon request.

## Rate Limit Response

After exceeding the rate limit, you'll receive a `429 Too Many Requests` response error code:

```json theme={null}
{
  "error": "Too Many Requests",
  "message": "Rate limit exceeded. Maximum 100 requests per second. Retry after 1 seconds.",
  "statusCode": 429
}
```

## Increasing Rate Limits

If you have specific requirements that exceed the default limits, you can request a rate increase:

**1. Contact Support**

Reach out to our support team at [support@inbound.new](mailto:support@inbound.new) with your requirements.

**2. Provide Use Case Details**

Include details about your use case, expected volume, and business requirements.

**3. Review and Approval**

Our team will review your request and work with you to find an appropriate solution.

## Rate Limit by Endpoint

> [!WARNING]
>
> Rate limits are applied per account. If you're using multiple accounts, each account has its own rate limit bucket.

**Important**: The SDK will return rate limit errors directly - you must handle them in your application code.

## Next Steps

> [card] [Authentication](https://inbound.new/docs/api-reference/introduction.md#authentication)
>
> Learn how to authenticate your API requests

> [card] [Send Your First Email](https://inbound.new/docs/api-reference/emails/send-an-email.md)
>
> Start sending emails with proper rate limiting

> [card] [Error Codes](https://inbound.new/docs/api-reference/errors.md)
>
> See all API error codes including rate limit responses


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