Rate limits

Every API key is assigned a rate-limit tier. Limits are per-key, per-rolling-60-second window.

Tiers

Tier	Requests per minute
standard	60
premium	300
unlimited	10,000

Your tenant admin assigns a tier when issuing the key.

Headers

Every response includes:

Header	Meaning
X-RateLimit-Limit	Your bucket's max for the current window
X-RateLimit-Remaining	Requests left in the current window
X-RateLimit-Reset	Unix timestamp (seconds) when the bucket resets

When you exceed the limit

You get 429 Too Many Requests:

{ "error": "Rate limit exceeded. Try again later." }

X-RateLimit-Reset tells you when to retry. Sleep until then, then retry.

Best practices

• Honor Retry-After when present.

• Cache GET /api/v1/manifest, /catalog, /capabilities, and /pricing/resolve responses for at least 60 seconds — they don't change often.

• For batch jobs, prefer fewer, larger calls — use filter parameters (e.g. ?status=active, ?accountId=...) on list endpoints to fetch the rows you need in one request rather than many small ones.

• Webhook deliveries do not consume your API rate limit.

Tier upgrades

Ask your account team to lift your tier. Justify the request with expected RPS and burst patterns; we are happy to right-size.

Related

• Authentication

• Errors