What is enforced today
There is currently no per-key rate limit on the Leadey API. Requests are not throttled and no429 is returned for volume.
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-RemainingandRateLimit-Reseton every response, so you can see your allowance without guessing at it429 Too Many RequestswithRetry-Afteronce the allowance is spent- notice before the limit takes effect, and a headroom period for existing integrations
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
429from day one. RespectRetry-Afterwhen present; fall back to exponential backoff when it isn’t. - Back off on
5xxtoo. The same code path covers a restart or a deploy. - Page efficiently.
pageSize=100plus 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.