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

# Rate Limits

> Leadping API request limits and 429 retry behavior.

*Revision Date: June 29, 2026*

Leadping API requests are limited to **300 requests per 60 seconds** for the applicable partition. Requests over the limit return `429 Too Many Requests`.

Leadping does not queue excess API requests.

## Limits

| Request type                                          | Partition       |                       Limit |
| ----------------------------------------------------- | --------------- | --------------------------: |
| Authenticated business API requests                   | Business        | 300 requests per 60 seconds |
| Lead intake with a valid enabled `sourceKey`          | Business intake | 300 requests per 60 seconds |
| Authenticated user fallback                           | User            | 300 requests per 60 seconds |
| Unauthenticated traffic or invalid source-key traffic | IP address      | 300 requests per 60 seconds |

Most authenticated business endpoints count against the business partition. Lead intake through `POST /leads`, `POST /leads/intake`, or `GET /leads/intake` counts against the business intake partition when Leadping can resolve a valid enabled `sourceKey`.

Requests with missing, invalid, disabled, or mismatched source credentials use the IP partition.

## 429 Responses

```http theme={null}
HTTP/1.1 429 Too Many Requests
Content-Type: application/problem+json
Retry-After: 17
```

```json theme={null}
{
  "status": 429,
  "title": "Too many requests.",
  "detail": "The API rate limit for this account has been exceeded."
}
```

`Retry-After` is in seconds. Wait for that value before retrying. If the header is not present, retry with exponential backoff and jitter.

## Higher Throughput

For higher sustained API throughput, contact [support@leadping.ai](mailto:support@leadping.ai) with the business, endpoints, source keys, expected sustained and burst volume, use case, and launch date.