RateHawk · Rate Limits

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, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests, concurrent_requests, and seconds.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Travel, Hotels, Booking, B2B, and Reservations.

4 Limits Throttle: 429
TravelHotelsBookingB2BReservationsRate LimitingQuotasThrottling

Limits

Per-Endpoint Limits (Overview) contract
requests
see Endpoints Overview
Enabled endpoints and their limits are returned by GET /overview/ per contract.
Search Concurrency contract
concurrent_requests
see provider documentation
Bound concurrent SERP / hotelpage requests per ETG best practices.
Request Timeout request
seconds
per-request timeout parameter
Search requests accept a timeout parameter that caps response wait time.
Booking Flow contract
requests
see provider documentation
Booking form / finish / finish-status polling cadence governed by best-practice guidance.

Policies

Contracted Limits
Limits are provisioned per partner contract and surfaced via the Endpoints Overview call.
Polling Strategy
Poll Order Booking Finish Status until processing reaches ok or a final failure status; avoid tight loops.
Backoff Strategy
Apply exponential backoff with jitter on throttling and transient errors.

Sources