Booking.com Hotel Pages and Search Results in Structured JSON
Extract Booking.com hotel details and hotel search result cards through a simple REST API. Use Booking-specific property URLs, review snippets, price text, and hotel metadata without building your own Booking.com scraper.
What you can build
Structured data for real applications. Here are some ideas.
Hotel Search Monitoring
Track Booking.com search result cards for destination queries, date ranges, and guest configurations. Feed travel dashboards and hotel competitor monitoring pipelines.
Property Page Enrichment
Open a Booking.com hotel page and extract title, canonical URL, Open Graph metadata, JSON-LD hotel schema, and aggregate ratings for catalog enrichment.
Travel Lead Qualification
Validate that a hotel exists on Booking.com and capture listing metadata before pushing travel inventory into CRM, affiliate, or pricing workflows.
Hotel Landing Page QA
Monitor Booking.com hotel pages for metadata drift, broken schema fields, or content changes that impact downstream travel search and comparison experiences.
Available endpoints
Everything you need in one API.
Hotel Details
/api/booking/hotel
Extract hotel schema, metadata, and rating fields from a Booking.com property page
Hotel Search
/api/booking/search
Search Booking.com hotel listings by destination, dates, guests, and locale
Related API docs
Try it now
One API call. Structured JSON response.
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"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
}
}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 |
Key features
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 price text.
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.