Ratehawk Rate Limits
The RateHawk / ETG pAPI v3 applies per-contract rate limits and per-endpoint settings that are returned to the partner via the Endpoints Overview call (GET /overview/). Limits and allowed request rates vary by contract and by endpoint (search vs. booking vs. content). ETG also recommends bounding the number of concurrent search requests and respecting the per-request timeout parameter. Specific numeric limits are issued per contract and are not reconciled in this artifact.
Ratehawk Rate Limits is the machine-readable rate-limit profile for RateHawk on the APIs.io network, in the API Commons Rate Limits shape.
It captures 4 rate-limit definitions, measuring requests, concurrent_requests, and seconds.
An exhausted limit returns HTTP 429.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Travel, Hotels, Booking, B2B, and Reservations.
generated, dated 2026-06-25.
Limits
Policies
Sources
- https://docs.emergingtravel.com/docs/best-practices-for-apiv3/
- https://docs.emergingtravel.com/docs/b2b-api/endpoints/
- https://docs.emergingtravel.com/docs/integration-guide/
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.