Expedia

Features

• Availabilities
• Holds
• Bookings

Data Mappings

Expedia uses a CSV catalog.

Availabilities Notes

Expedia checks for Availabilities by date only. Redeam's Booking API responds to these requests with all valid Availabilities having a Start matching the date requested by Expedia.

Expedia Price Ingestion

In addition to availabilities, Expedia is now able to pull pricing information for Redeam-connected products.

PLEASE NOTE: RatePrices that are bound to Expedia's channel must meet the following conditions to be used by Expedia:

1. A retail Price must be set.
2. The retail Price's currency must match with Expedia's product catalog.
3. The TravelerType's name must contain one of the following strings (case-insensitive; if multiple matches are possible, the first matching element in the list below is used):

• Adult
• Any
• Child
• Infant
• Senior
• Student

The TravelerType's modifier must not bemilitary, as Expedia's Price Ingestion specification does not support this traveler type.

Concurrent Rates Not Supported

For a Product to be compatible with Expedia, there must be no more than one Rate valid or available on any given day. Expedia searches for Rates by Product and date; successful searches are expected to contain exactly one Rate object in their responses:

Multiple Rates cannot be applied to the same Product on the same day, even if they are not applied concurrently:

Consider a Product that introduces a Rate change between the afternoon and evening offerings for example - while it may be tempting to create the Rates so that they start and end at midnight (especially if they are specified without times), this will cause any Expedia queries requesting the Rate during the overlap day to fail:

Since Expedia searches by date only, this situation can only be resolved by splitting the offering into two distinct Products: