Skip to main content
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 typePartitionLimit
Authenticated business API requestsBusiness300 requests per 60 seconds
Lead intake with a valid enabled sourceKeyBusiness intake300 requests per 60 seconds
Authenticated user fallbackUser300 requests per 60 seconds
Unauthenticated traffic or invalid source-key trafficIP address300 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/1.1 429 Too Many Requests
Content-Type: application/problem+json
Retry-After: 17

{
  "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 with the business, endpoints, source keys, expected sustained and burst volume, use case, and launch date.