429 Too Many Requests.
Leadping does not queue excess API requests.
Design for
429 Too Many Requests before launch. A client that retries immediately can turn a short throttle into a longer outage.Limits
Most authenticated organization endpoints count against the organization partition. Lead intake through
POST /leads, POST /leads/intake, or GET /leads/intake counts against the organization intake partition when Leadping can resolve a valid enabled Authorization: Bearer lp_src_... source key.
Requests with missing, invalid, disabled, or mismatched source credentials use the IP partition.
429 Responses
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 organization, endpoints, source keys, expected sustained and burst volume, use case, and launch date.Related API guidance
- Leadping API Authentication explains organization keys, user tokens, and source keys.
- Leadping API Reference documents endpoint request and response contracts.
- Leadping SDK Overview covers generated clients and request adapters.
- Sending Leads to Leadping explains safe retries and intake-specific failures.
Last updated: June 29, 2026