---
title: "RATE_LIMIT"
description: "What triggers a RATE_LIMIT error (HTTP 429) and how to handle rate limiting."
canonical_url: "https://docs.leyr.io/api/error-handling/rate_limit"
---
# RATE_LIMIT

> What triggers a RATE_LIMIT error (HTTP 429) and how to handle rate limiting.

## Summary

Corresponds to a standard `429 Too Many Requests` HTTP response status

> You have sent too many requests in a given amount of time and the rate limit has been exceeded.

## Example Response

```json
{
    "code": "RATE_LIMIT",
    "type": "https://docs.leyr.io/api/error-handling/rate_limit",
    "title": "Rate limit exceeded",
    "status": 429,
    "detail": "Rate limit exceeded. Please try again later.",
    "instance": "36b5909e-4391-4520-b303-84cbb80c4264"
}
```

## Common Causes

- Sending too many requests within a short time window
- Retry storms - aggressively retrying failed requests without delays

## Resolution Steps

1. Retry the request after a delay, using progressive backoff (e.g. 1s, 5s, 15s, 30s, 1m).
2. Reduce request concurrency and avoid bursting - spread polling or batch jobs over time.
3. If your integration legitimately needs a higher rate limit, contact our support team at [contact@leyr.io](mailto:contact@leyr.io).


## Sitemap

See the full [sitemap](https://docs.leyr.io/sitemap.md) for all pages.