Skip to main content
Leadsforge API limits how fast you can call it, so that one integration cannot slow down everyone else. The main limits are requests per minute and jobs running at the same time. Both answer 429 rate_limited when you exceed them.

Requests per minute

Each rate-limited endpoint has its own window of one minute. The window slides: a slot frees up one minute after the request that used it. These are defaults. Support can set different limits for your account.

Rate limit headers

Responses from rate-limited endpoints carry three headers: When you hit the limit, the 429 response also carries Retry-After with the number of seconds to wait.

Jobs running at the same time

Each account can run a limited number of jobs of each type at once: enrichment jobs (all channels together), company followers searches, and maps discovery searches. The default is 10 of each. Maps discovery searches started in the Leadsforge app count toward that limit too. A start request beyond the limit gets 429 rate_limited without Retry-After. Wait for a running job to finish, then retry. Only one maps owner enrichment can run per maps search; a second one gets 409 conflict.

Other 429 responses

A few other cases also answer 429 rate_limited:
  • A lookalike endpoint, or the start of a company followers or maps discovery search, is temporarily busy.
  • Your account has a limit on searches running at the same time, and you send another search or count while that many are already running.
These responses can come without Retry-After and without rate limit headers, so back off with jitter.

Retrying well

  • Honor Retry-After when it is present.
  • Without it, back off with jitter instead of retrying in a tight loop.
  • Retry job start requests with the same Idempotency-Key, so a retry never starts a second job. See Asynchronous jobs.