close

Sign in

To view secure documentation please login with EAN Service Desk, using the link below.

EAN service desk

No EAN Service Desk account?

Please contact your EAN representative

Login
Sign in
Rapid

Getting Started with EAN Rapid

There are three simple steps before starting development with EAN Rapid: get an API Key and Shared Secret, configure for EAN Authentication and begin testing your requests against our test endpoint.

1. Become a partner

If you haven't yet become an Expedia Affiliate Network partner, visit our sister site ean.com and apply today.

2. Get credentials & configure for EAN Authentication

If you are approved to integrate with the EAN Rapid API, you will need to obtain your API key by logging in to the Partner Portal.

Choose API from the top menu bar after you sign in, and you will be presented with your current API key(s) details:


The API key is one of two key credentials required for EAN Rapid's signature authentication system. You will also need your shared secret, which EAN Support will provide to you directly for security purposes. Your API key will be in a restricted development mode until your final launch review.

To make a request to an EAN Rapid API service, whether in test or production, you'll use the HTTP Authorization header to transmit your API key and an SHA-512 signature hash with each request. The SHA-512 hash consists of your shared secret, your API key, and a current UNIX timestamp. EAN Authorization headers always use the following format:

Authorization: EAN APIKey=yourAPIKey,Signature=sha512Hash,timestamp=yourUNIXTimestamp

See full details on our signature authentication page. You can use our signature generator tool to generate the SHA-512 hash value to test against your integration.

3. Begin testing your requests

Once you have received your credentials and have configured for EAN authentication, you can start making requests against our testing endpoint, https://test.ean.com.

The servers behind this endpoint are identical to our production servers, but any booking requests made against test.ean.com will not result in actual hotel reservations or credit card charges. You can choose from our documented Test headers for the booking API to control what type of response you want to see, or if you omit a Test header for any booking-related request, the test server will add one for you automatically.

Specifying your API version

Every request to a Rapid API service must specify the desired version by including the basePath value immediately after the endpoint:

https://test.ean.com/2/itineraries?…
https://api.ean.com/2.1/properties/22135/payment-options?token=U1dFC0JHTW

The basePath value is found at the top of our downloadable Swagger files and will always correspond with the version number for the given API service. Major versions will use the first numeral only (do not include .0).

Example - Version 2.0 Swagger

host: api.ean.com
basePath: "/2"
schemes:
- https
produces:
- application/json


4. Request a site review

Once you’re comfortable with your integration and have confirmed you meet the applicable launch requirements, ask your account manager for a site review. Once you are approved to go live, your account manager will enable your API key for production use. Simply switch your request endpoints from https://test.ean.com to https://api.ean.com and continue making requests - no additional code changes are required.

WARNING: If you receive 403 Forbidden responses after switching to https://api.ean.com, alert your account manager and ask them to verify your API key is enabled for the production endpoint. EAN will not authorize a development API key for our production endpoint.

New Release - EAN Rapid 2.1

EAN Rapid 2.1 has been fully released to production! Find out what's new or see our changelog details to get started. Rapid 2.0 documentation is still available via the version drop-down menu in the upper right corner of each doc page.