Skip to main content

What is enforced today

There is currently no per-key rate limit on the Leadey API. Requests are not throttled and no 429 is returned for volume.
An earlier version of this page stated a limit of 120 requests per minute. That number was never enforced. If you sized an integration around it, you were working from the wrong figure — the correction is below, and nothing you built will have been throttled.
We are introducing a published limit, because an unmetered API is not one we can promise to keep fast for everyone. When it lands it will arrive with:
  • RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset on every response, so you can see your allowance without guessing at it
  • 429 Too Many Requests with Retry-After once the allowance is spent
  • notice before the limit takes effect, and a headroom period for existing integrations
Until then, treat throughput as a courtesy rather than a contract. If you are planning a bulk migration or a high-volume sync, tell us the shape of it at support@leadey.ai and we will make sure it lands comfortably.

Building so a limit never breaks you

Write the client as though the limit already exists and you will never have to revisit it.
  • Handle 429 from day one. Respect Retry-After when present; fall back to exponential backoff when it isn’t.
  • Back off on 5xx too. The same code path covers a restart or a deploy.
  • Page efficiently. pageSize=100 plus filters means fewer round trips — see Pagination.
  • Prefer a filter to a poll. Fetching a narrow slice repeatedly beats re-reading a full list.
  • Cache what rarely changes — pipelines, statuses, users, custom field definitions.
Spreading work across several API keys is not a way around a future limit — when it lands it will be scoped per workspace, not per key.