Rate limits

Each API key has its own limit, set by the platform administrator on the API client (default 60 requests per minute). The window is a fixed one minute.

Every authenticated response carries:

Header	Meaning
`X-RateLimit-Limit`	Requests allowed per minute for this key
`X-RateLimit-Remaining`	Requests left in the current window
`X-RateLimit-Reset`	Seconds until the window resets

When exceeded you get 429 with error code rate_limited and a Retry-After header (seconds):

HTTP/1.1 429 Too Many Requests
Retry-After: 23
X-RateLimit-Limit: 60
X-RateLimit-Remaining: 0

{"error":{"code":"rate_limited","message":"Rate limit of 60 requests per minute exceeded","requestId":"…"}}

Good practice

Spread load; do not burst at the top of a minute.
Cache stable results (a search result is valid for 15 minutes via its offerToken).
On 429, wait Retry-After seconds, then retry.
Need a higher limit? Ask the platform administrator to raise it for your client.

A separate, generous per-IP ceiling protects the whole platform; ordinary integrations will not reach it.