booking.com APIbooking.com ↗
Search Booking.com properties by destination, dates, and guests. Retrieve names, prices, ratings, addresses, and descriptions via 2 structured endpoints.
curl -X GET 'https://api.parse.bot/scraper/347ab358-c792-4521-9ff2-bff0c7f845e0/search_properties?rooms=1&adults=2&offset=0&checkin=2026-05-20&checkout=2026-05-25&destination=Paris' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for properties on Booking.com by destination, dates, and guest configuration. Returns paginated results with property names, URLs, prices, and ratings.
| Param | Type | Description |
|---|---|---|
| rooms | integer | Number of rooms |
| adults | integer | Number of adults |
| offset | integer | Results offset for pagination (increments of 25) |
| checkinrequired | string | Check-in date in ISO format YYYY-MM-DD |
| checkoutrequired | string | Check-out date in ISO format YYYY-MM-DD |
| destinationrequired | string | Search destination (city, region, or property name) |
{
"type": "object",
"fields": {
"properties": "array of objects each containing name, url, price, rating, and address",
"total_found": "integer total number of matching properties"
},
"sample": {
"data": {
"properties": [
{
"url": "https://www.booking.com/hotel/fr/hotelwestminster.html?aid=304142&...",
"name": "Hotel Westminster",
"price": "$1,013",
"rating": "Scored 8.6 8.6Excellent 859 reviews",
"address": null
}
],
"total_found": 1370
},
"status": "success"
}
}About the booking.com API
The Booking.com API provides 2 endpoints for querying accommodation listings and fetching individual property details. Use search_properties to run destination-based searches filtered by check-in/checkout dates, room count, and guest count — getting back paginated results with names, prices, ratings, and addresses. Use get_property_details to pull full descriptive text and address data for any specific property by its URL.
Search Properties
The search_properties endpoint accepts a destination string (city, region, or property name), required checkin and checkout dates in YYYY-MM-DD format, and optional parameters for adults, rooms, and pagination via offset (increments of 25). Each result in the properties array includes the property name, url, price, rating, and address. The total_found integer tells you how many total results matched, allowing you to page through large result sets by incrementing offset.
Get Property Details
The get_property_details endpoint takes a single url parameter — a standard Booking.com hotel page URL such as https://www.booking.com/hotel/fr/opale-noire.html — and returns the property name, address (or null if unavailable), and description text. This is useful for enriching search results with the full prose description that Booking.com displays on the listing page.
Coverage and Limitations
Search results reflect availability for the date range and guest configuration you supply, so the same destination query can return different prices or availability on different calls. Pagination uses a fixed increment of 25 via the offset parameter; there is no cursor-based pagination. The get_property_details endpoint currently returns name, address, and description — it does not expose room-type breakdowns, amenity lists, photo URLs, or review text.
- Aggregate hotel prices for a destination across a date range using
search_propertiesprice and rating fields - Build a travel comparison tool that pages through all results using
total_foundandoffset - Populate a property database with addresses and descriptions via
get_property_details - Monitor price changes for specific Booking.com properties by querying
search_propertieson a schedule - Feed structured property names and URLs into an itinerary planning application
- Validate or enrich an existing hotel list by resolving Booking.com URLs to current names and addresses
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Booking.com have an official developer API?+
What does `search_properties` return for each property?+
properties array contains five fields: name (string), url (string linking to the Booking.com listing), price (string for the stay total or nightly rate as displayed), rating (string or numeric score), and address (string). The total_found integer at the top level reflects the full count of matching results across all pages.Does `get_property_details` return amenities, photos, or room types?+
name, address, and description text only. Amenity lists, photo URLs, room-type breakdowns, and cancellation policy are not part of the response. You can fork this API on Parse and revise it to add an endpoint targeting those fields.Can I retrieve guest reviews through this API?+
search_properties endpoint returns a rating value per property, but individual review text, review counts, and category scores are not exposed. You can fork this API on Parse and revise it to add a reviews endpoint.How does pagination work in `search_properties`?+
offset parameter, which increments in steps of 25. Each response includes total_found so you can calculate how many pages exist. There is no cursor or token — you advance through results by incrementing offset by 25 per call.