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

# Rate Limits

> Platform API request rate limits in production and development, what happens when you exceed them, and limits on users and members.

The Platform API limits how many requests each client can make per second, and how many users and members you can create.

## Request rate limits

Rate limits apply to each client, per HTTP method, per second. The integration environment (INT, `https://int-api.mx.com`) has lower limits than production.

| Method | Production (requests per second) | Integration (requests per second) |
| :- | :- | :- |
| `GET` | 2,000 | 300 |
| `POST` | 750 | 100 |
| `PUT` | 750 | 100 |
| `DELETE` | 150 | 50 |

Some features have their own, lower limits.

## When you exceed a limit

When you exceed a rate limit, the API returns `429 Too Many Requests`:

```json theme={null}
{
  "error": {
    "message": "Too many requests to this action.",
    "status": "too_many_requests",
    "type": "too_many_requests_error"
  }
}
```

The response doesn't include a `Retry-After` header. Limits reset every second, so retry after a short wait, and use exponential backoff if you keep receiving `429` responses. To avoid hitting limits, spread requests out over time instead of sending them in bursts.

## User and member limits

* **Users:** The integration environment allows up to 100 users.
* **Members:** A user can have up to 25 members, in both integration and production.
* **Institutions:** The integration environment provides access to only some institutions.

Aggregation has its own limits, including how often you can aggregate a member. See [Aggregation](./aggregation).