Fetch Booking.com property search with priced room options, property details and guest reviews as structured JSON with one SocialCrawl API key. Reads are priced in credits.
3 active endpoints. Search, property and reviews.
Three read endpoints for public Booking.com data. Search a destination for priced properties, read one property's catalogue record, and page through guest reviews.
/v1/booking/searchAbout 25 properties a page for a destination. Each has its address, coordinates, star rating, review score out of 10 and count, photos, and every bookable room option priced in place.hotel.prices, with the meal plan and free-cancellation date in each row's title. Each page leaves out properties an earlier page already served. Standard tier (1 credit).
location, check_in, check_out, adults, children, rooms, cursor
/v1/booking/hotelOne property's catalogue record: address, coordinates, star rating, photos, amenities and the check-in and check-out windows. It does not price a stay, and the review score is left to the search row and the reviews route. Standard tier (1 credit).
id, url
/v1/booking/hotel/reviewsA property's guest reviews, up to 25 a page. Each has its score out of 10, title, what the guest liked and disliked, language, date, the guest's name and country, and the property's reply. data.total is the full review count. Advanced tier (5 credits).
id, url, limit, cursor
Returns Booking.com properties for a destination with address, coordinates, star rating, review score out of 10, photos, and every bookable room option with its price.
Use it to compare hotels and room prices in a city. Add check_in and check_out for your dates, or you get a default stay.
1 credit
location · A destination, for example Lisbon.
$ curl https://www.socialcrawl.dev/v1/booking/search?location=Lisbon \
-H "x-api-key: sc_YOUR_API_KEY"// Running this live needs your own API key. Hit "Try it" to see an example responseBooking.com is a normal SocialCrawl data surface. You call GET /v1/booking/… with an API key, spend credits on live misses, and get a single JSON envelope back.
Send your key in the x-api-key header. No Booking.com account or developer app is needed for public reads. The same key works across SocialCrawl platforms.
Search takes location and optional dates, guests and rooms. Property routes accept id or url. Dates are YYYY-MM-DD. Formats are validated before any charge.
Search and property detail cost 1 credit. Guest reviews cost 5 credits. Cache hits cost 0.
Every response is the same shape: success, data, credits_used, credits_remaining, request_id, cached. Lists also carry pagination when the route pages.
Most products find an entity first, then deepen into detail and reviews only when needed.
GET /v1/booking/search?location=…PlaceList with priced room options
Pass dates, guests and rooms to price the stay you care about.
GET /v1/booking/hotel?id=…Place with address, amenities and check-in windows
Take the property id from place.id on a search row.
GET /v1/booking/hotel/reviews?id=…ReviewList with liked and disliked text, up to 25 a page
data.total shows the full review count.
GET /v1/booking/search?location=…&cursor=…More properties for the same search
Pass the returned cursor; repeated properties are removed for you.
GET /v1/booking/search?location=Lisbon&check_in=2026-12-01&check_out=2026-12-05&adults=2
Host: www.socialcrawl.dev
x-api-key: sc_your_api_key_here
GET /v1/booking/hotel/reviews?id=pt%2Fmasa-5-de-outubro{
"success": true,
"data": {
"items": [
{
"place": {
"id": "pt/masa-5-de-outubro",
"name": "Example property",
"rating": {
"value": 8.9
},
"hotel": {
"prices": {
"total": 480,
"currency": "EUR"
}
}
}
}
]
},
"credits_used": 1,
"credits_remaining": 9999,
"request_id": "req_…",
"cached": false
}Field names match the rest of SocialCrawl where archetypes align. Parse once, reuse across platforms.
items[] with address, coordinates, stars, review score, photos, hotel.prices
address, coordinates, star rating, photos, amenities, check-in and check-out windows
items[] with score, title, liked and disliked text, language, date, guest country, responses[]
cursor plus data._warnings counting any repeated properties removed
Same request lifecycle as every other /v1 platform endpoint. Booking.com is not a sidecar.
Next.js catch-all routes into the Hono social API. We mint a request_id, authenticate the key, then enforce rate limit (600/min) and concurrency (50 in flight per key).
Registry lookup finds the booking route. Required params and format checks run first. Invalid input returns 400 with no charge. Valid calls debit the tier cost atomically before the read starts.
A deterministic cache key is built from platform + resource + params. Hit: return immediately, credits_used = 0. Miss: the public page is read live, with retries on 5xx or network errors and a circuit breaker if the source is unhealthy.
Booking.com data is mapped to the Place, PlaceList and ReviewList archetypes, validated against the canonical Zod schema, then wrapped in the success envelope and logged for billing audit.
Billing rules that matter in production
Booking.com is public read data. We normalize it into the SocialCrawl schema so your code does not learn a second vendor SDK.
Public property pages, search results with room prices, and guest reviews.
Public pages are read on request and normalized server-side. You never run a Booking.com login or booking session.
PlaceList and Place for properties and ReviewList for guest reviews.
No booking, messaging or partner tools.
The jobs this API is most often used for.
Hotel rate benchmarking and guest-review analysis
Callers search a destination first, then read the properties that matter and pull their reviews. Priced room options with meal plan and cancellation terms, plus guest reviews that keep liked and disliked text apart, in the shared Place and Review schemas.
Live misses read the public page on request. Repeat calls hit cache and cost 0 credits.
Common ways teams put this data to work, and the stack each one tends to run.
search with dates to compare room prices and cancellation terms across a market.
search with a cursor to sample how a destination is priced.
hotel/reviews to mine liked and disliked text by country and language.
Search is 1 credit. A page of reviews is 5. Cache hits are free.
curl "https://www.socialcrawl.dev/v1/booking/search?location=Lisbon&check_in=2026-12-01&check_out=2026-12-05&adults=2" \
-H "x-api-key: sc_your_api_key_here"curl "https://www.socialcrawl.dev/v1/booking/hotel/reviews?id=pt%2Fmasa-5-de-outubro" \
-H "x-api-key: sc_your_api_key_here"Same key as the rest of the catalog
Every endpoint returns structured JSON in a unified envelope. Computed fields such as engagement rate and content category are included only where the endpoint supports them and the required source inputs are present.
Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.
Contact usAsk AI about SocialCrawl