Skip to main content
Booking.com endpoints require a paid plan (Starter or higher). Without one, these endpoints return 402 plan_upgrade_required. See Pricing for details.

​
Endpoints

  • GET /v1/booking/search — Search hotel availability for a destination and stay window.
  • GET /v1/booking/search/crawl — Queue a multi-page Booking search as an async job (up to 25 pages).
  • GET /v1/booking/property — Retrieve structured property details and per-room rates.
  • GET /v1/booking/reviews — Retrieve the review score breakdown, and individual review cards on request.

​
Point of sale

Booking’s prices vary by point of sale — the same room can quote differently depending on which country the request appears to originate from. Pass pos_country (a 2-letter ISO country code) to pin the request to a residential exit IP in that market. Without it, requests resolve through a default US-based identity.

​
Individual review cards

GET /v1/booking/reviews always returns the review score breakdown (staff, facilities, cleanliness, and more) from a plain page load. Individual review cards render behind a client-side panel that only populates after a click, so retrieving them requires a real browser interaction — set include_review_details: true to opt into that click-through. It’s billed as a separate interact session on top of the base fetch: 25 credits total instead of 15.

​
Hotel monitors

Watch a Booking.com property at fixed dates and occupancy, and get notified only when the price actually changes — including cross-provider rate-parity monitoring against Agoda. See Hotel Monitors.