Inspect Hotel Room Process Information
View all Booking.com Hotel & Travel Data endpoints →Make a read-only follow-up for hotel_id and one or more comma-separated blockIds obtained from data.block[].block_id in hotel details. Preserve the original dates, adults, child ages, rooms, and currency. The process-information response was not live-validated, so no checkout fields or confirmation identifiers are promised. Despite the operation name, this GET request does not create, pay for, or confirm a hotel reservation.
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/detail-book-process-info API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/booking/detail-book-process-info?key=<API_KEY>&blockIds=<blockIds>&hotel_id=180769'
Query Result
Use Cases
- Prototype a read-only review panel for a room block selected from hotel details.
- Check the documented process information associated with two shortlisted room blocks.
- Detect accidental cross-hotel block reuse in an accommodation integration test.
- Evaluate what process metadata is available before designing a separate reservation handoff.
Frequently asked questions
Where do blockIds come from?
Use block_id values in data.block from get-hotel-details. Keep those values paired with that response's hotel, dates, guests, and currency; the IDs are context-dependent.
Will this endpoint book or charge for the hotel?
No. It is a read-only GET for documented process information. Its response was not live-validated and must not be presented as a reservation or payment confirmation.