Skip to main content
GET
Use this endpoint when you need the full booking record: itinerary pages, confirmation emails and vouchers, support tools, customer history and finance reconciliation. It sits at the end of the flow (search, rooms, prebook, book) and is how you read back what was booked.

Status, details or idempotency lookup?

Request example

Response example

booked_offer is the full offer object from rooms and prebook. It is shortened here to the fields used in this page.

Field guide

Offer and guests

References: which number to show

These three are different things. Do not treat them as interchangeable.

Lifecycle

Voucher

Cancellation

Confirmed details (supplier’s post-booking record)

data.confirmed_details is what the supplier reports after booking. It is null until that record has been read, for example while the booking is PROCESSING. It is separate from booked_offer, which never changes.
Booking details contain guest personal data and supplier confirmation information. Call this endpoint from trusted backend services only and limit who can see the data.
The Money object is always { amount_minor, currency, currency_exponent }. 17700 with exponent 2 is 177.00.

Next step

To cancel, use Quote Cancellation and then Cancel Booking.

Authorizations

x-api-key
string
header
required

Environment-specific API key created in the Unifystays portal

Headers

X-Unifystays-Contract-Version
enum<string>
default:2

Hotel API contract version. Optional: 2 is the current version and the default.

Available options:
2
X-Unifystays-Currency
string

ISO 4217 currency for display amounts (display_ledger, display_amount, commercial_display). Optional: defaults to your organization's display currency, USD unless configured. Read pricing.display_currency in the response.

Required string length: 3
Example:

"EUR"

Path Parameters

booking_id
string
required

Unifystays booking ID returned by Create Booking (ubk_...).

Example:

"ubk_eGQ0dW9uV1Vi"

Response

contract_version
string
required

Response contract version.

Example:

"2"

success
boolean
required

True when the request succeeded.

Example:

true

message
string
required

Human-readable summary. Do not parse it.

Example:

"Booking confirmed."

data
object
required

The full booking record.