Type of acknowledgement record.

ID of the acknowledgement record.

Date when the acknowledgment record was last updated.

Whether the property is live on Expedia sites.

• An Expedia property is inactive if one of these conditions is true:

  • Payment issues or overdue invoices
  • Compliance issues due to regulatory or tax mandates
  • Recontracting or change of ownership
  • Incomplete onboarding
  • Renovations

• A Vrbo property (listing) is inactive if one of these conditions is true:

  • Property manager removed it from distribution
  • Marketplace violation occurred
  • Account is overdue
  • Minimum content is missing

Top-level property status derived from supporting checkpoints.

Grouping to which the field belongs, for UI layout purposes.

Description of the group, to be localized.

Whether the data is optional.

Field name for the information to be captured.

Description of the key, to be localized.

Subtype of data.

Description of the subtype, to be localized.

Type of data.

Description of the type, to be localized.

Lines that describe the physical street address.

State or province of the property.

Two-character ISO country code.

City or locality where the property is located.

Postal code of the address.

Identifier for additional information required by the district.

Value of the key required by the district.

Type of document referenced.

URL of the registration document file.

Travel start date for the exception (blackout) window in the YYYY-MM-DD format.

Travel end date for the exception (blackout) window in the YYYY-MM-DD format.

Beginning date of the booking window (in the YYYY:MM:DDThhh:mm:ss format, in the property’s local time zone).

End date of the booking window (in the YYYY:MM:DDThhh:mm:ss format, in the property’s local time zone).

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).

Fulfillment status.

Reason why the unit is in or out of compliance. The label used for the registration number in this string comes from the numberTypeLabel field on the RegistrationNumberRequirement type.

Whether the unit is compliant or not.

Latitudinal coordinates of property.

Longitudinal coordinates of property.

Beginning date in this format: YYYY-MM-DD

End date in this format: YYYY-MM-DD

Type of discount.

Unit of the discount. Currently, PERCENT is supported when creating or updating a discount. AMOUNT is supported for queries only.

Type of the discount.

Unit of the discount.

Exception (blackout) dates for which the promotion should NOT apply. This field is only returned when querying for a single promotion (by specifying the promotion ID).

Category of the promotion. Currently, only DISCOUNT_PROMOTION is supported (such as Priced Promotions).

Promotion code that travelers will use to apply the promotion. This field is returned in our booking APIs if a reservation is created for a product that has an active promotion. It is returned in PromotionCode for the Booking Notification API and in promoName for Booking Retrieval API. Note that only these characters are supported: ​​a-z, A-Z, 0-9, ., ,, ', :, !, ?, $, %, (, ), /, -, and space.

Detail of the discount being applied on the promotion.

Rate plans for which this promotion is applicable.

ID of the promotion stored in the Expedia platform.

Whether the promotion is negotiated. (Negotiated promotions cannot be updated.)

Name of the promotion.

List of restrictions that can be applied to these promotions.

Whether the promotion is currently bookable based on the its reservation date/time range. This field is supported in queries only. All dates and times are relative to the property’s time zone. The promotion may still be unavailable due to other restrictions. At the time of querying, if the promotion's bookingLocalDateTimeFrom and bookingLocalDateTimeTo values are in the past but the travelDateFrom and travelDateTo values are in the future, the promotion is considered expired because the promotion can no longer be made available.

Status of the promotion.

Description of the district regulation.

District ID (such as Miami Beach).

List of legal property types.

Localized district name that can be used for display.

Four-character locale code (language and country codes) of property's local district (such as fr_FR for a property in France).

URL to jurisdiction regulation infomation.

Whether registration is required by the jurisdiction. This is based on the geo code of the property’s address, not the property type (for example, registration may be required for a hotel but not a vacation rental in a specific area).

Jurisdiction regulations that the partner needs to meet to comply with onboarding.

ID of the rate plan stored in the Expedia platform.

Exemption type.

Description of the exemption.

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.

Reservation date and time being queries for. Format is YYYY-MM-DDThh:mm:ss, in the property’s local time zone.

Type of the discount. Currently, only single discounts are supported (flat discount percentage, such as 15% off).

ID of the promotion stored in the Expedia platform.

Status of the promotions.

Travel date window being queried for.

Guest's first (given) name.

Guest's last name (surname).

Phone numbers of the guest.

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)

Additional required regulation data by jurisdiction, such as license holder name or property address.

Exemptions of a requirement under certain conditions.

Whether this regulatory category is a vacation rental.

Maximum number of nights allowed by the jurisdiction. null means no requirement.

Minimum number of stay nights for this category (default is 1).

Regulation requirement that Expedia and Vrbo support.

List of registration number requirements.

Property regulatory category where the registration number requirements apply.

Localized string of the regulatory category.

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).

Legal property subtype, applicable for residences, such as primary home or secondary home. (This field provides the value that is specified in the registration:details:regulatorySubType field of the updateUnitRegistration mutation.)

Legal property type, such as hotel, bed and breakfast, residence, etc. (This field provides the value that is specified in the registration:details:regulatoryType field of the updateUnitRegistration mutation.)

Locale code used to localize the text, which conforms to the BCP-47 (RFC 5646) standard, such as fr-FR.

Localized text.

Annual night cap.

Whether the cap is enforced (or just informational).

Value of the applicable night to which the discount is applied. Permitted values are 2 to 28.

Whether the discount applied on the applicable night is recurring. For example, if applicableNight is set to 3 and isRecurring is set to true, the discount will be applied to the third, sixth, ninth nights (and so on).

Additional discount that is added to value for members only. For example, if value is 10, unit is PERCENT, and memberOnlyAdditionalValue is 5, members are offered 15 percent off.

Type of discount.

Unit of the discount. Currently, PERCENT is supported when creating or updating a discount. AMOUNT is supported for queries only.

Value of the discount applied.

Localized response text.

Date and time (in UTC, format: YYYY-MM-DDThh:mm:ssTZD) when this response was created.

Date and time (in UTC, format: YYYY-MM-DDThh:mm:ssTZD) when this response was updated.

Status of the response. The following values may be returned: APPROVED, BEFORE_SUBMITTED_FOR_MODERATION, QUEUED_FOR_LANG_DETECT, REJECTED, BEFORE_SUBMITTED_TO_ES, SUBMITTED, and REMOVEDBYCLIENT.

Be aware that reviews may be pending for up to 14 days depending on lodging partner actions and review content.

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

Whether additional pages can be retrieved.

Category of the promotion. Currently, only DISCOUNT_PROMOTION is supported (such as Priced Promotions).

ID of the promotion stored in the Expedia platform.

Whether the promotion is negotiated. (Negotiated promotions cannot be updated.)

Name of the promotion.

Whether the promotion is currently bookable based on the its reservation date/time range. This field is supported in queries only. All dates and times are relative to the property’s time zone. The promotion may still be unavailable due to other restrictions. At the time of querying, if the promotion's bookingLocalDateTimeFrom and bookingLocalDateTimeTo values are in the past but the travelDateFrom and travelDateTo values are in the future, the promotion is considered expired because the promotion can no longer be made available.

Status of the promotion.

Cursor value for this edge.

Node that references the promotion data.

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

Information about the current page of results.

Total number of promotions returned that meet the search criteria.

Status of the property on all platforms and property content.

Physical street address of the property.

Geographical location of the property.

Regulatory requirements and parameters that apply to the property. You can specify the locale argument to retrieve the results in a specific language; specify the four-letter ISO code for language. Use a four-character code that indicates language and region, such as fr_FR for French in France.

Expedia ID of the property.

Known IDs for the property 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.

Traveler-facing listing URLs of the property on the requested domains. Specify the domains argument (type: String!) and provide one or both of these values: expedia.com, vrbo.com. If you specify expedia.com, the API returns a listing URL if the property exists an Expedia site. If you specify vrbo.com, a listing URL is returned if the property exists on a Vrbo site.

Human-readable name of the property.

List of promotions that matches the specified arguments. You can specify these arguments:

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

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.

Reviews provided by travelers for the property that match the specified arguments. You can specify these arguments:

• filter (type: ReviewFilter), which provides additional arguments to filter the reviews that are returned by the query.
• pageSize (type: Int!), which is required and specifies the maximum number of reviews on each page (up to 10) returned by the response. For example, if there are 15 reviews on a property, you can retrieve two pages if this argument is set to 10 (page 1 includes 10 reviews, page 2 includes 5 reviews).
• after (type: String), which is the cursor from the previous query response that marked the end of the previous page of results.
• orderBy (type: ReviewsOrderBy), which provides the sort order of results; only one field should be specified. If not specified, reviews are sorted by review creation dateTime.

Collection of unit configurations available for the property.

Locale for the property listing on the requested domain.

URL if the property is enabled on the requested domain.

Category to which the rating applies:

• checkIn
• overall
• location
• communication
• onlineListing
• cleanliness
• roomCleanliness

Value of the rating, from 1 (terrible) to 5 (excellent).

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)

Additional registration information required by certain districts.

Checks the consistency of the information in our systems at the property level to determine whether the registration information is sufficient to fulfill the requirements of the property's district. We do not recommend including this field in the query because it does not provide the true value for some properties.

If false is returned for a unit, you can use the Product API to identify active units, though false may be returned for inactive units that have incorrect regulatory information.

Detailed registration information for the unit or room type.

Geographical jurisdiction identifier. For non-configured districts, this is null.

Acknowledgement records for the bookable unit. These are displayed to the traveler to confirm that they understand the regulatory requirements.

Additional information about the bookable unit required by certain districts.

Links for registration documentation files (if required).

Compliance status according to the local jurisdiction's regulatory requirements.

This object returns a non-compliant status for mandatory requirements only. If invalid information is provided for an optional regulatory requirement, or if regulatory information is set in a jurisdiction that does not require regulatory information, status: COMPLIANT will be returned. However, for optional requirements, a warning is returned in the warningStatus field when the data is set (using the updateUnitRegistration mutation).

Registration number displayed to the traveler.

List of exemptions for the property, such as maximum night cap.

Number of rooms in the bookable unit.

Registration records for the bookable unit filed with the governing jurisdiction.

Property classification category as maintained by the governing jurisdiction.

Regulatory category in the specified locale.

Property subtype, such as primary or secondary, or null if not applicable.

Property type, such as residence, condo, boat, etc.

Expedia ID of the unit or room type.

Note: We strongly recommend that you include this field in your implementation even though it is nullable. This field provides an audit trail for reporting purposes.

Whether pending applications are allowed to list.

Sample format string to use as an example for partners.

Whether the registration expiration date is required.

Whether the registration number is optional.

Localized display name (such as みんぱく for Japan Minpaku).

Registration number type. (This field provides the value that is specified in the registration:details:registrationRecords:registrationNumberType field of the updateUnitRegistration mutation.)

Label of the registration number.

Regex used to validate the syntax of the registration number.

Registration record expiration date in this format: yyyy-mm-dd

Registration record ID.

Type of registration/license.

Localized registration number type.

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.

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).

Contact information for the guest who made the reservation.

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.

Guest loyalty tier. Values include MEMBER, VIP, PREMIUMVIP, and null. You must include this field to complete certification.

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

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

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.

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.

Total number of guests associated with the reservation.

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. If a value add promotion (VAP) was not used, an empty array is returned. We strongly recommend that you include this field in your implementation.

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. 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.

Beginning of the date range (inclusive) when the reservation can be made in order for this promotion to be applicable. Format is YYYY-MM-DDThh:mm:ss, in the property’s local time zone.

End of the date range (inclusive) when the reservation can be made in order for this promotion to be applicable. Format is YYYY-MM-DDThh:mm:ss, in the property’s local time zone.

Whether a promotion is applicable only to members shopping on Expedia. The default value for this field is false.

Note that member-only badging is not applied to member-only deals that are less than 10%.

Whether this promotion is applicable only to travelers booking on the mobile device. This field is returned when querying for a single promotion only (by specifying the promotion ID).

Maximum number of days in advance of the reservation date for the promotion to be applicable.

Maximum duration of stay for which the promotion can be applicable. Maximum value is 28.

Minimum number of days in advance of the reservation date for the promotion to be applicable. The default value for this field is 0.

Minimum duration of stay for which the promotion can be applicable.

Start time for the same day for which the promotion is applicable (in the property’s local time zone). Applicable only for SAME_DAY_PROMOTION.

Beginning travel date for which this promotion is applicable in YYYY-MM-DD format.

End travel date for which this promotion is applicable in YYYY-MM-DD format.

Localized review text.

Brand to which the review belongs. Values include Aago, BedandBreakfast, CheapTickets, Ebookers, Expedia, HomeAway, Hotels, Lastminute, MrJet, Orbitz, Travelocity, Venere, VSC, and Wotif.

Date and time (in UTC, format: YYYY-MM-DDThh:mm:ssTZD) when this review was created.

Review ID.

Whether the partner can respond to the review. Reasons why a review is ineligible include:

• The review was imported and cannot be responded to
• The window within which a partner can respond has expired
• A response has been submitted and approved (moderated) and the partner is no longer allowed to submit a response

Date and time (in UTC, format: YYYY-MM-DDThh:mm:ssTZD) when this review was last updated.

Media URLs and caption uploaded with the review, if any.

Property IDs.

Review response submitted by the partner (using the setReviewResponse mutation).

Source of the review; values include PLATFORM and IMPORTED.

Overall rating for this review, typically on a 1-5 point scale.

Status of the review.

Localized review title (headline).

Date range when reviews were created.

Whether an owner or property manager response exists for the review.

Reservation details.

Expedia or Vrbo ID of the review.

Source of the review ID. To retrieve native reviews, specify PLATFORM. To retrieve imported reviews, specify IMPORTED.

Date range when reviews were updated.

First name of the traveler.

Last name (surname) of the traveler.

Image caption.

URL of the full image.

URL of the image's thumbnail.

Reservation check-in date.

Reservation checkout date.

Guest information.

IDs of the reservation.

Status of the reservation.

Review IDs and their sources.

Reservation ID.

Source of the ID.

Next page cursor for the next page of results (null if no more pages are available).

Review content, including each review's source, localized text, and reservation information to which it pertains.

Total number of reviews returned that meet the search criteria.

SSort order based on review creation dateTime in ascending or descending order.

Sort order based on review updated dateTime in ascending or descending order.

Sort order based on dateTime of when the owner response was created in ascending or descending order.

Sort order based on dateTime when the owner response was updated in ascending or descending order.

Sort order based on reservation check-in date in ascending or descending order.

Sort order based on reservation checkout date in ascending or descending order.

Value of member-only discount applied. For example, if the regular discount is 10% and memberOnlyAdditionalValue is set to 5, a member will receive a 15% discount and a non-member will receive a 10% discount.

Type of discount.

Unit of the discount. Currently, PERCENT is supported when creating or updating a discount. AMOUNT is supported for queries only.

Value of the discount applied.

Checkpoint specified by name. This field requires an argument: checkpointByName(name: String!). Refer to the name field below for the list of values that can be used.

Content requirement (checkpoint) that determines overall status. This field provides an optional argument, checkpoints(filter: CheckpointFilter), which enables you to filter the returned checkpoints by result. Refer to the CheckpointFilter type for details.

Number of checkpoint items associated with the property or unit, if quantifiable.

Whether the checkpoint conditions were satisfied. If false, the content requirement has not been met; verify that content is included in the Listings integration file for processing.

UTC time when checkpoint was last evaluated. This can help identify whether the data is stale if you see an unexpected status.

Maximum threshold allowed for the checkpoint to be satisfied, if applicable.

Minimum threshold required for the checkpoint to be satisfied, if applicable.

Checkpoint name. Here is the list of checkpoints that may be returned, by onbaording source. For information about the minimum requirements that must be met for each checkpoint, see Intro to property status.

Note: Not all checkpoints are included in every response, and this list may not be definitive. Assumptions about the presence of any of these checkpoints should not be built into logic.

For properties onboarded on Expedia, these checkpoints may be returned:

• BEXPropertyIsEnabledPredicate - Top-level checkpoint and "container" of all others.
• BEXHasPropertyOnboarded, which relies on the following required minimum content checkpoints are fulfilled and were provided by the partner during onboarding:
  • HasActiveImages
  • HasActiveRoom
  • HasAddress, which relies on the following checkpoints:
    • HasAddressLine1
    • HasAddressLine2
    • HasCity
    • HasCountry
    • HasPostalCode
    • HasProvince
    • HasValidatedAddress
  • HasAmenities (fulfilled by default)
  • HasBathroomType
  • HasBreakfast (for conventional lodging only)
  • HasBuildingFeatures
  • HasCheckInCheckOut
  • HasGuestFacilitiesAndServices
  • HasInternet
  • HasKitchen (for vacation rentals only)
  • HasKitchenFeatures (for vacation rentals only)
  • HasMandatoryFeesFacilitiesAndServices (for vacation rentals only)
  • HasParkingTransport
  • HasPaymentMethod
  • HasPets
  • HasPool
  • HasRoomLayout
  • HasBathroomCount
  • HasBedroomCount
  • HasBusinessModel
  • HasCheckInInstructions
  • HasContact
  • HasCurrencyCode
  • HasInventory
  • HasLatLong
  • HasPhone
  • HasPropertyName
  • HasPropertyTaxes, which relies on the HasLodgingTax checkpoint
  • HasRegulatory
  • HasStructureType
• BEXHasStopSellDisabled - No external services have set stop-sell on the property. This checkpoint is generated internally and cannot be updated by the partner.
• HasProviderConfigured - An active provider exists for the property. This checkpoint is generated internally by Expedia based on internal processes; it cannot be updated by the partner. Contact your Technical Relationship Manager if you have issues with this checkpoint.
• IsPCOOnboarded - The property has completed the prelive step of Partner Central Onboarding, which determines if the IsPCOPublishSubmitted checkpoint is required. This checkpoint is generated internally and cannot be updated by the partner, and it is not applicable for properties that were onboarded using the API.
• IsNotPCOOnboarded - The property has not completed the prelive step of Partner Central Onboarding. If this is fulfilled, IsPCOPublishSubmitted is not required. This checkpoint is generated internally and cannot be updated by the partner, and it is not applicable for properties that were onboarded using the API.
• IsPCOPublishSubmitted - The partner has clicked the "publish" button at the end of Partner Central Onboarding. This checkpoint is generated internally and cannot be updated by the partner.

For properties onboarded on Vrbo, these checkpoints may be met at the property level:

• IsPropertyLive - Top-level checkpoint and "container" of all others
• IsNotDeleted - The listing exists (is not deleted)
• HasNotCancelledSubscriptions - Listing subscriptions have not been cancelled (though a listing may be inactive for reasons other than cancellation, such as expired subscription)
• IsAccountNotDelinquent - The listing does not have violations
• HasBookableUnit - The listing has units that are enabled and bookable. However, a unit may be considered bookable by our system, though it may not actually be bookable for other reasons, such as being archived.
• IsActiveByOwner - The listing is not deactivated by the property manager
• IsListingNotArchived - The listing is not archived (archived listings are inactive, and they are not available in search of the Vrbo dashboard)
• IsActiveByCsr - The listing is not deactivated by a customer service representative
• HasActiveSubscription - The listing has a valid subscription and is active (though a listing may be inactive for reasons other than cancellation, such as expired subscription)
• HasActiveUnit - The listing has a unit and it is enabled. However, a unit may be considered bookable by our system, though it may not actually be bookable for other reasons, such as being archived.
• IsMinimumContentProvided - The listing has met the minimum content requirements
• IsPpbListing - The listing has the pay-per-booking (PPB) payment type defined
• IsNotPpbListing - The listing does not have the pay-per-booking (PPB) payment type defined
• IsPreviewListing - The listing has a product type of "preview"
• IsNotPreviewListing - The listing does not have a product type of "preview"
• IsRenewable - The listing is renewable
• IsSubscriptionBasedListing - The listing has payment terms (of type SUBSCRIPTION) defined
• IsTrustedPmListing - The listing belongs to a trusted partner
• IsUserNfmp - User is flagged as "not fair market practice"
• IsMerchantAccountNotRevoked - The listing's merchant account has not been revoked
• AdvertiserReadyToPublish - The listing's property manager has a valid publish date
• HasActivePPSV2Subscription - The listing has a valid subscription of type SUBSCRIPTION_V2
• HasCurrentEntitlements - The listing has a current active entitlement (entitlement is required for each listing's subscription)
• HasMatchingListProductType - The listing's product type matches the entitlement type
• HasPendingOrActiveSubscription - The listing has a pending or active subscription
• HasSubscription - The listing has a subscription

For properties onboarded on Vrbo, these checkpoints may be met at the unit level:

• HasUnitMinimumContentProvided - Top-level checkpoint and "container" of all others
• HasImages - Minimum content requirement of six images has been met
• HasBookingType - The booking policy is set for the property (INSTANT or QUOTEHOLD)
• HasLocation, which relies on these checkpoints:
  • HasValidatedAddress - Unit has valid, stored address and geolocation data upon lookup
  • HasGeoCode - Unit has valid and stored latitude and longitude
  • HasPropertyAddress - Unit has a valid and stored property address
• HasPropertyDetails, which relies on these checkpoints:
  • HasBathroom - Unit has at least one bathroom defined
  • HasMaxOccupancy - Unit has valid maximum occupancy defined
  • HasPropertyDescription - Unit has met minimum content requirement for a description
  • HasPropertyHeadline - Unit has met minimum content requirement for the headline
  • HasPropertyName - Unit has met minimum content requirement for the property name
  • HasPropertyType - A valid property type enumeration is defined
  • HasPropertyContact - At least one form of contact is defined for the property
• HasRates - Unit has met minimum requirement for valid and stored rates
• HasRegistrationNumber - Unit has a valid and stored registration number, if required by the property's jurisdiction
• HasHouseRules - House rules are defined for the unit
• HasCancellationPolicy - Cancellation policy is defined for the unit
• NotRegulatoryDelistRequest - Unit was delisted by regulatory operations

Ordered list of parent checkpoint nodes in the status calculation tree. If you need to reconstruct the tree, discover added context about a checkpoint, or make use of the checkpointByName field, then this information may be useful.

Status of the checkpoint retrieval.

Currency in which the amount is shown.

Rate type.

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.

Start date of the travel window (format: YYYY-MM-DD).

End date of the travel window (format: YYYY-MM-DD).

Status of the unit for Vrbo properties only. To check the status of Expedia properties (rooms), use the Product API as shown in this example.

Cardinality of this unit configuration on the property, for Vrbo properties only.

Expedia ID of the unit.

Known IDs for the property in the source system(s).

Registration information for the unit or room type. You can specify the locale argument to retrieve the results in a specific language; specify the four-letter ISO code for language. Use a four-character code that indicates language and region, such as fr_FR for French in France.