Travel Redirect API Key
Travel Redirect API Key is assigned and configured as part of the Travel Redirect API onboarding process
What is a Travel Redirect API Key?
The Travel Redirect API key is a case-sensitive, alphanumeric string that looks something like this:
X99X9X9-99XX-9XX9-X999-99XX99X9X999X
Where does a partner get the Travel Redirect API Key?
An API Key will be sent to the partner as part of the API on boarding process.
How is the Travel Redirect API Key used?
The Travel Redirect API Key is required for accessing Travel Redirect APIs. The key is included in the header of each API request, and is used to authenticate the partner making the request. The standard Travel Redirect API Key authentication header element looks like this:
Key: X99X9X9-99XX-9XX9-X999-99XX99X9X999X
What does the Travel Redirect API Key do?
This key is a unique identifier that maps each API request to a single partner operating on a single Expedia brand on a single Expedia Point of Sale.
The string is always used in its complete form, and there is no situation where a partner would need to make any changes to the partner key, as use of the Travel Redirect API Key in an incomplete form will result in an API authentication error.
Keys and Deeplinks
The deeplink structure returned in the API response is directly tied to the Travel Redirect API Key. The Expedia brand to which the deeplink is directed, the point of sale of the site, as well as the structure of the deeplink itself are all managed by the configuration of the Travel Redirect API Key.
Why was I assigned more than one Travel Redirect API key?
Partners using the Travel Redirect APIs will have at least one Travel Redirect API Key. If the partner is operating on multiple points of sale, and/or if the partner is operating on multiple Expedia brands, they should have a different Travel Redirect API key for each unique combination of brand and Point of Sale.
In that situation it is up to the partner to ensure that the correct key is used in the correct situation.