Hotel Rates API - Google Hotels, Booking, Expedia, Airbnb
Pricing
from $8.00 / 1,000 calendar requests
Hotel Rates API - Google Hotels, Booking, Expedia, Airbnb
One Actor for every travel data endpoint: Google Hotels calendars, offers and search, Booking.com, Expedia, Hotels.com, Agoda, Tripadvisor, Vrbo, Hostelworld, Airbnb, official hotel sites, rate comparison and Google Flights. Pick an endpoint, send a JSON body. Made by ScraperCompany.
Pricing
from $8.00 / 1,000 calendar requests
Rating
0.0
(0)
Developer
ScraperCompany
Maintained by CommunityActor stats
0
Bookmarked
3
Total users
1
Monthly active users
11 hours ago
Last modified
Categories
Share
Hotel Rates API by ScraperCompany is the power-user Actor: it exposes every travel endpoint behind one input. Choose an endpoint (Google Hotels price calendar, OTA offers, destination search, Booking.com, Hotels.com, Expedia, Agoda, Tripadvisor, Vrbo, Hostelworld, Airbnb search and calendars, official hotel websites, cross-OTA rate comparison, Google Flights) and pass its JSON request body; each item is the endpoint's response plus the request id. Batch many requests across endpoints in one run. Pricing is pay-per-event, by endpoint, from $0.003 per lookup to $0.045 per comparison (see the table below); failed requests are not charged.
Proxies, retries and anti-bot handling are built in, so you don't need your own proxies or an API key. Start a run, get structured JSON.
What can this hotel rates scraper do?
- 40+ travel endpoints in one Actor, each billed at its own price.
- Google Hotels: price calendars (330 nights), OTA offers, room matrix, stay prices, destination search, details, reviews.
- OTAs: Booking.com, Hotels.com, Expedia, Agoda, Tripadvisor, Vrbo, Hostelworld rates, rooms, search and reviews.
- Airbnb search and priced availability calendars; official hotel websites (50+ booking engines).
- Rate comparison across four OTAs, and Google Flights search, date grid and booking options.
- Batch mixed endpoints with requests; relative dates like
"30 days"work in any date field.
Endpoints
| Endpoint | What it returns | Price per request |
|---|---|---|
/v1/search | Google Hotels: find property token by name | $0.003 |
/v1/calendar | Google Hotels: price calendar (up to 330 nights) | $0.012 |
/v1/serp/google_hotels_calendar | Google Hotels: price calendar, SERP format | $0.012 |
/v1/stay | Google Hotels: price one stay window | $0.008 |
/v1/offers | Google Hotels: every OTA's offer for a stay | $0.015 |
/v1/rooms | Google Hotels: room matrix across OTAs | $0.008 |
/v1/serp/google_hotels_property | Google Hotels: property offers, SERP format | $0.008 |
/v1/hotels/search | Google Hotels: destination search | $0.006 |
/v1/serp/google_hotels | Google Hotels: destination search, SERP format | $0.006 |
/v1/hotels/property | Google Hotels: property details | $0.008 |
/v1/hotels/resolve | Google Hotels: resolve name with address | $0.018 |
/v1/hotels/reviews | Google Hotels: reviews | $0.003 |
/v1/official | Official hotel website rates | $0.006 |
/v1/ota/booking | Booking.com: price calendar (up to 365 dates) | $0.018 |
/v1/ota/booking/rooms | Booking.com: rooms and rate plans | $0.018 |
/v1/ota/booking/search | Booking.com: find hotel slug | $0.006 |
/v1/ota/booking/reviews | Booking.com: reviews | $0.003 |
/v1/ota/hotels | Hotels.com: headline price | $0.018 |
/v1/ota/hotels/rooms | Hotels.com: rooms and rate plans | $0.018 |
/v1/ota/hotels/search | Hotels.com: find property id | $0.003 |
/v1/ota/hotels/reviews | Hotels.com: reviews | $0.003 |
/v1/ota/expedia | Expedia: rooms and rates | $0.018 |
/v1/ota/expedia/search | Expedia: find property id | $0.003 |
/v1/ota/expedia/reviews | Expedia: reviews | $0.003 |
/v1/ota/agoda | Agoda: rooms and rates | $0.018 |
/v1/ota/agoda/search | Agoda: find property id | $0.003 |
/v1/ota/tripadvisor | Tripadvisor: OTA offers for a stay | $0.018 |
/v1/ota/tripadvisor/search | Tripadvisor: find location id | $0.003 |
/v1/ota/tripadvisor/reviews | Tripadvisor: reviews | $0.003 |
/v1/ota/vrbo | Vrbo: listing quote | $0.018 |
/v1/ota/vrbo/search | Vrbo: destination search | $0.003 |
/v1/ota/hostelworld | Hostelworld: rooms and rates | $0.018 |
/v1/ota/compare | Compare Booking.com, Hotels.com, Agoda, Expedia | $0.045 |
/v1/serp/airbnb | Airbnb: search | $0.018 |
/v1/airbnb/calendar | Airbnb: availability calendar with prices | $0.018 |
/v1/serp/airbnb_property_availability_calendar | Airbnb: availability calendar, SERP format | $0.018 |
/v1/serp/google_flights | Google Flights: search | $0.006 |
/v1/serp/google_flights_return | Google Flights: return / next-leg options | $0.006 |
/v1/serp/google_flights_booking | Google Flights: booking options | $0.008 |
/v1/serp/google_flights_calendar | Google Flights: date-grid prices | $0.009 |
/v1/serp/google_flights_location_search | Google Flights: airport/city lookup | $0.003 |
Use cases for hotel rates data
- Developers: Call every hotel, rental and flight endpoint from one Actor and one integration instead of wiring up a scraper per site.
- Revenue managers: Mix Google Hotels calendars, OTA prices and the hotel's own website in one scheduled batch.
- Data teams: Feed a pricing warehouse with raw JSON from many sources, each item tagged with its request id.
What hotel rates data can you extract?
| Field | Description |
|---|---|
endpoint | Endpoint that served the request |
input | The exact body sent |
(endpoint fields) | Every field the endpoint returns, unchanged |
request_id / billed / scraped_at | Traceability and billing |
Every dataset item also carries input (the exact request that was sent), request_id (quote it to support), billed and scraped_at.
How to scrape hotel rates from every travel site
- Open Hotel Rates API in Apify Console and go to the Input tab.
- Pick an Endpoint and write its Request body in JSON (the default prices a Google Hotels calendar for 30 nights). To batch, fill Batch of requests with
{"endpoint": ..., "body": ...}objects. - Adjust the options if needed. Dates accept an exact date (
2026-12-01) or a relative one (30 daysfrom today), so saved tasks and schedules never go stale. - Click Start and wait for the run to finish.
- Download the results from the Output tab as JSON, CSV, Excel or HTML, or fetch them with the Apify API.
Input example
This is the default input; running the Actor without changes prices 30 nights for the example Google Hotels property. A batch looks like {"requests": [{"endpoint": "/v1/ota/agoda", "body": {"property_id": "8795952", "check_in": "30 days"}}, {"endpoint": "/v1/ota/booking/search", "body": {"name": "Moxy Boston Downtown", "city": "Boston"}}]}.
{"endpoint": "/v1/calendar","body": {"token": "ChUIoben2Mv6-CYaCi9tLzA3czVwbjQQAQ","days": 30,"currency": "USD","market": "US"},"includeErrors": true,"maxConcurrency": 3,"maxRetries": 2}
Output example
One dataset item per request (trimmed here; real items contain every field the API returns):
{"endpoint": "/v1/calendar","input": {"token": "ChUIoben2Mv6-CYaCi9tLzA3czVwbjQQAQ","days": 30,"currency": "USD","market": "US"},"calendar_elapsed_s": 0.14,"collection_id": "ratecol_0123456789abcdef0123456789abcdef","coverage": "84/84","elapsed_s": 0.31,"market": "US","observed_at": "2026-08-07T01:23:45.678Z","rates": [{"adults": 2,"currency": "USD","fees": 25,"implied_tax_rate": 0.203217,"los": 1,"market": "US","provenance": {"collection_id": "ratecol_0123456789abcdef0123456789abcdef","derivation": "normalized_upstream","observation_id": "rateobs_0123456789abcdef0123456789abcdef","observed_at": "2026-08-07T01:23:45.678Z","price_basis": "room_base_before_taxes_and_fees","requested_currency": "USD","requested_market": "US","returned_currency": "USD","schema_version": 1,"source": "google_hotels_calendar","source_kind": "calendar","source_property_id": "ChUIoben2Mv6-CYaCi9tLzA3czVwbjQQAQ","upstream_rate_id": null},"rate": 332.01,"rate_base": 332.01,"rate_total": 424.48,"rates_include_tax": false,"stay_date": "2026-08-04","tax": 67.47}],"requested_days": 90,"tax_profile": {"implied_tax_rate": 0.2032,"rates_include_tax": false},"token": "ChUIoben2Mv6-CYaCi9tLzA3czVwbjQQAQ","unpriced_dates": ["2026-08-19"],"validation": {"ok": true,"problems": []},"request_id": "req_3f9c0d6e2b8a4c1f9e7d5b3a1c0e8f6d","billed": true,"scraped_at": "2026-10-01T14:03:27.512Z"}
A request that fails is saved with an error message instead (turn off Include failed requests to skip those). Failed requests are never charged.
How much does it cost to scrape hotel rates from every travel site?
This Actor uses pay-per-event pricing: you pay for successful API requests, not for compute time.
| Event | Charged when | Price | Per 1,000 |
|---|---|---|---|
search-request | A search or lookup endpoint: property token, OTA id search, Vrbo search, airport lookup. | $0.003 | $3.00 |
review-page | One page of reviews from Google Hotels (up to 10 per request, each charged), Booking.com, Expedia, Hotels.com or Tripadvisor. | $0.003 | $3.00 |
search-page | Google Hotels destination search page, Booking.com hotel search, Google Flights search or return leg. | $0.006 | $6.00 |
property-request | Google Hotels stay, rooms, property offers or details; Google Flights booking options. | $0.008 | $8.00 |
official-request | Rates from a hotel's own booking engine. | $0.006 | $6.00 |
flights-calendar-request | Google Flights date-grid prices for one route. | $0.009 | $9.00 |
calendar-request | Google Hotels price calendar (up to 330 nights). | $0.012 | $12.00 |
offers-request | Every booking site's offer for one property and stay. | $0.015 | $15.00 |
ota-request | Booking.com, Hotels.com, Expedia, Agoda, Tripadvisor, Vrbo, Hostelworld rates; Airbnb search or calendar. | $0.018 | $18.00 |
resolve-request | Hotel name resolved to candidates with address and phone. | $0.018 | $18.00 |
comparison-request | One hotel compared across Booking.com, Hotels.com, Agoda and Expedia. | $0.045 | $45.00 |
offers-page | Google Hotels calendar with mainstream basis or source spot-checks: one per extra offers page. | $0.005 | $5.00 |
priced-night | One Airbnb check-in date priced with Airbnb's own quote. | $0.0015 | $1.50 |
These prices apply from November 5, 2026, after Apify's 14-day notice of a price change; until then runs are charged the previous prices shown on the Pricing tab.
From November 5, 2026, paid Apify plans pay less: calendar-request up to 14% off, comparison-request up to 7% off, offers-page up to 15% off, offers-request up to 6% off, priced-night up to 20% off, resolve-request up to 13% off (Bronze 5%, more on higher plans). The Pricing tab shows the price on your plan.
Each endpoint is charged at its own price (see the table above). For example, 1,000 Google Hotels calendars cost $12.00, 1,000 Booking.com price calendars $18.00, and 1,000 property-token lookups $3.00.
- Failed requests (errors, invalid input, blocked upstream after retries) are free.
- Requests where the source returns nothing at all (no results, nothing priced) are saved but not charged.
- Set Maximum cost per run when you start a run and the Actor stops cleanly before going over it.
FAQ
Do I need proxies or an API key?
No. Proxy rotation, retries and anti-bot handling are built in, and the Actor is ready to run as is. You only pay the per-event prices above.
Where are the request fields documented?
The dedicated Actors (see Related scrapers) use the same field names in their input forms, and the batch example above shows the body format. A body with an unknown or missing field fails with a message naming the field, and failed requests are never charged. The body is passed to the endpoint unchanged (except relative dates, which are converted to YYYY-MM-DD).
Should I use this or a dedicated Actor?
Use the dedicated Actors (Booking.com, Google Hotels, Airbnb, ...) for guided forms and tailored dataset views. Use this one when you need several endpoints in one run or want to send raw request bodies.
Is it legal to scrape hotel rates from every travel site?
The Actor collects publicly available information that anyone can see without logging in. You are responsible for how you use the results: respect the source site's terms, copyright and privacy law (such as GDPR) and do not collect personal data without a lawful basis. If in doubt, ask a lawyer.
What happens when a request is blocked or rate-limited?
Rate limits (HTTP 429) and temporary errors (5xx) are retried automatically with exponential backoff, respecting Retry-After. If a request still fails it is saved with the error message and not charged, and the rest of the batch keeps going. A run only fails when every request failed.
Why did a request return an error?
Read the error field: validation problems (for example a malformed date or an unknown id) are reported exactly as the API sees them. Fix the input and run again; failed requests cost nothing.
How many requests can I run at once?
Any number per run. The Actor sends up to 3 requests in parallel by default (change it under Run options); larger batches simply take longer.
Use it from your code
Call the Actor from any language through the Apify API. With the JavaScript client (npm install apify-client):
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: process.env.APIFY_TOKEN });const run = await client.actor('scrapercompany/scrapercompany-hotel-rates').call({"endpoint": "/v1/ota/agoda","body": {"property_id": "8795952","check_in": "30 days","nights": 1,"currency": "USD"}});const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(items);
With Python (pip install apify-client):
import osfrom apify_client import ApifyClientclient = ApifyClient(os.environ["APIFY_TOKEN"])run = client.actor("scrapercompany/scrapercompany-hotel-rates").call(run_input={"endpoint": "/v1/ota/agoda","body": {"property_id": "8795952","check_in": "30 days","nights": 1,"currency": "USD",},})for item in client.dataset(run["defaultDatasetId"]).iterate_items():print(item)
You can also schedule runs, chain them with webhooks, or connect them to Make, Zapier, n8n, Google Sheets and other integrations from the Integrations tab.
Related scrapers
- Google Hotels Price Calendar Scraper: a ready-made form for forward rate calendars
- Booking.com Price Scraper: Booking.com price calendars and rooms without writing JSON
- Hotel Price Comparison: the same stay on several OTAs in one request
Support
Questions, a field you need, or a site that stopped working? Open an issue on the Issues tab. Include the request_id from the dataset item so we can trace the request.