Connect Book, Get Booking details, Get Booking List, Cancel

The Booking APIs are the final step in the Connect flow. Once the rate has been validated via Price, use these APIs to confirm the booking, retrieve booking records, and handle cancellations.

Book

Submit the booking by passing guest details, contact information, and payment info where required. The token from the Price response is mandatory — it tells Connect that the rate was validated before booking was attempted.

On success, the response returns a bookingId and a confirmation voucher to send to the customer.

⚠️ Always include the Price token. Attempting to book without it, or with a stale token from a previous Price call, will cause the booking to fail.

Guest information

How much guest information you need to collect depends on the allGuestsInfoRequired flag returned by the Price API:

If true — collect full details for every guest (name, age, document info where applicable). If false — lead guest details are sufficient.

Payment

Whether a card is required depends on the supplier and your account configuration. Check the cardRequired flag in the Price response. If true, pass payment details in the Book request. Zentrum Connect forwards the card directly to the supplier — it is not stored or charged by ZentrumHub.

POST https://hotel-connect.prod.zentrumhub.com/api/v1/book

Handling timeouts and ghost bookings

If the Book call returns a timeout error or a non-confirmed status, do not show a hard failure to the user. The supplier may still be processing the booking in the background.

Ghost booking recovery — polling flow

Book returns timeout (5002) or confirmation pending (5004).

Start polling Get Booking Details every 10–15 seconds.

Continue for up to 5 minutes (approximately 30 attempts).

If status returns Confirmed — proceed normally and show the customer their booking.

If still unconfirmed after 5 minutes — surface an appropriate error and contact ZentrumHub support with your correlationId.

Get Booking Details

Retrieve the full record for a booking using its bookingId. This endpoint serves two purposes: powering your My Trips or booking management page, and recovering from ghost bookings as described above.

GET https://hotel-connect.prod.zentrumhub.com/api/v1/book/{bookingId}

Get Bookings List

Retrieve a list of bookings made under your account. Useful for building booking management and reconciliation workflows.

GET https://hotel-connect.prod.zentrumhub.com/api/v1/book/getbookings

Cancel Booking

Cancel a confirmed booking by its bookingId. Only full cancellations are supported — partial room cancellations are not.

⚠️ Always show the user their cancellation penalty before triggering a cancel. The penalty rules are available in the cancellationPolicies from the Price response. Never cancel without the user seeing and acknowledging the fee.

DELETE https://hotel-connect.prod.zentrumhub.com/api/v1/book/{bookingId}

FAQs

Do I need to pass a credit card to complete the booking?

Check the cardRequired field in the Price response. If true, a payment card must be included in the Book request. Zentrum Connect passes it directly to the supplier — we do not store or charge it.

Do I need full guest details for all guests?

Check the allGuestsInfoRequired field in the Price response. If true, collect details for every guest. If false, lead guest details are sufficient for the booking.

What should I do if the Book call times out?

Do not show a hard error. Initiate the ghost booking polling flow described above — poll Get Booking Details every 10–15 seconds for up to 5 minutes. If the booking status comes back as Confirmed, it succeeded. If it remains unconfirmed after 5 minutes, treat it as a failure and contact support with your correlationId.

Full parameter details for all Booking APIs are available in the API Reference.