GET
Hotel Search
/api/booking/search
Search Booking.com hotel listings by destination, dates, guests, and locale
Booking.com API
Booking.com Scraper API for Hotel Search and Hotel Data
Use Scrappa as a Booking.com scraper API for hotel search result cards, visible price text, dated availability signals, review score fields, images, and property-page metadata without maintaining your own browser scraper. Extract Booking hotel data through a simple REST API.
10
Endpoints
Booking.com
Source coverage
$0.20
Per 1k requests
Try it now
Make one request. Inspect structured JSON.
Use the first endpoint in this API family with a Scrappa API key. Every account includes 500 free monthly credits, so you can validate the response shape before buying credits.
Request preview
Request
curl -X GET "https://scrappa.co/api/booking/search?ss=Paris&checkin=2026-06-01&checkout=2026-06-04&group_adults=2&no_rooms=1" \
-H "Accept: application/json" \
-H "X-API-KEY: YOUR_API_KEY"
JSON response
{
"success": true,
"data": {
"title": "Paris: 7,421 properties found",
"canonical_url": "https://www.booking.com/searchresults.html?ss=Paris",
"h1": "Paris: 7,421 properties found",
"results": [
{
"name": "Ritz Paris",
"url": "https://www.booking.com/hotel/fr/ritz-paris.html",
"image": "https://cf.bstatic.com/xdata/images/hotel/square600/123456789.webp",
"review_score": "9.6",
"location": "1st arr., Paris",
"price": "$1,842"
}
],
"total_results": 7421,
"parsed": true
}
}What you can build
Structured data for real applications. Here are some ideas.
Hotel search
Search Booking.com by destination, dates, guests, rooms, currency, and locale to capture structured hotel result cards for travel dashboards and monitoring workflows.
Prices
Return visible price text from Booking.com result cards when prices render for the supplied dates and search parameters.
Availability signals
Use dated search result cards as availability signals for matching queries. The endpoint reports what Booking.com renders publicly, not guaranteed inventory or reservation holds.
Reviews
Capture public review score fields from search cards and aggregate rating data from property pages when those fields are present in the source HTML.
Property enrichment
Open a Booking.com hotel page and extract title, canonical URL, Open Graph metadata, JSON-LD hotel schema, and aggregate rating fields for catalog enrichment.
Booking.com scraper API
Booking hotel data API for search, prices, availability signals, and review score fields
The Booking.com scraper API is built for teams that need public Booking hotel data in JSON: search result cards by destination, visible price text, dated availability signals, individual hotel page metadata, review score fields, images, locations, and canonical property URLs. Instead of maintaining browser sessions, parser updates, and Booking.com-specific extraction logic, call Scrappa with an API key and connect the response to travel search, rate monitoring, catalog enrichment, or QA workflows.
Search Booking.com by destination, check-in date, check-out date, guests, rooms, currency, and locale.
Extract Booking.com review scores, location snippets, property images, visible price text, hotel URLs, canonical URLs, and metadata.
Treat dated result cards as availability signals from public Booking.com pages, not as confirmed inventory or reservation holds.
Use the hotel endpoint when you already have a Booking.com property URL, country, or hotel slug.
Use Booking reviews API fields from public pages for monitoring and enrichment without claiming first-party ratings.
Test the Booking.com scraper API with 500 free monthly credits before scaling production traffic.
Choose the right Booking.com API endpoint
Use Booking.com Search API for listing discovery
Run destination and date-based searches to capture result cards with hotel names, property URLs, image URLs, review scores, location labels, visible price text, and dated availability signals. This is the fastest starting point for hotel monitoring, travel inventory discovery, and Booking.com competitor research.
Open Booking.com Search API docsUse Booking.com Hotel API for property enrichment
Fetch a single Booking.com property page when you need canonical URL validation, Open Graph metadata, JSON-LD hotel schema, aggregate rating fields, review score data from the source page, or page-level QA checks for a known hotel listing.
Open Booking.com Hotel API docsAvailable endpoints
Everything you need in one API.
GET
Hotel Details
/api/booking/hotel
Extract hotel schema, metadata, and rating fields from a Booking.com property page
GET
Destinations
/api/booking/destinations
Resolve Booking.com destination ids and types from a destination query
GET
Search by URL
/api/booking/search-by-url
Parse a copied Booking.com search or destination URL into result cards
GET
Review Scores
/api/booking/review-scores
Extract aggregate review score fields from a Booking.com property page
GET
Photos
/api/booking/photos
Extract public image URLs from Booking.com property metadata
GET
Facilities
/api/booking/facilities
Extract rendered facilities, amenities, and policies from a hotel page
GET
Rooms
/api/booking/rooms
Extract visible room cards when Booking renders dated room availability
GET
Prices
/api/booking/prices
Extract visible price cards from dated Booking.com search results
POST
Bulk Prices
/api/booking/bulk-prices
Run up to two dated Booking.com price searches in one request
Related resources
Google Hotels API docs
Compare hotel inventory and price-comparison workflows from Google Hotels when you need multi-provider results in one response.
Google Hotels API overview
Compare Scrappa travel API options before choosing Booking-specific extraction or multi-provider hotel search.
Google Hotels autocomplete API docs
Resolve destinations and hotel names before calling Booking.com search flows in travel search interfaces.
Scrappa vs Booking.com Demand API
See how Scrappa compares to the official API.
| Feature | Scrappa | Booking.com Demand API |
|---|---|---|
| Setup complexity | API key only | Partnership approval |
| Property page metadata extraction | Limited | |
| Booking.com search result cards | Partnership inventory only | |
| Approval process | Instant | Weeks/months |
| Free tier | 500 credits/month | |
| Pay-as-you-go credit packs | ||
| Authentication | API key | Partner credentials |
Setup complexity
Scrappa:
API key only
Booking.com Demand API:
Partnership approval
Property page metadata extraction
Scrappa:
Booking.com Demand API:
Limited
Booking.com search result cards
Scrappa:
Booking.com Demand API:
Partnership inventory only
Approval process
Scrappa:
Instant
Booking.com Demand API:
Weeks/months
Free tier
Scrappa:
500 credits/month
Booking.com Demand API:
Pay-as-you-go credit packs
Scrappa:
Booking.com Demand API:
Authentication
Scrappa:
API key
Booking.com Demand API:
Partner credentials
Key features
Booking.com property-page extraction with JSON-LD hotel schema
Search result cards with hotel URL, image, review score, location, and price text
Dated search result cards that can be used as public availability signals
Destination, check-in, check-out, guest, room, language, and currency parameters
Canonical URL and metadata capture for QA and enrichment pipelines
Useful for Booking-specific monitoring without affiliate API access
Simple API key auth with 500 free credits per month
Frequently asked questions
You can extract Booking.com property-page metadata such as title, canonical URL, Open Graph fields, JSON-LD hotel schema, aggregate rating data, and hotel search result cards with names, URLs, images, review scores, locations, and visible price text.
Yes. The Booking hotel data API endpoints cover Booking.com hotel search result cards and individual property-page metadata. Use search for destination, date, guest, room, currency, and locale workflows, and use hotel details when you already have a Booking.com property URL or country and slug pair.
It returns dated search result cards when Booking.com renders them for the supplied query. Those cards can be used as public availability signals alongside visible price text, but Scrappa does not guarantee inventory, hold rooms, or perform booking transactions.
Yes, for review-related fields that are visible on public Booking.com pages. The search endpoint returns review score fields from result cards, and the hotel endpoint can return aggregate rating data found on the property page. Scrappa does not create or claim first-party reviews for your site.
The Booking.com Demand API is a partner product with approval requirements and account setup. Scrappa is designed for public-page extraction workflows and only needs a Scrappa API key, which makes it much faster to test Booking.com hotel and search data.
For best results, yes. Booking.com often redirects bare destination-only searches to an empty search form, so providing check-in and check-out dates improves result-card coverage and response quality.
Yes. The hotel endpoint accepts a full Booking.com property URL, or you can provide a country and slug pair if you already store Booking.com listing identifiers.
Yes. Every Scrappa account includes 500 free credits per month, so you can test Booking.com hotel and search extraction before buying credit packs or moving to a subscription.