API Obsolescence Plan

The following plan outlines what we consider an acceptable process that will allow you to better manage your upgrades, as well it will allow Amadeus to introduce and to update any IATA mandates on a timely manner.
To move forward with new APIv2 product deliveries, you need to take into account two types of deprecations:

Proxy version deprecation
Verb deprecation

Proxy version deprecation

Our API development plan is to allow Amadeus to introduce four releases per year. The target months for these releases are for example January, April, July, October.

April 30 of Year N, all proxies delivered up to 31 December of Year N-2 will be rejected by the API gateway

Advantage:

You can take this process into account in your development and budget plans. We recommend that you make an effort to regularly upgrade the API version release used by your application. Anyhow you can select the first release of a calendar year and keep it for almost 2 years. However, if you wish to upgrade on a more frequent basis it will provide greater benefits by always running our latest functions and transaction.

A graphical representation of this rule

July 31, 2006	April 30, 2007	April 30, 2008
Suppress from Gateway all releases delivered up to December 2003 Proxy versions from 2.1.16.1 to 2.1.23.3 (included)
	Suppress from Gateway all releases delivered up to December 2005 Proxy versions from 2.1.24.2 to 2.1.31.0 (included)
		Suppress from Gateway all releases delivered up to December 2006 Proxy versions from 2.1.32.0 to 2.1.35.0 (included)

Please note that:

Deprecation of Proxy from version 2.1. 24.2 to version 2.1.31.0 (included) originally scheduled for April 30, 2005 is now planned for April, 2007.

Verb deprecation

List of impacted function calls:

Removed in Proxy#	Rejected in Test	Rejected in Production	Deprecated			Replaced by
Removed in Proxy#	Rejected in Test	Rejected in Production	In Proxy	Interface	Transaction	Interface	Transaction
34	June 2007	Nov 2007	<23	Fare	LowFareSearch	PoweredFare	LowFareSearch
			29	Air	SellFromAvailability	PoweredAir	SellFromAvailability
			29	PNR	CreateSeatRequest	PoweredPNR	AddMultiElements
			29	PNR	UpdateName	PoweredPNR	NameUpdate
			29	PNR	TransferOwnership	PoweredPNR	TransferOwnership
			29	PNR	CreateFreqFlyerRequest	PoweredPNR	AddFrequentFlyer
35	June 2007	Nov 2007
			<23	PoweredAir	Availability	PoweredAir	MultiAvailabilty
			29	PoweredHotel	Pricing	PoweredHotel	StructuredPricing
Proxy of Q4 2007	Jan 2008	Apr 2008
			32	FARE	DisplayFaresForCityPair	PoweredFare	DisplayFaresForCityPair
			32	FAREPLUS	DisplayFaresForCityPair	PoweredFare	DisplayFaresForCityPair
			31	Air	ModifyAirSegment	PoweredAir	RebookAirSegment
			31	FARE	DisplayLowestApplicableFare	PoweredFare	PricePNRWithLowerFare
			31	FARE	DisplayLowestPossibleFare	PoweredFare	PricePNRWithLowestFare
			31	FARE	PriceItinerary	PoweredFare	PricePNRWithBookingClass + PoweredTicket_ CreateTSTFromPricing
			31	FarePlus	DisplayLowestApplicableFare	PoweredFare	PricePNRWithLowerFare
			31	FarePlus	DisplayLowestPossibleFare	PoweredFare	PricePNRWithLowestFare
			31	FarePlus	PriceItinerary	PoweredFare	PricePNRWithBookingClass + PoweredTicket_ CreateTSTFromPricing
			29	Queue	PlaceOnMultiple	PoweredQueue	PlacePNR
			29	Queue	PlaceOnSingle	PoweredQueue	PlacePNR
			29	Queue	Count	PoweredQueue	CountTotal
			29	Ticket	CreateTST	PoweredTicket	CreateManualTST
			29	Ticket	DeleteTST	PoweredTicket	DeleteTST
			29	Ticket	DisplayTST	PoweredTicket	DisplayTST
			29	Ticket	UpdateTST	PoweredTicket	UpdateTST

Starting with Proxy-32, which will be the first Proxy to be relased in 2006, the traditional CAI_openConversationByCorporateID() and CAI_createConversationFactory functions will no longer exist.
If you want to benefit from the new functionalities introduced with the Proxy-32 and beyond, you have to migrate to the new method.

API GROUP