Date that defines the start of the checkout date window (format: YYYY-MM-DD).

Date that defines the end of the checkout date window (format: YYYY-MM-DD).

Currency in which the amount is shown.

Nightly rates for the reservation.

Rate type: NET for Expedia Collect or SELL for Hotel Collect.

Total rates for the reservation.

Guest's email address.

Guest's first (given) name.

Guest's last name (surname).

The traveler's Expedia Group VIP Access loyalty tier. These reservations often include value add promotions (VAPs), therefore it is important to associate this field and reservation:valueAddedPromotions in your systems so that end-users can properly identify loyal travelers and loyalty perks that the traveler is expecting. Values include MEMBER, VIP, PREMIUMVIP, and null. You must include this field to complete certification.

The phone numbers of the guest.

Details about the frequent traveler reward program. This field identifies if the traveler is a member of the supplier's loyalty program to ensure the supplier is able to greet the guest accordingly and award loyalty points as needed.

Purpose of the guest's reservation.

Area code (three digits).

Country code (two digits).

Phone number (seven digits, no hyphen).

ID in the source system.

Source of the ID.

ID in the source system.

Source of the ID.

Description of why the reservation is ineligible for reconciliation.

Reason why the reservation cannot be reconciled. Values include the following:

• GUEST_REQUESTED_CANCEL - Traveler cancelled the reservation
• NO_SHOW - Traveler was a no-show
• MODIFY_DATES_AMOUNTS - There was a difference in the booking price when the lodging partner charged the traveler (for example, because an extra night was added at the time of stay)

Starting date and time when the reservation was last updated (format: YYYY-MM-DDTHH:mm:ssTZD, TZD is a time zone designator in the form +/-hh:mm).

Ending date and time when the reservation was last updated (format: YYYY-MM-DDTHH:mm:ssTZD, TZD is a time zone designator in the form +/-hh:mm).

Value of the cursor of the last result on the current page.

Whether additional pages can be retrieved.

Text that is displayed to travelers if a payment type is associated with the reservation.

List of the property's reservations that match the specified arguments:

• filter (type: ReservationFilterInput), which enables you to refine the reservations to retrieve. If this argument is not specified, the query returns all reservations for the property.
• pageSize (type: Int!), which is required and specifies the maximum number of reservations on each page (up to 25) returned by the response. For example, if there are 40 reservations on a property, you can retrieve two pages if this argument is set to 25 (page 1 includes 25 reservations, page 2 includes 15 reservations).
• after (type: String), which is the cursor from the previous query response that marked the end of the previous page of results.

Reasons and descriptions why the reservation cannot be reconciled.

Reason why the reservation can be reconciled. Values include the following:

• GUEST_REQUESTED_CANCEL - Traveler cancelled the reservation
• NO_SHOW - Traveler was a no-show
• MODIFY_DATES_AMOUNTS - There was a difference in the booking price when the lodging partner charged the traveler (for example, because an extra night was added at the time of stay)

Accessibility requests made by the guest for the reservation. We strongly recommend that you include this field in your implementation.

Count for all adult guests associated with the reservation.

Bed type of the reservation.

Entity that collects payment for the reservation.

Check-in date (format: YYYY-MM-DD) of the reservation.

Checkout date (format: YYYY-MM-DD) of the reservation.

Ages of children associated with the reservation.

Count for all child guests associated with the reservation.

Timestamp of when the reservation was created (format: yyyy-mm-ddThh:mm:ssTZD, where TZD is a time zone designator in the form +/-hh:mm). Compare this value to that of lastUpdatedDateTime to determine if a reservation has been modified.

Expedia's reservation ID.

Whether one or more reconciliation attempts have been made on the reservation.

Date and time when the reservation was last updated. Compare this value to that of creationDateTime to determine if a reservation has been modified.

ID of message thread (conversation) associated with the reservation. This requires implementation and certification of the messaging capability. If no message threads exist for a reservation, null is returned.

Text that is displayed to guests if there is a multi-room booking associated with the reservation.

Guest payment details.

Guest who made the reservation.

ID of the rate/rate plan and the source of the ID. In the response, when idSource is set to SUPPLIER, the id field returns the same value as returned by the existing booking APIs. However, for Hotel Collect properties, the A- prefix is no longer added to the source value and the A suffix is no longer appended to the rate ID as was done by the booking APIs.

The reason(s) why the reservation can or cannot be reconciled.

Reconciliation type of the reservation, either MODIFY, CANCEL, NO_SHOW, or null.

IDs associated with the reservation and the source of the IDs.

Whether smoking is allowed for the reservation.

Source of the reservation. Refer to Booking sources for the list of possible values (though \"A-\" is not included in Hotel Collect sources returned by this API).

Text that is displayed to guests if there is a special request associated with the reservation.

Current status of the reservation.

Connectivity or lodging partner's amount for the reservation.

Travel Industry Designator Service (TIDS) code that allows a reservation to be recognized by industry suppliers.

Known IDs for the unit/room in the source system(s). IDs that are returned depend on where the property was onboarded:

• If the property was onboarded onto Vrbo, three IDs are returned: the partner’s (external ID), Vrbo’s (Vrbo internal ID), and Expedia's (EID).
• If the property was onboarded onto Expedia, only the Expedia ID is included in the response.

Value add promotion(s) used to book the reservation, which are additional benefits that travelers receive based on loyalty tier status, chosen property, and room type or rate plan they book. If a value add promotion was not used, an empty array is returned. We strongly recommend that you include this field in your implementation to ensure traveler-promised perks can be properly fulfilled by suppliers.

Cursor value for this edge.

Node that references the reservation data.

Checkout date window for which to filter reservations. Example:

checkOutDate: { from: "2021-08-05", to: "2021-08-07" }

Date and time when the reservation was last updated. Compare this value to that of creationDateTime to determine if a reservation has been modified.Example:

 lastUpdatedDateTime: {
    "from": "2022-03-02T10:23:17Z",
    "to": "2022-06-08T12:00:00Z"
  }

IDs of the reservations to retrieve. Example to retrieve two reservations based on their IDs:

reservationIds: [
  {
    "id": "123HotelCode",
    "idSource": "SUPPLIER"
  },
  {
    "id": "456HotelCode",
    "idSource": "SUPPLIER"
  }
]

Edges in the connection to traverse, each containing a cursor and node.

Information about the current page of results.

Total number of reservations.

Description of the promotion.

ID of the promotion.

Currency in which the amount is shown.

Rate type.

Accelerator percentage, expressed as a fraction of 1 (for example, 0.25).

Compensation base percentage, expressed as a fraction of 1 (for example, 0.25).

Traveler's membership number.

Reward program code.

Date when the rate becomes effective (format: YYYY-MM-DD).

Itemized list of fees.

Time unit of the rate.

Date when the rate expires (format: YYYY-MM-DD).

Amount of the fee.

Type of fee for this itemized rate.

Total amount of the fee after tax is applied.

Total amount of the fee before tax is applied.

Compensation information associated with the reservation.