Rate limiting
Rate limiting facilitates a stable and maintainable service while ensuring the sustainable and cost-efficient use of Expedia Group systems.
What is rate limiting?
The Shopping API depends on a central inventory management system. As this system has finite capacity, it needs to be protected from over-utilization for the benefit of all partners and Expedia Group brands.
Traffic optimization is achieved by limiting the volume of traffic a partner can request to reasonable levels. These rate limits ensure the continued delivery of a stable and maintainable service to partners while also guaranteeing the efficient use of Expedia Group systems.
For Shopping API traffic, the significant factors for determining load are the number of hotels, the number of rooms, and the length of the stays being searched in each request.
Headers
To help you see the load your calls are creating, we include all of the following headers on as many responses as we can, but we cannot guarantee they'll be provided for every response.
| Parameter (header) | Description | Value |
|---|---|---|
Rate-Limit-Day-Remaining | Optional header for the remaining capacity, as a percentage, for the daily time window. | Number |
Rate-Limit-Day-Reset | Optional header for the timestamp, as the number of milliseconds since the Unix Epoch, when the daily capacity resets. | Number |
Rate-Limit-Minute-Remaining | Optional header for the remaining capacity, as a percentage, for the per minute time window. | Number |
Rate-Limit-Minute-Reset | Optional header for the timestamp, as the number of milliseconds since the Unix Epoch, when the per minute capacity resets. | Number |
Rate-Limit-Reduction-Status | Optional header that indications the state (inactive, active) of minute capacity reduction triggered once all daily capacity has been used. | String |