# Rate Limits

The API uses rate limiting to ensure service stability for all users.

## Current Limits

- **100 requests per minute** per organization
- Token bucket algorithm
- Resets every 60 seconds


## Rate Limit Headers

Every response includes rate limit information:


```http
HTTP/1.1 200 OK
RateLimit-Limit: 100
RateLimit-Remaining: 87
RateLimit-Reset: 1699564800
```

| Header | Description |
|  --- | --- |
| `RateLimit-Limit` | Maximum requests per window |
| `RateLimit-Remaining` | Requests remaining |
| `RateLimit-Reset` | Unix timestamp when limit resets |


## When Limit is Exceeded

**429 Too Many Requests** response:


```http
HTTP/1.1 429 Too Many Requests
Content-Type: application/problem+json
Retry-After: 60

{
  "type": "https://docs.apiera.io/problems/rate-limit-exceeded",
  "title": "Rate Limit Exceeded",
  "status": 429,
  "detail": "Rate limit of 100 requests per minute exceeded. Please retry after 60 seconds.",
  "instance": "/v1/products",
  "correlationId": "550e8400-e29b-41d4-a716-446655440000"
}
```

Wait for the duration specified in the `Retry-After` header before retrying.

## Best Practices

- Monitor `RateLimit-Remaining` header
- Respect `Retry-After` when receiving 429 responses
- Cache responses when possible
- Use bulk endpoints instead of individual requests
- Spread requests evenly throughout the minute


## Need Higher Limits?

Contact support through your dashboard to discuss enterprise rate limits.