Skip to content
Scope an integration

Glossary

What is API rate limiting?

Rate limiting is the cap an API places on how many requests a client can make in a period of time, to protect the service from overload.

Rate limiting is how an API controls traffic: it allows a client a certain number of requests per second, minute or day, and rejects the rest, usually with HTTP status 429 Too Many Requests. Limits protect the provider’s systems, so every integration that moves real volumes has to plan around them.

How does it work?

  1. The API counts requests per key, user, tenant or IP address.
  2. When the limit is reached, it returns 429, often with a Retry-After header.
  3. A well-behaved client waits, then retries with exponential backoff and jitter.
  4. Batching, pagination and incremental syncs reduce the number of requests needed.

Limits differ widely between vendors and are not always documented, so integrations should read them from response headers where available and be configurable rather than hard-coded.

Where it shows up in integrations

  • Full HRIS syncs The first sync of tens of thousands of employees can hit limits quickly.
  • Multi-tenant connectors Limits may apply per customer tenant, so one busy customer should not block others.
  • Bulk enrolments Enrolling a whole department in an LMS needs batching or queued requests.

Common pitfalls

  • Retrying immediately in a tight loop, which makes throttling worse.
  • Ignoring Retry-After and rate-limit headers the API provides.
  • Running full syncs when an incremental (“changed since”) endpoint exists.
  • Not monitoring for 429s, so slow syncs go unnoticed until data is stale.