Hotel Bookings

Manage the full hotel booking lifecycle: initiate a reservation, process payment, retrieve booking history, and handle cancellations.

Initiate Booking

POST /v1/hotel/booking/initiate

Create a reservation. Returns a booking_id used in all subsequent booking operations. The reservation is held for a short window while payment is processed.

curl -X POST 'https://cloud.vanitypass.com/v1/hotel/booking/initiate' \
  -H 'Content-Type: application/json' \
  -H 'X-Environment: Sandbox' \
  -d '{"room_id":"room_example","hotel_id":"htl_example","check_in":"2026-07-01","check_out":"2026-07-03","guests":{"adults":2,"rooms":1},"lead_guest":{"first_name":"Jane","last_name":"Doe","email":"jane@example.com"}}'

Pay for Booking

POST /v1/hotel/booking/pay

[!WARNING] Deprecated: This endpoint is deprecated. Use the unified checkout orchestrator endpoints (/v1/checkout/sessions and /v1/checkout/sessions/{id}) instead.

Initiate payment for a booking. Returns a payment intent or redirect URL depending on the payment method and gateway configured for your organisation.

curl -X POST 'https://cloud.vanitypass.com/v1/hotel/booking/pay' \
  -H 'Content-Type: application/json' \
  -H 'X-Environment: Sandbox' \
  -d '{"booking_id":"book_example","payment_method":"card"}'

List Bookings

POST /v1/hotel/booking/list

List bookings with optional filters. Returns a paginated list of hotel bookings for the organisation.

curl -X POST 'https://cloud.vanitypass.com/v1/hotel/booking/list' \
  -H 'Content-Type: application/json' \
  -H 'X-Environment: Sandbox' \
  -d '{"page":1,"per_page":20}'

Cancel Booking

POST /v1/hotel/booking/cancel

Cancel a booking. Returns cancellation policy details including any applicable fees and the expected refund timeline.

curl -X POST 'https://cloud.vanitypass.com/v1/hotel/booking/cancel' \
  -H 'Content-Type: application/json' \
  -H 'X-Environment: Sandbox' \
  -d '{"booking_id":"book_example"}'

Booking Object

Booking detail responses (from Get Booking Details / List Bookings) were enriched with structured guest, hotel-profile, and payer/payee fields. Every field below is nullable — treat any as absent if the supplier or catalogue did not provide it.