Getting Started with Rapid
Getting started with Rapid is simple. Just get an API key and a Shared Secret, configure for Rapid Authentication, and begin testing.
1. Become a partner
You will need to become a partner in order to integrate with Rapid. If you haven’t done so yet, simply visit our sister site Expedia Partner Solutions and apply today.
2. Review our launch requirements, whichever are applicable to your website
Review the launch requirements to decide which requirements will require front end UI development and factor this into your project planning.
3. Prepare your environment
Review these resources to prepare your environment for using Rapid.
4. Get credentials and configure for Rapid Authentication
Once you have become a partner and been approved to integrate with Rapid, you will need to obtain your API key. You can do this by logging into EPS Portal and clicking Connectivity in the menu bar on the left. Then select API key from the options. You will be presented with your current API key details.
The API key is one of two key credentials required for Rapid's signature authentication system. You will also need your shared secret, which you can access by going into EPS Portal and navigating to the API Keys page. Your API key will be in a restricted development mode until you have been approved for launch to a production environment, after your site 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. Rapid 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.
5. Begin testing your requests
Once you have received your credentials and have configured for Rapid Authentication, you can start making requests against our testing endpoint, https://test.ean.com/. 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: To ensure a stable and maintainable service is delivered for all partners, rate limits are applied. The system monitors anomalous API traffic and will take action to protect itself automatically. Before making any planned changes to the behaviour of calling the API, or conducting performance tests with API access, make sure to review your plans with your Rapid Consultant.
Specifying your API version
Every request to the API service must specify the desired version by including the
basePath value immediately after the endpoint:
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
Example: Version 2.0 Swagger
host: api.ean.com basePath: '/2' schemes: - https produces: - application/json
6. Request a site review
Once you’re comfortable with your integration and have confirmed you meet the applicable launch requirements, ask your business development manager for a site review. When you're approved to go live, your business development 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.