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

Hotel-to-block pairing Use room blocks returned for the same hotel rather than independent guessed block IDs.
Multiple selected block identifiers Pass documented comma-separated blockIds when reviewing more than one selected block.
Original stay carried forward Retain the exact stay and guest configuration associated with the block response.
Process information without purchase This GET endpoint is an informational step, not a reservation submission.

Live API Demo

GET /api/project/booking/detail-book-process-info

Request cost is temporarily unavailable. No price is assumed.

View pricing

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'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

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.

Related operations

Guides

View Subscription Plans →