Version 3 Home

Assets » Cheat Sheet » Database Catalogs

Hotels Version 3 is the most current, upgraded, and enhanced Hotel API.

The Legacy API Version 200631 will be completely removed on December 31st, 2012. Update NOW!

Beta vs. Live API Accounts

Hybrid Sites

All API Keys are in beta testing mode until their associated applications have been reviewe, approved and set for live bookings. All beta testing is done with CID 55505 from searching through booking.

Once all development has been completed and you are ready to make live bookings:

Log into your API account
Select the Site Review option under Applications.
We will contact you with the results of your review
Once the key/application/site has been approved, RESET all requests with your own CID associated with that key so that all sales are properly tracked.

Note: If your apiKey is not set for production access you will not be able to make any live bookings or be paid commissions.

You must be approved for access by following the Launch Requirements and using your own CID and apiKey in all requests once your apiKey is activated.
If you do not use your own CID and apiKey combination, only static bookings are created.
Static tests return generic confirmation numbers such as CF#1234.

Use a special combination of both the API and the EAN white label template to create a Hybrid Site.

Typically these sites use the API for shopping, searching and/or SEO landing pages but then transfer the user to the EAN template during the course of the booking path.

The user can be transferred at any point up to the actual booking page by using a deep link returned in the API.

Hybrid sites do not require you to obtain your own Secure Certificate to pass user Credit Card information.

Transition to Version 3

Question: If I'm updating from Verson 200631, can I transition to Version 3 requests one step at a time until I work my way through the complete booking process?

Answer: Absolutely! All requests are stateless, so you can work your way through the booking path one step at a time. You can benefit from using Version 3 immediately. Simply populate Version 200631 elements with the corresponding value from Version 3 response items as you work your way through the booking path.

For example, Version 3 rateKey is populated with Version 200631 hrnQuoteKey, Version 3 chargeableRate is populated with Version 200631 nativeRoomRate. To compare requests/results between the two versions, refer to the Cheat Sheet section for the appropriate comparison charts or follow the transition guide for step by step instructions. Use the guides for "mapping" all changes between the two versions.

Review the complete Step by Step Guide to quickly and easily transition from Version 200631 to Version 3.

More Translated Documents

Getting Started	Hotel API	Do it Right the First Time
Is the API for Me? Getting Started API Authentication Beta vs. Production Access Planning Your Integration The Development Life Cycle Manage Your Own IP Addresses	Hotel Version 3 Benefits and Features Service Resources Cheat Sheet XML Sandbox Tracking Sales Hybrid Sites Testimonials	Launch Requirements Best Practices Error Handling Properly Handling Data Transfers Agency Tutorial Venere Tutorial Test Booking Procedures How Do I...?
Version 3 Services	Version 3 Example Sets	Version 3 Objects
getList (Availability/Dateless) getGeoSearch getAvailability getInformation getRules getItinerary (One or Many) getAlternateProperties getReservation getPaymentInfo getCancel getPing	Hotel Lists Geo Functions Hotel Rooms Room Options: XML/REST/SOAP Agency Room Response Hotel Info Agency Rules Itineraries Alternative Properties Reservations Regional Tax Example	Common Request Elements Currency Options Language Options Minor Revision Numbers RateInfo Object Room Group Object Sorting Methods Amenity Mask Bed Types Value Adds Cancel Policy Info Credit Card Types
Version 3 Logical Diagrams	Version 3 Flow Charts	Hotel Assets
Hotel List Geo Functions Hotel Rooms Hotel Info Agency Rate Rules Hotel Itinerary Alternative Properties Hotel Reservation	Search Flow Chart Prodcut Selection Flow Chart Itinerary Options Flow Chart Typical Shopping Path Typical Booking Path	API Assets TripAdvisor Hotel Image Categorization Hotel Maps and Virtual Tours Customer Support Center Credit Card Currency Values
Database	Quick Reference	Self Help
Database Catalogs GeoData Files Schema Property Data Files Schema Room Data Files Schema Amenities Files Schema Database Tutorial	Entities and Special Characters URL Encoded Characters Color Charts Font Sizes	FAQs Debugging Guide API Authentication Resolution API Change Log & Updates Code Library SIG Generator Known Issues Current API Status Support

Manage Your Own IP Updates on Version 3

All affiliates are advised to start updating to the new Version 3 as soon as possible to prevent urgent transitions within your own schedules once a date is finalized and announced to remove Version 200631. In addition, you’ll enjoy great benefits in performance on the new version along with a long list of new features and enhancements.

You can manage your own IPs for Version 3 within your developer account by following this process once you have signed up for a Developer Hub account:

Sign in to your developer account.
- Each account is automatically assigned an API Key and gives you instant access to Version 3 when using CID 55505 and your API Key as outlined in the documentation.
Navigate to Applications => then click Edit
- Fill out the form with all the necessary information and be sure to include the CID and IP addresses to be associated with that API Key once you are making live requests.
- Do Not check the box within the Request for a Site Review instructions box until you have completed all development and are ready to launch your site.
IP authentication will not take place until your account is set for live access. When you are ready for a site review, Check the box and click SAVE.
- By checking the box, it will send a request to EAN to set this key for live access. We will respond back to you when it has been completed or if you have items to correct from the Checklist for Approval.
- Access on all keys have testing limits only until we approve them for live traffic. In the meantime, it will allow you to perform all development with limited API access.
Once your key is set for live access you can manage IP authentication from your developer account by updating the IPs in the Application page as needed.
- When making updates to your IPs, do not check the box when saving since you are not requesting a site review once your key has already been set for live access.
Send an API request from your program in order for the updated IP list in your developer account to transfer to your EAN Affiliate Account.

If you do not send an API requesst after updating your IP list, the IPs will not be updated in your affiliate record and API requests coming from the new IP will fail.

For reference, it takes about 20 minutes for the IPs to be recognized once they've been synchronized.

version 206 as of 3 days ago by Charlie

0 Comments

Please sign in to post a comment.