# Rate limits

Requests per minute per environment, the headers that show them, and what happens over the limit.


Each account has a number of Texa API requests per minute for each environment. By default:

| Environment | Requests per minute |
|---|---|
| Live | 300 |
| Sandbox | 60 |

Every answer says where you stand:

| Header | Meaning |
|---|---|
| `X-RateLimit-Limit` | requests allowed in the current minute |
| `X-RateLimit-Remaining` | requests left in it |
| `X-RateLimit-Reset` | when the minute ends (Unix seconds) |

Over the limit, the answer is **429** with `Retry-After` in seconds. Wait that long, then send the
same request again (with the same `Idempotency-Key`, if it had one).

- `GET /v1/me` shows your current limit as `limits.requests_per_minute`.
- The widget's polling for new lines doesn't count against your limit.
- Need more? Write to [info@texadesk.com](mailto:info@texadesk.com) with your expected traffic.
  Limits are raised per account.

## Texa Desk API

The Texa Desk API limits requests per person and per address to protect the helpdesk your team is
working in. Space out bulk jobs (a few requests a second), and back off on 429.