# Rate Limits

To ensure platform reliability and fair use, Resolve implements rate limits for the REST API.

Resolve APIs use the Sliding Window algorithm to monitor and control request rates with a **100 requests/minute** limit. The API will return a `429 Too Many Requests` status if the amount of requests exceeds rate limits.

All responses from Resolve APIs will include the following headers:

- `X-Ratelimit-Limit`: The maximum amount of requests permitted within a 60-second period.
- `X-Ratelimit-Remaining`: The remaining requests within the current period.
- `X-Ratelimit-Reset`: A UNIX timestamp indicating when the rate limit period will reset.

<h2>Best Practices</h2>

- Use caching when necessary for data that is routinely requested by your application.
- Utilize the `X-Ratelimit-Limit` and `X-Ratelimit-Remaining` response headers in your application to avoid surpassing rate limits.
- Your application should avoid making additional API requests if your requests return with a `429` status code.