Getting Started with EPS Rapid

1. Become a partner

You will need to become our partner in order to integrate with EPS Rapid. If you haven’t done so yet, simply visit our sister site Expedia Partner Solutions and apply today.

2. Get credentials & configure for EPS Authentication

Once you have become our partner and been approved to integrate with EPS Rapid, you will need to obtain your API key. You can do this by logging into your EPS Account and choosing API from the top menu bar. You will be presented with your current API key details:

The API key is one of two key credentials required for EPS Rapid's signature authentication system. You will also need your shared secret, which EPS 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 our 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. EPS 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 EPS 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 https://test.ean.com will not result in actual property 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.

IMPORTANT: The system monitors anomalous API traffic and takes actions to protect itself automatically. Work with your EPS Integration Consultant to review the plan before you change the behavior of calling API, or conducting the performance tests with API access.

Specifying your API version

Every request to the 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. When you're 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. EPS will not authorize a development API key for our production endpoint.