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

# Rate limits

> How throttling and quotas surface in responses, and how to back off.

Two separate mechanisms can refuse a request. They return different
status codes, so handle them differently.

## Rate limits: `429`

Requests are throttled per workspace. A throttled request returns
`429` with a `Retry-After` header giving the seconds to wait.

```bash theme={null}
curl -i -H "X-API-Key: $API_KEY" $API_BASE/api/datasets
# HTTP/1.1 429 Too Many Requests
# Retry-After: 30
```

Wait for `Retry-After` and retry. Add jitter if several workers share
a key, so they do not retry in step.

## Quotas: `402`

Runtime Security scans are metered against your plan's
`max_runtime_security_calls`. When the quota runs out, scan routes
return `402` with the typed code `QUOTA_EXCEEDED` until the quota
resets or the license is upgraded. Retrying does not help.

Runtime Security Apps also carry hourly and daily event caps that
answer `429` with `APP_QUOTA_EXCEEDED`. See
[Runtime Security errors](https://docs.blindsight.io/runtime-security/errors.md) for both.

## Next steps

* [Errors](https://docs.blindsight.io/api-reference/errors.md): the response envelope.
* [Runtime Security errors](https://docs.blindsight.io/runtime-security/errors.md): codes specific to scan and proxy.


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