Rate limits

Each API key may send 600 requests per minute, with bursts of up to 100 requests. Above it the API answers 429 rate_limited with a Retry-After header in seconds: wait at least that long before retrying.

Request bodies are limited to 256 KB (413 payload_too_large).

429 Too Many Requests

HTTP/1.1 429 Too Many Requests
Retry-After: 2
X-Request-Id: 1a2b3c4d-5e6f-4a7b-8c9d-0e1f2a3b4c5d
Content-Type: application/json

{"error": {"code": "rate_limited",
           "message": "Rate limit exceeded for this API key; retry after the Retry-After header",
           "provider": null, "request_id": "1a2b3c4d-5e6f-4a7b-8c9d-0e1f2a3b4c5d"}}

Limits

Item	Value
Requests	600 per minute per API key, bursts up to 100
Request body	256 KB
Search: wait per provider	30 seconds (slower providers are reported as timeout)
Book: server-side limit	About 135 seconds
offer_token validity	24 hours from the search
booking_token validity	2 years from the booking

Recommended client behaviour

Topic	Recommendation
Concurrency	At most 5 concurrent searches and 2 concurrent bookings per key
Search frequency	Search when a customer asks. Do not poll search or use it to pre-fill caches.
Timeouts	Search 60 s; recheck, booking details and cancel 100 s; book 150 s
Retries	Exponential backoff (1 s, 2 s, 4 s; at most 3 attempts) on 429 (after Retry-After), 5xx and network errors. Book: only the identical request (Idempotency & retries).
Response size	Search responses can be 100 KB or more; each offer carries a token of about 1 KB