Skip to main content
The burst limit stops a key spending its whole minute in one second. The tenant limit is shared by every key the tenant holds, so a batch job and an interactive integration each get a key, and neither can starve the other of its own 300, but together they stay within 1,200. Every authenticated response carries:
  • RateLimit-Limit: the key’s requests a minute.
  • RateLimit-Remaining: what is left in the tightest window.
  • RateLimit-Reset: seconds until that window resets.
Over the limit, the answer is 429 with the problem type rate-limited and Retry-After, in seconds. A refused request still counts, so wait for Retry-After instead of retrying at once: a client that keeps hammering stays limited.
Reading a large directory is cheap at the right page size: ask for limit=500 and a first full read of 10,000 people is 20 requests. See Pagination.