Booking Details API

The Booking Details API retrieves full details of a booking made through ZentrumHub. It has two distinct use cases — one for normal product flows, one for error recovery. Implement both.

POST{baseEndpoint}/api/hotel/getBookingDetails

Two use cases

Use case 1

My Trips / Booking history

When a user views their past bookings, call this API with the bookingId to fetch full booking details — guest info, hotel, dates, rate, cancellation policy, and booking status.

Use case 2 — critical

Ghost booking recovery

If a Book API call times out or fails, poll this endpoint repeatedly before showing the user an error. The supplier may have completed the booking in the background after the timeout.

Ghost booking polling pattern

Polling parameters — after a Book failure or timeout

IntervalEvery 10–15 seconds

Maximum duration5 minutes (approximately 20–30 attempts)

Stop whenStatus is confirmed — show the user the booking confirmation immediately

After 5 minutesIf still unconfirmed, show an error and ask the user to contact support with their correlationId

Never show a hard booking failure without polling first. The Book API timeout does not mean the booking failed at the supplier end. Showing the user a failure screen when the booking is actually confirmed causes confusion and — if they retry — a duplicate booking that generates a debit note.

What the response includes

The full response contains everything needed to display a booking confirmation or trip detail page: hotel name, address, and contact details; check-in and check-out dates; room type and board basis; rate breakdown and cancellation policy; guest names; and current booking status.

ZentrumHub bookings only. This API only returns data for bookings made through the ZentrumHub Booking API. Bookings made directly on supplier portals are not accessible here.

Error codes

Code	Message
4001	Invalid data in request — refer to fields[] for details
5000	Unknown system error — contact support with the correlationId