Getting startedReservations

Prerequisite: Availability and Rates API | Booking Notification or Booking Retrieval API

Intro to reservations

If a lodging partner is moving existing properties to a new connectivity solution or if the partner is onboarding for the first time, the Lodging Supply GraphQL API can facilitate the onboarding process. The reservations capability of the API enables a partner to retrieve reservations made on an Expedia Group point-of-sale. This API alleviates the need to manually export and import reservations by simply querying for a future checkout date window.

Download the launch kit here.

Note: This capability retrieves reservations for properties that were onboarded to Expedia sites only. Retrieving reservations for Vrbo properties is not supported at this time.

Comparison to booking APIs

If you have coded to the Booking Notification or Booking Retrieval API, be aware of these differences in the response attributes of this API:

Booking APIsReservations capability
Prefix the value in the source field with an "A-" to indicate that a reservation is Hotel Collect, such as A-Expedia or A-Hotels.comRemoves the prefix and provides the businessModel field so that partners can identify the collection model
Offer three types of transactions: original reservation, modified reservation, and cancelled reservation​Provides the status field, which currently only supports BOOKED and CANCELLED values
Bed types, smoking preference, multi-room reservation messages, and payment instructions are represented within SpecialRequests with unique request codes​Provides the bedTypes, smokingType, and multiRoomText fields, and the specialRequest field returns the traveler-specific requests for reservations​
Return the total amounts after tax along with the tax amountReturns the total amount after tax and the total amount before tax (a difference between the two indicates the tax amount)

In addition, the Lodging Supply GraphL API returns Unicode characters if the guest provided these in the reservation. This includes non-ASCII characters and non-English characters such as Chinese, Japanese, and so on, which could be included in guest names and special requests. Therefore, you must support all UTF-8 and Unicode characters.


Be aware of these limitations when implementing the reservations capability:

  • The reservations retrieval capability is read-only and returns a summary of a reservation. Write operations are not supported at this time.​

  • The following data points are not currently retrieved: credit card information, compensation, per-stay and per-person fees, and value add promotions.​

  • Only reservations for local inventory are retrieved.​

  • The state of a failed reservation cannot be changed once retrieved. If a reservation failed to be delivered by the Booking Notification or Booking Retrieval API, this capability enables you to retrieve these reservations, though modifications or cancellations to those reservations will be delivered using the secondary delivery method, such as email or fax.​

  • You can query for reservations based checkout dates. You cannot query for reservations based on booking dates.​