$3/1K | Hotel Rates API - Booking, Expedia & Airbnb avatar

$3/1K | Hotel Rates API - Booking, Expedia & Airbnb

Pricing

from $10.32 / 1,000 calendar requests

Go to Apify Store
$3/1K | Hotel Rates API - Booking, Expedia & Airbnb

$3/1K | Hotel Rates API - 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 $10.32 / 1,000 calendar requests

Rating

0.0

(0)

Developer

ScraperCompany

ScraperCompany

Maintained by Community

Actor stats

0

Bookmarked

4

Total users

2

Monthly active users

3 days ago

Last modified

Features

Limited permissions

Share

Hotel Rates API - Google Hotels, Booking, Expedia, Airbnb

Hotel Rates API by ScraperCompany is the power-user Actor: it exposes every travel endpoint behind one input.

โญ Like this Actor? Leave a review

If Hotel Rates API saved you time, please leave a review on the Store. It takes a minute, helps other people find a scraper that works, and tells us what to build next.

๐ŸŸข Nothing to set up: no code, no login and no keys. Click Try for free, start a run, and export JSON, CSV or Excel, or pull the results through the Apify API. You pay only for results; failed and empty requests are free.

๐Ÿ“ฆ What you get

EndpointWhat you getPricePer 1,000
/v1/searchGoogle Hotels: find property token by name$0.003$3.00
/v1/calendarGoogle Hotels: price calendar (up to 330 nights)$0.012$12.00
/v1/serp/google_hotels_calendarGoogle Hotels: price calendar, SERP format$0.012$12.00
/v1/stayGoogle Hotels: price one stay window$0.008$8.00
/v1/offersGoogle Hotels: every OTA's offer for a stay$0.015$15.00
/v1/roomsGoogle Hotels: room matrix across OTAs$0.008$8.00
/v1/serp/google_hotels_propertyGoogle Hotels: property offers, SERP format$0.008$8.00
/v1/hotels/searchGoogle Hotels: destination search$0.006$6.00
/v1/serp/google_hotelsGoogle Hotels: destination search, SERP format$0.006$6.00
/v1/hotels/propertyGoogle Hotels: property details$0.008$8.00
/v1/hotels/resolveGoogle Hotels: resolve name with address$0.018$18.00
/v1/hotels/reviewsGoogle Hotels: reviews$0.003$3.00
/v1/officialOfficial hotel website rates$0.006$6.00
/v1/ota/bookingBooking.com: price calendar (up to 365 dates)$0.018$18.00
/v1/ota/booking/roomsBooking.com: rooms and rate plans$0.018$18.00
/v1/ota/booking/searchBooking.com: find hotel slug$0.006$6.00
/v1/ota/booking/reviewsBooking.com: reviews$0.003$3.00
/v1/ota/hotelsHotels.com: headline price$0.018$18.00
/v1/ota/hotels/roomsHotels.com: rooms and rate plans$0.018$18.00
/v1/ota/hotels/searchHotels.com: find property id$0.003$3.00
/v1/ota/hotels/reviewsHotels.com: reviews$0.003$3.00
/v1/ota/expediaExpedia: rooms and rates$0.018$18.00
/v1/ota/expedia/searchExpedia: find property id$0.003$3.00
/v1/ota/expedia/reviewsExpedia: reviews$0.003$3.00
/v1/ota/agodaAgoda: rooms and rates$0.018$18.00
/v1/ota/agoda/searchAgoda: find property id$0.003$3.00
/v1/ota/tripadvisorTripadvisor: OTA offers for a stay$0.018$18.00
/v1/ota/tripadvisor/searchTripadvisor: find location id$0.003$3.00
/v1/ota/tripadvisor/reviewsTripadvisor: reviews$0.003$3.00
/v1/ota/vrboVrbo: listing quote$0.018$18.00
/v1/ota/vrbo/searchVrbo: destination search$0.003$3.00
/v1/ota/hostelworldHostelworld: rooms and rates$0.018$18.00
/v1/ota/zenhotelsZenHotels: rooms and rates for a stay$0.018$18.00
/v1/ota/yanoljaNOL (Yanolja): rooms and rate plans for a stay$0.018$18.00
/v1/ota/yanolja/searchNOL (Yanolja): find stay id by name$0.003$3.00
/v1/ota/lastminutelastminute.com: headline price for a stay$0.018$18.00
/v1/ota/lastminute/searchlastminute.com: find hotel id by name$0.003$3.00
/v1/ota/compareCompare Booking.com, Hotels.com, Agoda, Expedia$0.045$45.00
/v1/serp/airbnbAirbnb: search$0.018$18.00
/v1/airbnb/calendarAirbnb: availability calendar with prices$0.018$18.00
/v1/serp/airbnb_property_availability_calendarAirbnb: availability calendar, SERP format$0.018$18.00
/v1/serp/google_flightsGoogle Flights: search$0.006$6.00
/v1/serp/google_flights_returnGoogle Flights: return / next-leg options$0.006$6.00
/v1/serp/google_flights_bookingGoogle Flights: booking options$0.008$8.00
/v1/serp/google_flights_calendarGoogle Flights: date-grid prices$0.009$9.00
/v1/serp/google_flights_location_searchGoogle Flights: airport/city lookup$0.003$3.00
  • ๐Ÿ’ต Price: from $3 per 1,000 search-request events ($0.003 each); failed and empty requests are free.
  • โš™๏ธ Setup: none. No account on the site, no cookies, no keys.
  • ๐Ÿ“ Export: JSON, CSV, Excel or HTML from the Output tab, or the Apify API.
  • ๐Ÿ” Automate: schedules, webhooks, Make, Zapier, n8n and AI agents (MCP).

โœจ What can this hotel rates scraper do?

Choose an endpoint (Google Hotels price calendar, OTA offers, destination search, Booking.com, Hotels.com, Expedia, Agoda, Tripadvisor, Vrbo, Hostelworld, ZenHotels, NOL (Yanolja), lastminute.com, 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.

  • 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; ZenHotels, NOL (Yanolja) in Korea and lastminute.com stay prices.
  • 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.

๐Ÿš€ Quick start: how to scrape hotel rates from every travel site

  1. Click Try for free (or open the Actor in Apify Console) and go to the Input tab.
  2. 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.
  3. Adjust the options if needed.
  4. Click Start and wait for the run to finish.
  5. Download the results from the Output tab as JSON, CSV, Excel or HTML, or fetch them with the Apify API.

๐Ÿ’ก Tip: run it once with the pre-filled input to see the output, then change the input to your own.

โš–๏ธ What makes it different?

Hotel Rates APIMany alternatives
SetupNothing to configure: no login, no keysOften your own accounts, cookies or network setup
You pay forSuccessful results; failed and empty requests are freeOften run time, or every attempt
When a request failsRetried automatically, and never chargedOften an empty or failed run

๐Ÿ‘ฅ Who uses 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?

FieldDescription
endpointEndpoint that served the request
inputThe exact body sent
(endpoint fields)Every field the endpoint returns, unchanged
request_id / billed / scraped_atTraceability and billing

Every dataset item also carries input (the options used for that request), request_id (quote it to support), billed and scraped_at.

โŒจ๏ธ Input

InputNameWhat it does
endpointEndpointEndpoint to call. The request body below uses that endpoint's field names; the dedicated Actors use the same names in their input forms.
bodyRequest body.g....", "days": 90}for the Google Hotels calendar. Date fields accept exact dates or relative ones such as"30 days"` from today.
requestsBatch of requests (advanced)......}}` objects, one request each, mixing any endpoints. When set, Endpoint and Request body above are ignored.

๐Ÿ“ฅ 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 all the fields):

{
"input": {
"token": "ChUIoben2Mv6-CYaCi9tLzA3czVwbjQQAQ",
"days": 30,
"currency": "USD",
"market": "US"
},
"coverage": "84/84",
"market": "US",
"observed_at": "2026-08-07T01:23:45.678Z",
"rates": [
{
"adults": 2,
"currency": "USD",
"fees": 25,
"implied_tax_rate": 0.203217,
"local_taxes_and_fees": null,
"los": 1,
"market": "US",
"provenance": {
"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"
},
"rate": 332.01,
"rate_base": 332.01,
"rate_including_vat": null,
"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": []
},
"vat_basis": "unknown",
"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 requests, not for compute time.

EventCharged whenPricePer 1,000
search-requestA search or lookup endpoint: property token, OTA id search, Vrbo search, airport lookup.$0.003$3.00
review-pageOne 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-pageGoogle Hotels destination search page, Booking.com hotel search, Google Flights search or return leg.$0.006$6.00
property-requestGoogle Hotels stay, rooms, property offers or details; Google Flights booking options.$0.008$8.00
official-requestRates from a hotel's own booking engine.$0.006$6.00
flights-calendar-requestGoogle Flights date-grid prices for one route.$0.009$9.00
calendar-requestGoogle Hotels price calendar (up to 330 nights).$0.012$12.00
offers-requestEvery booking site's offer for one property and stay.$0.015$15.00
ota-requestBooking.com, Hotels.com, Expedia, Agoda, Tripadvisor, Vrbo, Hostelworld rates; Airbnb search or calendar.$0.018$18.00
resolve-requestHotel name resolved to candidates with address and phone.$0.018$18.00
comparison-requestOne hotel compared across Booking.com, Hotels.com, Agoda and Expedia.$0.045$45.00
offers-pageGoogle Hotels calendar with mainstream basis or source spot-checks: one per extra offers page.$0.005$5.00
priced-nightOne Airbnb check-in date priced with Airbnb's own quote.$0.0015$1.50

The $3/1K in the title is the price of 1,000 search-request events, the cheapest mode; the table above prices every mode.

๐Ÿท๏ธ 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 15% 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.

Cost examples

JobCost
100 requests$0.30
1,000 requests$3.00
10,000 requests$30.00

Apify's $5 of free monthly usage covers about 1,666 search-request events.

  • โœ… Failed requests (errors, invalid input, a site refusing 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.

๐Ÿ”Œ Integrations

โฐ Schedules and webhooks

Use Apify Schedules to repeat a run hourly, daily or weekly and compare results over time, and webhooks or the Integrations tab to push new results to Make, Zapier, n8n, Google Sheets, Slack or your own warehouse.

๐Ÿค– AI agents and MCP

Results are structured JSON, so they are easy to feed to a model. AI agents such as Claude can run this Actor and read its results through the Apify MCP server.

๐Ÿ’ป API: JavaScript and Python

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 os
from apify_client import ApifyClient
client = 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)

โ“ FAQ

Do I need an account on the site, or an API key?

No. The Actor is ready to run as is, and 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.

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 fails?

Failed attempts are retried automatically. 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: it says what was wrong with the input, for example a malformed date or an unknown id. Fix it 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.

๐Ÿ“ Tried it? Tell others

Once you have run Hotel Rates API, a short review on the Store helps the next person decide.

๐Ÿ’ฌ 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. We read every issue.