Rate limits

180 requests per minute, counted per organization and shared across every key that organization holds.

Creating more keys does not increase your allowance. The limit exists to bound one organization's total traffic, so it is attached to the organization rather than to the credential.

Endpoints with their own limit

Some endpoints cost far more to serve than a normal read, and carry a tighter limit of their own.

Endpoint	Limit
GET /v1/events/{eventId}/report	3 requests per minute

Headers

Every response tells you where you stand:

Header	Meaning
X-RateLimit-Limit	Requests allowed in the window
X-RateLimit-Remaining	Requests left in the current window
X-RateLimit-Reset	Milliseconds until the window resets

Pace your requests using X-RateLimit-Remaining rather than waiting to be refused. Because a few endpoints have their own limit, read these headers on every response rather than assuming the 180 applies.

Being throttled

Exceeding the limit returns 429 with a Retry-After header:

{
  "error": "rate_limit_exceeded",
  "message": "Too many requests.",
  "statusCode": 429
}