Skip to content

Data sources

Every source the API covers, what it is best for, and what it costs.

Overview

ScraperCompany collects rates from Google Hotels, eight OTAs and rental sites, Google Flights and 31 official hotel booking engines. Each source has different coverage, cost and latency. Credit costs below follow the credit schedule (metering is in beta; the API is free during the beta).

Google Hotels

Best for: Forward rate calendars and destination search

Nightly rates for up to 330 nights per call (90 by default) from Google's calendar data, per-seller offers and room types for a single night, and the hotels Google lists for a destination with their prices.

Credits: 5 per calendar call; 3 for stay, offers or rooms; 3 per destination-search page; 1 for property search
Endpoints: /v1/search, /v1/hotels/search, /v1/calendar, /v1/stay, /v1/offers, /v1/rooms

Characteristics

  • One calendar call replaces one request per night
  • Destination search returns about 20 properties per page with filters (price, rating, class, amenities) and their property tokens, ready for the calendar (guide)
  • Market and currency are selectable, and taxes/fees are normalized per market
  • Offers and rooms break a single night down by seller (OTAs and the official site)
  • SearchAPI-compatible shapes at /v1/serp/google_hotels, /v1/serp/google_hotels_calendar and /v1/serp/google_hotels_property

Booking.com

Best for: Booking.com's own prices and rooms

Resolve a hotel by name, then read Booking's own inventory: a multi-date calendar and the room and rate-plan grid.

Credits: 1 for search; 8 per calendar or rooms call
Endpoints: /v1/ota/booking/search, /v1/ota/booking, /v1/ota/booking/rooms

Hotels.com

Best for: Expedia Group inventory

Resolve a hotel to its numeric Hotels.com id, then price one date per call. Prices are specific to the point of sale, so compare like with like.

Credits: 1 for search; 8 per price or rooms call
Endpoints: /v1/ota/hotels/search, /v1/ota/hotels, /v1/ota/hotels/rooms

Expedia

Best for: Expedia's own rooms and rate plans

Resolve a hotel to its numeric Expedia id, then read every room type and rate plan for one stay: total, nightly price, cancellation terms and payment model. The point of sale (US or CA) decides the currency.

Credits: 1 for search; 8 per rates call
Endpoints: /v1/ota/expedia/search, /v1/ota/expedia

Agoda

Best for: Asia-Pacific coverage

Resolve a hotel to its Agoda id, then read Agoda's rooms and rate plans. Currency conversions are Agoda's own.

Credits: 1 for search; 8 per rooms call
Endpoints: /v1/ota/agoda/search, /v1/ota/agoda

Tripadvisor

Best for: Metasearch offers from several OTAs at once

The provider offers Tripadvisor shows for one stay window, by Tripadvisor location id. Name search is not available yet: take the location id from the hotel's Tripadvisor URL (the number after -d in /Hotel_Review-g…-d12345-…).

Credits: 8 per call
Endpoints: /v1/ota/tripadvisor

Hostelworld

Best for: Hostels

Dorm beds and private rooms with rate plans, by numeric Hostelworld property id. Currency is the property's own.

Credits: 8 per call
Endpoints: /v1/ota/hostelworld

Airbnb

Best for: Vacation rentals

Destination or map-area search with listing ids, prices, price breakdowns, ratings and cursor pagination, in SearchAPI's engine=airbnb shape; and a listing's day-by-day availability calendar with Airbnb's own quoted stay prices.

Credits: 8 per search; 8 plus 1 per priced night for the calendar
Endpoints: /v1/serp/airbnb, /api/v1/search?engine=airbnb, /v1/airbnb/calendar, /v1/serp/airbnb_property_availability_calendar

Vrbo

Best for: Vacation rentals on Vrbo

Search a destination for rentals with nightly and stay prices, then quote one rental by property id or by the listing id in its Vrbo URL (US market).

Credits: 1 per search; 8 per quote
Endpoints: /v1/ota/vrbo/search, /v1/ota/vrbo

Google Flights

Best for: Flight prices

Every itinerary Google Flights offers for one-way, round-trip and multi-city trips, with per-segment detail and price insights; return legs, booking options by seller, airport and city lookup, and a flexible-date price grid.

Credits: 3 per search, return leg or booking options; 1 per location search; 5 per calendar
Endpoints: /v1/serp/google_flights, /v1/serp/google_flights_return, /v1/serp/google_flights_booking, /v1/serp/google_flights_location_search, /v1/serp/google_flights_calendar

Official Hotel Websites

Best for: Direct booking rates and parity checks

The rate the hotel sells at on its own site. The booking engine is detected from the hotel's URL; 31 engines are supported.

Credits: 4 per call
Endpoints: /v1/official, /v1/official/engines

Characteristics

  • Returns the hotel's own rooms and rate plans
  • Latency depends on the engine, from well under a second to several seconds when a browser is needed; GET /v1/official/engines lists the cost per engine
  • Pair with OTA rates for rate parity monitoring

Guest reviews

Best for: Reputation monitoring and review analytics

Guest reviews from Tripadvisor, Booking.com, Expedia, Hotels.com and Google Hotels: rating, title, text, author, stay details, the property's reply and upstream labels like Verified review β€” page by page, each page with provenance.

Credits: 2 per page of any source; a page with no reviews is free
Endpoints: /v1/ota/tripadvisor/reviews, /v1/ota/booking/reviews, /v1/ota/expedia/reviews, /v1/ota/hotels/reviews, /v1/hotels/reviews

Characteristics

  • Ratings stay on each source's own scale (Tripadvisor 0–5, Booking and Expedia 0–10); compare via rating_scale
  • Google Hotels rows name their provider β€” Google mixes its own reviews with Tripadvisor's, Priceline's and others
  • Management replies, stay dates, room types and helpful-vote counts where the source publishes them
  • Upstream labels carried verbatim: "Verified review", "Liked: …" themes, "Verified Purchase"

Vertical engines (beyond travel)

Best for: News monitoring

Google's own RSS wire: keyword search or section feeds (world, business, technology…), newest first, up to 100 stories per page with publisher and canonical link.

Credits: 1 per page
Endpoints: /v1/news

Best for: SERP analytics and SEO

Google organic results, People Also Ask questions and the AI Overview text, rendered in a real browser. Google redirects resolve to destination URLs on request.

Credits: 5 per page
Endpoints: /v1/google/search

Best for: A second search engine, over plain HTTP

Bing organic results with titles, snippets and display URLs; click trackers are decoded back to destination URLs. Bing's related searches ride along.

Credits: 1 per page
Endpoints: /v1/bing/search

Best for: Local business data

Google Maps places search (name, address, coordinates, rating, phone, website, category) and place detail with the review count.

Credits: 3 per call
Endpoints: /v1/maps/search, /v1/maps/detail

Best for: Demand signals

Google Trends interest over time (0-100 relative to the keyword's own peak) and top/rising related queries with growth percentages.

Credits: 1 per call
Endpoints: /v1/trends/interest, /v1/trends/related

Best for: Retail price and assortment tracking

Google Shopping product cards (title, price, merchant, condition), Amazon search with point-of-sale pricing, Amazon ratings histograms with featured reviews, and Walmart search and reviews from the store's own JSON.

Credits: 3 Shopping; 1 Amazon/Walmart search; 2 reviews
Endpoints: /v1/shopping/search, /v1/amazon/search, /v1/amazon/reviews, /v1/walmart/search, /v1/walmart/reviews

Best for: Hiring and labour-market data

Google Jobs cards (title, company, location, publisher, posting age, employment type, apply sources) and Indeed job records (salary verbatim plus extracted range, posting age, company ratings) over plain HTTP.

Credits: 3 Google Jobs; 1 Indeed
Endpoints: /v1/jobs/search, /v1/indeed/jobs

Choosing the Right Source

Use caseRecommended
Forward rate calendar for many propertiesGoogle Hotels calendar (5 credits per property)
Per-seller breakdown for key datesGoogle Hotels offers (3 credits per night)
OTA price comparisonOTA compare (20 credits) or single OTAs (8 each)
Guest reviews for one hotelAny reviews endpoint (2 credits per page)
Confirm which hotel a token namesGoogle Hotels resolve (12 credits, with addresses)
SERP rank tracking, AI Overview monitoringGoogle search (5 per page) or Bing (1 per page)
Local business / competitor listingsGoogle Maps search + detail (3 credits each)
Retail price and assortment monitoringAmazon, Walmart and Google Shopping search
Rate parity monitoringOfficial site (4) plus OTAs
Hotels in a destination, with pricesGoogle Hotels destination search (3 credits per page)
Vacation rentalsAirbnb search and priced calendar, or Vrbo search and quotes

Data Freshness

  • Live endpoints collect from the source when you call them; responses say when the data was observed (for example observed_at on calendar responses).
  • Stored rates (GET /v1/rates/stored) return the latest stored observation with its freshness, without calling the source.

Cost tip

For routine monitoring, one Google Hotels calendar call (5 credits) covers up to 330 nights. Use offers (3 credits per night) and OTA endpoints (8 credits per call) only for the dates where you need seller-level detail.