Expedia Affiliate Network
  • Home
  • Affiliate Program
  • Products
  • Developers
  • Travel Agents
  • About EAN
  • Blog
  • Support
  • Login
Open/Close Menu

Upgrade to Hotel API v3 with our Transition Guide

Posted by Kate Fetty on February 27, 2012 1 Comment
Tweet
Buffer

Want to upgrade to EAN’s Hotel API V3? The Transition Guide is here.

EAN Upgrade 224x142 Upgrade to Hotel API v3 with our Transition Guide

Our team of API experts has compiled a detailed upgrade guide to walk you thru the process of upgrading to API V3. The Version 3 Transition Guide is a succinct list of step by step instructions featuring each item that needs updated, revised or changed to upgrade from the old Hotel API (Version 200631) to our new smokin’ fast API Version 3.

The Transition Guide, located in the Developer Hub, provides diagrams of the required changes in each part of the user’s purchase path. The guide also includes an itemized list comparing each element, from each version, by each API call, so you know exactly what’s changed, what’s new and what’s been removed.  With the Transition Guide you will learn how to leverage some of the most important new features within the hotel list, room availability, and itinerary requests.

To get started, simply follow the steps outlined for a successful integration upgrade from start to finish.  Here’s a preview Jump right to the item you need, or browse from start to finish, from signing up for new version access to completing the final approval to launch.

1. First Steps

2. Search & Shopping Path

3. Product Selection

Get signed up, make test calls immediately, and prepare all global API changes.New Features
Getting Started
Global Changes
XML Sandbox
Follow the user through the entire shopping experience and leverage the most powerful EAN features yet.Hotel List Request
Hotel List Response
Geo Functions Request
Geo Function Response
Take advantage of new optional features to control the volume and type of data returned.Hotel Information Request
Hotel Information Response
Hotel Rooms Request
Hotel Rooms Response
Rate Rules Request
Rate Rules Response

4. Booking Path

5. Error Handling

6. Final Steps

Service the user through each step of the purchasing process, enhanced affiliate stats options, or creating your own customer service tools.Payment Types Request
Reservation Request
Reservation Response
Itinerary Request
Itinerary Response
Cancel Reservation
Manage ongoing troubleshooting with enhanced error messages handling ideas.Exception Messages
Alternate Properties Request
Alternate Properties Response
Debugging
Finalize the entire process by completing all launch requirements and requesting a site review for approval to launch.Launch Requirements
Approval to Launch
Hybrid Sites

 

If you have any further questions about upgrading, review our FAQs or visit the full Transition Guide in the EAN Developer Hub. We also have a downloadable quick guide available for you to take with you.

With such a thorough resource at your disposal, what are you waiting for? EAN API V3 is the platform for the future, so get started today so you don’t miss out on any of the upcoming enhancements.

 

Other Posts that may interest you

  • May 9, 2011 — EAN Insider Info: Our new Hotel API v3 (9)
  • October 7, 2010 — Top 10 Tips to drive ancillary hotel sales for Airlines (and train operators) (0)
  • September 30, 2011 — Congratulations API Hackday ATX Winners! (0)
  • September 13, 2010 — EAN WordPress travel site: 10-step guide to creating yours! (51)
  • August 9, 2012 — EAN’s API Made Easy – New White Papers (0)
 Upgrade to Hotel API v3 with our Transition Guide

About Kate Fetty

Kate Fetty is a Marketing Manager at EAN since early 2009 and focuses on product marketing and marketing communications. She has a passion for social media, mobile, and the future of API development. Kate enjoys live music and traveling the globe in her spare time.

Kate Fetty

Written by Kate Fetty

One Response

  • Mat

    I think I’m going to change to this.

    The Chameleon platform is very ‘buggy’.

    Take for example here http://tulumboutiquehotels.com/demo.html

    The search box is preloaded with my destination, but when you search it brings up Oaxaca, vallarta, and other wrong destinations. Sometimes its brings results for Tulum but often not. Very strange?

    March 21, 2012 at 5:58 pm

Leave a Reply

Click here to cancel reply.

Connect with us

Travel Affiliates on Google PlusTravel Affiliates on TwitterTravel Affiliates on FacebookTravel Affiliates on LinkedInTravel Affiliates on RSSJoin our Travel Affiliate Network

Categories

  • Best Practices (14)
  • Blog (2)
  • Conferences (6)
  • Content (3)
  • Contests (2)
  • CRO (1)
  • EAN Events (2)
  • Featured (45)
  • Guest Posts (1)
  • Integration (18)
  • Merchandising (8)
  • Mobile (3)
  • Products (2)
  • SEO (32)
  • Social Media (10)
  • Uncategorized (6)
  • Upcoming Events (9)

Top Authors

  • Louise Bell RSS feed (21)
  • Jose Truchado RSS feed (18)
  • Martin Macdonald RSS feed (13)
  • Jeff Slipko RSS feed (5)
  • Ira Ignatova RSS feed (3)
  • Lara Irwin RSS feed (2)
  • Charlie Ranlett RSS feed (2)
  • Kate Fetty RSS feed (2)
  • Lily Cheng RSS feed (2)

Top 10 Posts

  • EAN Wordpress travel site: 10-step guide to creating yours!
  • How to Create and Upload your Header and Footer in Chameleon
  • New URL masking Guidelines
  • Why White Label?
  • Uploading a Header and a Footer for Your Affiliate Site
  • Search boxes that you can brand
  • EAN Insider Info: Our new Hotel API v3
  • EAN's API Made Easy - New White Papers
  • What's in a CNAME?
  • How to Customize your EAN Search Box for a Niche Site I
Private Label & API:
  • Commissions & Payments
  • Integration & Samples
  • Merchandising Resources
  • Support
  • Developers
  • About EAN
  • Program Benefits

© 2002-2012 Expedia Inc. All Rights Reserved. Terms and Conditions and Privacy Policy EAN, ean.com, expediaaffiliate.com, Expedia Affiliate Network logo, ian.com and Interactive Affiliate Network logo are trademarks and/or service marks of Expedia, Inc.