Get Hotel Details and Stay Prices
View all Booking.com Hotel & Travel Data endpoints →Retrieve a known numeric hotel_id with optional stay dates, adult count, child ages, room count, currency, and language. Hotel 180769 returned Hyatt Grand Central New York with status=true and message=Success. Observed data includes hotel_id, hotel_name, city_trans, countrycode, url, address, arrival_date, departure_date, currency_code, rooms, facilities_block.facilities, block, and composite_price_breakdown. Room blocks include block_id, occupancy, price breakdowns, and cancellation/prepayment policy text. Omitted dates used the documented current date through four days later; set both dates for reproducible comparisons. A nonexistent ID returned HTTP 200 with status=false, message=NO DATA!, status_code=400, and data=null. Check business status before reading hotel fields; NO DATA alone does not establish why another request failed.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/booking/get-hotel-details API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/booking/get-hotel-details?key=<API_KEY>&hotel_id=180769'
Query Result
Use Cases
- Enrich a selected search result with a property address, facilities, and available room context.
- Compare one known hotel across explicit stay windows without mixing occupancy settings.
- Validate a hotel identity against its name, city, country, and canonical property URL.
- Exercise success and NO DATA branches in a travel application without creating reservations.
Frequently asked questions
What dates apply when I omit checkin_date and checkout_date?
The documented defaults are the current date and the current date plus four days. The omitted-date probe returned 2026-10-18 through 2026-10-22; those were probe-time values, not permanent defaults. Set both dates for price research.
Why can this endpoint return NO DATA with HTTP 200?
Transport success and business success are separate. The observed nonexistent hotel returned message=NO DATA!, status=false, status_code=400, and data=null. The response does not identify a universal root cause for every NO DATA case.
Which ID belongs in hotel_id?
Use a numeric property ID, such as the verified hotel 180769 or an id from a hotel search result. The New York city UFI 20088325 and a properties-workflow detail_id are different identifiers.
Does a returned room price reserve that room?
No. This is a read-only detail request. Inspect the price breakdown, extra charges, occupancy, dates, and room-block policies; availability and price can change before a separate booking process.