Interface: PoweredAir

Introduction

The PoweredAir interface has been designed and implemented to facilitate the retrieval of seat map information, flight availability, schedule and timetable information, and to manage negotiated space inventories.

The AIR operations have been catagorised into the following functions:

MultiAvailability

Operations that will retrieve flight availability, schedules, and timetable information including dual city pair availability options.

CreateNegoSpace

Operations for allocating negociated space within the Amadeus system.

CreatePassiveNegoSpace

This function provides the capability to create passive negotiated space within the Amadeus system.

ChangeNegoSpace

Operation that will change exisiting negociated space elements.

CancelNegoSpace

Operations that will cancel existing negociated space elements.

DisplayNegoSpace

Operations that will return existing negociated space details.

RetrieveSeatMap

Seat maps may be requested for flights of Amadeus system user airlines and other airlines that hold an interactive seat map agreement with Amadeus.

FlightInfo

The Flight Information function provides Amadeus end-users with up-to-date information related to the operation of a particular flight before, during and after departure.

RebookAirSegment

The RebookAirSegment function enables you to rebook existing segments in a PNR.

Considerations

Limitations

At this time, there are no known limitations for the PoweredAir interface. Any limitations specific to a function are identified within the associated section of this document.

Unsupported Functions

Not applicable.

Prerequisites

There are no prerequisites to using the PoweredAir Interface. Any prerequisites specific to a function is identified within the associated section of this document.

Function: MultiAvailability

Overview

The MultiAvailability function provides operations to request the following flight information for participating airlines within the Amadeus System:

• Availability
• Timetables
• Schedules
• Scrolling

Supported Operations

Limitations

There are currently no limitations at this time.

Unsupported Operations

Not applicable.

Prerequisites

For the SevenDay search and ForwardScan option the Extended ownership security (EOS) must exist for the office as this controls the way that agents and offices can retrieve data created by other offices or Corporations.

The Specific Flight option requires an end of extended security agreement for the system user. This option is not supported for all users.

Building A Query

Depending on the flavor of the API that is used, each query will follow a given structure. The queries for the function operations are clearly explained with data element examples in a generic table view that can be adapted to the specific flavor of the API in use.

It is important to note that the examples in each chapter are only illustrations and are meant to provide the basis for a better understanding on which fields are mandatory for basic operation utilization. It is not a full explanation of every field that can be utilised for the operation, but rather a guideline to its use.

Receiving A Reply

MultiAvailability specific

ActionCode

This field must contain the type of request using the relevant codeset.

SubActionCode

This field is mostly use in a scrolling entry in a dual context, to specify to which part of the display the scrolling must apply (it can be the first part, the second part or both).

TypeOfRequest

It is possible to determine the type of display for the reply by changing the value specified for the data element typeOfRequest for a MultiAvailability display. In the extract from an Operation example listed below, it has specified the values 'TN' for a neutral display and TT for a Negotiated Space display. However, it can be replaced with one of the other options listed below:

MultiAvailability Display options:

It should also be noted that the order in which flights appear on an availability display depends on the type of availability you request and (for all types) the regulations that apply in your own market.

For the Negotiated Space Availability the displays are ordered by departure time in ascending order.

There are four different flight types:

Non-Stop Flight

A flight with 'NO' intermediate stops, and the same flight number and aircraft - EU flights shown by Departure time (earliest to latest).

Direct Flight

A flight with intermediate stop(s) and the same flight number and aircraft - EU flights shown by Elapsed flight time (shortest to longest).

Connecting Flight

a flight with intermediate stop(s) and a change of flight number and aircraft - EU connecting flights are shown by Elapsed flight time and they include flights with an equipment change en route.

Change-Of-Gauge

Connecting flight with intermediate stops and change of aircraft EU display the COG as connection.

European Union regulations apply in most Amadeus markets except the US NMC.

Order of flights on US (DOT set to yes in the office profile) displays. The order of flights described below applies to all types of Availability Display, except that within each category Direct flights or 2-segment Interline connections; for example, flights are sorted according to the display type. Such as, by Departure time, rather than Elapsed flight time, for a display by Departure time. Flight categories are never mixed.

1. Non-stop flights, by departure time (earliest to latest)
2. Direct and change-of-gauge flights, by Elapsed flight time (shortest to longest). Change-of-gauge flights shown on one line with EQV as the equipment code.
3. 2-segment online connections, by Elapsed flight time
4. 2-segment interline connections, by Elapsed flight time
5. 3-segment connections, by Elapsed flight time. No sorting between online and interline to default to the DOT display, US NMC users must have the 'dept of transport dsply' indicator set to 'yes' in their office profiles.

Reply Structure

The actionCode 45 indicates that this is a reply to an Availability request.

Error Messages

Operation: MultiAvailability Request

Simple availability with connection location, BKK.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Basic Request With Selected Carrier

Basic Multi-Availability Request with a Selected Carrier, AF and DL.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Connection & Class of Service

MultiAvailability with connections and class of service selected.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Class Of Service & Carrier

MultiAvailability with different class of services selected and more than one carrier selected

Query Structure

Possible Errors

See "Error Messages" section

Operation: Negotiated Space in a Neutral availability Request

MultiAvailability with one class of services selected and one carrier. In the folowing example all optional fields have been completed to illustrate all of them.

Query Structure

Possible Errors

See "Error Messages" section.

Operation: Negotiated Space dedicated availability Request

MultiAvailability with one class of services selected and one carrier In the folowing example all optionals fields have been completed to illustrate all of them.

Query Structure

Possible Errors

See "Error Messages" section.

Operation: Seven Day Search

The 7-Day search request option is available to all users. The 7-Day Search mode is not allowed for TimeTable. The actual search period is up to eight days, input date plus seven days. When no flights have been found during the 7-Day search process warning messages are issued.

This excerpt shows the entry used for a query illustrating the departure Date 051201 The type 'SEV' indicates that this is a seven day search.

Note: the format of the date is six characters - if you enter the date format incorrectly, you will receive erroneous results, such that the first available date is greater than the seven days limited to this option.

Hence, the first first flight available is the very next day 06dec.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Forward Search

ForwardScan uses the same option as the 7-Day search, the difference is that when an argument is added such as to specify the number of days - this automatically converts the query to ForwardScan. Maximum number of days scanned is 31 days. Carrier Preferrred AND Extended Ownership is mandatory to use this function and ForwardScan is restricted to City Ticketing Office (CTO) or an Airport ticketing Office (ATO).

This excerpt shows the entry used for a query illustrating the departure Date 051201 The type 'SEV' indicates that this is a seven day search, however when the argument is added the search expands and subsequently the search turns into a ForwardScan.

Note: the format of the date is six characters - if you enter the date format incorrectly, you will receive erroneous results, such that the first available date is greater than the seven days limited to this option.

Hence, the first first flight available is the very next day 06dec.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Basic Schedule

Basic example using a schedule request.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Complex Schedule

A complex example using a schedule request.

Query Structure

Possible Errors

See "Error Messages" section

Operation: More Complex Schedule

More complex example using a schedule request.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Schedule For A Specific Flight

The following illustrates a schedule request for the specific flight of BA 009 from London to Sydney on 25June2002 departing at 0100;

Note: this option is not supported for all users and is restricted to specific users with extended security agreements only.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Simple Timetable

Simple time table request.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Timetable With Airline Option

Simple timetable airline option request.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Request scrolling (MD) on previous entry

Scrolling on previous simple availability display

Query Structure

Possible Errors

See "Error Messages" section.

Function: CreateNegoSpace

Overview

The ability to create active or interactive negotiated space is dependent upon an extended ownership security (EOS) agreement between the airline and agency. Only specified agents are authorized to create the negotiated space on behalf of the airline.

This function provides the capability to create active or interactive single date negotiated space. Active or interactive Negotiated space may be created in two manners;

Single negotiated space

Single negotiated space is one that is created for a particular flight number, board-off point, and owner for a single date of operation.

Multiple negotiated space **NOT YET IMPLEMENTED**

Multiple negotiated space is create for a particular flight number, board-off point, and owner for an entire period, and if desired for selected days of operation.

Note: each allotment will still be for one single date only; multiple creating simply creates several allotments at one time.

When creating active or interactive negotiated space, the following elements are mandatory;

• Airline
• Date of service
• Flight number
• City pair
• Class of service
• Quantity
• Negotiated space owner
• Associated Handling Table

In addition to the mandatory fields, the following fields are optional;

• Tour reference
• Tour name
• Authorization code
• Commencement date
• Expiry date
• Reduction date and amount

**NOT YET IMPLEMENTED**, This feature is not currently available through the API interface.

Supported Operations

Currently, negotiated space may be created for a single date only. The following operations are available for creating a single negotiated space;

Simple creation

This operation allows the user to create a single negotiated space within Amadeus specifying only the mandatory data elements; airline, date of service, flight, city pair, class of service, quantity, nego owner details (negotiated space owner associated Handling Table).

With commencement date

A commencement date is used to specify when the sale from the negotiated space may begin.

With expiry date

An expiry date is used to specify when the sale of the negotiated space expires and will no longer be available.

With reduction date and amount

The reduction date and amount are used to specify a date when the unsold negotiated space levels may be reduced or set to zero.

With tour name

A tour name is used as a method for the airline to provide a meaningful name to a negotiated space that could relate to a particular product or range of products offered for sale through the negotiated space owners.

With tour name and tour reference

A tour reference is used in conjunction with the tour name to further detail the association of the negotiated space to a particular product or range of products offered for sale through the negotiated space owners. A tour reference may not exist without the presence of a tour name.

With authorization code

At creation time, an authorization code may be entered to identify the agent responsible for the creation of the negotiated space. This code is not used within Amadeus, but is made available for those agents/airlines who wish to maintain a record of such information.

With office level for handling table

At creation time, it is possible for the agent to specify a specific office level handling table to be utilized for the different options and default values controlling Negotiated Space allotment creation and synchronization.

With office level and sign level for handling table

At creation time, it is possible for the agent to specify a sign level handling table to be utilized for the different options and default values controlling Negotiated Space allotment creation and synchronization. When specifying a sign level table for usage, the agent sign sending the request will be associated as the specific sign level table requested. It is not possible to specify a specific user sign.

With corporate code level for handling table

At creation time, it is possible for the agent to specify a specific corporate level handling table to be utilized for the different options and default values controlling Negotiated Space allotment creation and synchronization.

It is possible to specify the following combinations for the corporate code;

• Corporate code
• Corporate code plus country
• Corporate code plus city

Complex combination of optional elements

It is possible to combine all mandatory elements and multiple optional elements when creating the negotiated space.

Limitations

Not applicable.

Unsupported Operations

The following operations are not currently supported for creating negotiated space via the API;

• Create single nego space with event name
• Create single nego space with any type of linked negotiated space
• Create multiple negotiated space

Prerequisites

An agreement must exist between the airline and the agent for negotiated space. The Negotiated Space customers are advised and driven by the NMC who is in charge of the settings for all Airlines that are Passive Negotiated Space implemented. Therefore the NMC, for each customer, will set the appropriate parameters and the correct security.

Building A Query

Depending on the flavor of the API that is used, each query will follow a given structure. The queries for the function operations are clearly explained with data element examples in a generic table view that can be adapted to the specific flavor of the API in use.

It is important to note that the examples in each chapter are only illustrations and are meant to provide the basis for a better understanding on which fields are mandatory for basic operation utilization. It is not a full explanation of every field that can be utilised for the operation, but rather a guideline to its use.

Receiving A Reply

Reply Structure

Error Messages

Operation: Simple Single Nego Space

The following structure is an example query to create a single negotiated space with the following mandatory elements;

Query Structure

Possible Errors

See "Error Messages" section

Operation: Single Nego Space With Commencement Date

The following is an example of creating a single negotiated space with the optional field identifying the negotiated space to become effective for sale on 20/05/01.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Single Nego Space With Expiry Date

The following is an example of creating a single negotiated space with the optional field identifying when the negotiated space is to become no longer effective for sale on 25/05/01.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Single Nego Space With Reduction Date And Amount

The following is an example of creating a single negotiated space with the optional fields identifying the date the negotiated space is to be reduced and the amount to reduce it to;

• Reduction Date - 200501
• Reduction Amount - 20

Query Structure

Possible Errors

See "Error Messages" section

Operation: Nego Space With Tour Name

The following is an example of creating a single negotiated space with the optional field identifying the tour name, HELLO TOURS, for negotiated space.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Tour Name With Tour Reference

The following is an example of creating a single negotiated space with the optional field identifying the tour reference, 1298B, for the negotiated space with the tour name HELLO TOURS. Please note, it is not possible to specify a tour reference without a tour name.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Single Nego Space With Authorization Code

The following is an example of creating a single negotiated space with the optional field identifying an authorization code, BW, for negotiated space.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Single Nego Space With Office Id And Sign Level For Handling Table

The following is an example of creating a single negotiated space with the optional field identifying a sign level handling table to be used in the office ID level for the negotiated space.

Note: the sign level for the handling table cannot be specified without specifying an office ID level.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Single Nego Space With Corporate Code Level For Handling Table

The following is an example of creating a single negotiated space with the optional field identifying the corporate code level, 1A0, for the negotiated space instead of an office ID level.

Note: that the corporate code level and the office level share the same field structure element. Therefore, it is not possible to have a corporate code level and an office Id level specified.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Corporate Code Level With City

The following is an example of creating a single negotiated space with the optional field identifying the corporate code level, 1A0, and a specific city code for the negotiated space.

Note: that the city code and the corporate code share the same field and that it may not be specified without the corporate code level.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Corporate Code Level With Country

The following is an example of creating a single negotiated space with the optional field identifying the corporate code level, 1A0, and a specific country for the negotiated space.

Note: that the country code and the corporate code share the same field and that it may not be specified without the corporate code level.

Query Structure

Possible Errors

See "Error Messages" section

Function: CreatePassiveNegoSpace

Overview

The ability to create passive negotiated space is dependent upon an extended ownership security (EOS) agreement between the airline and agency. Only specified agents are authorized to create the passive negotiated space on behalf of the airline.

Creating passive negotiated space is very similar to creating active or interactive negotiated space. When passive negotiated space is created, the inventory is held in the Amadeus system exactly in the same manner that active or interactive negotiated space is held. However, no messages are transmitted to the associated airline at any time regarding the passive negotiate space creation, update, deletion, sells, cancellations. It is the responsibility of the passive negotiated space agent to notify the airline directly of any negotiated space booking details.

This function provides the capability to create ONLY passive negotiated space. Passive Negotiated space may be created in two manners;

Single negotiated space

Single negotiated space is one that is created for a particular flight number, board-off point, and owner for a single date of operation.

Multiple negotiated space **NOT YET IMPLEMENTED**

Multiple negotiated space is created for a particular flight number, board-off point, and owner for an entire period, and if desired for a selected days of operation.

Note: that each allotment will still be for one single date only; multiple creating simply creates several allotments at one time.

When creating passive negotiated space, the following elements are mandatory;

• Airline
• Date of service
• Flight number
• City pair
• Class of service
• Quantity
• Negotiated space owner
• Associated Handling Table

In addition to the mandatory fields, the following fields are optional or mandatory depending on the configuration of the Airline Handling table or of the specific configuration table associated with the agent who performs the request;

• Tour reference
• Tour name
• Authorization code
• Commencement date
• Expiry date
• Reduction date and amount

**NOT YET IMPLEMENTED**, This feature is not currently available through the API interface.

Supported Operations

Currently, negotiated space may be created for a single date only. The following operations are available for creating a single negotiated space;

Simple creation

This operation allows the user to create a single negotiated space within Amadeus specifying only the mandatory data elements; airline, date of service, flight, city pair, class of service, quantity, and nego owner details (negotiated space owner associated Handling Table).

With commencement date

A commencement date is used to specify when the sale from the negotiated space may begin.

With expiry date

An expiry date is used to specify when the sale of the negotiated space expires and will no longer be available.

With reduction date and amount

The reduction date and amount are used to specify a date when the unsold negotiated space levels may be reduced or set to zero.

With tour name

A tour name is used as a method for the airline to provide a meaningful name to a negotiated space that could relate to a particular product or range of products offered for sale through the negotiated space owners.

With tour name and tour reference

A tour reference is used in conjunction with the tour name to further detail the association of the negotiated space to a particular product or range of products offered for sale through the negotiated space owners. A tour reference may not exist without the presence of a tour name.

With authorization code

At creation time, an authorization code may be entered to identify the agent responsible for the creation of the negotiated space. This code is not used within Amadeus, but is made available for those agents/airlines who wish to maintain a record of such information.

With office level for handling table

At creation time, it is possible for the agent to specify a specific office level handling table to be utilized for the different options and default values controlling Negotiated Space allotment creation and synchronization.

With office level and sign level for handling table

At creation time, it is possible for the agent to specify a sign level handling table to be utilized for the different options and default values controlling Negotiated Space allotment creation and synchronization. When specifying a sign level table for usage, the agent sign sending the request will be associated as the specific sign level table requested. It is not possible to specify a specific user sign.

With corporate code level for handling table

At creation time, it is possible for the agent to specify a specific corporate level handling table to be utilized for the different options and default values controlling Negotiated Space allotment creation and synchronization.

It is possible to specify the following combinations for the corporate code;

• Corporate code
• Corporate code plus country
• Corporate code plus city

Complex combination of optional elements

It is possible to combine all mandatory elements and multiple optional elements when creating the negotiated space.

Limitations

Not applicable.

Unsupported Operations

The following operations are not currently supported for creating negotiated space via the API;

• Create single nego space with event name
• Create single nego space with any type of linked negotiated space
• Create multiple negotiated space

Prerequisites

An agreement must exist between the airline and the agent for negotiated space. The Negotiated Space customers are advised and driven by the NMC who is in charge of the settings for all Airlines that are Passive Negotiated Space implemented. Therefore the NMC, for each customer, will set the appropriate parameters and the correct security.

Building A Query

Depending on the flavor of the API that is used, each query will follow a given structure. The queries for the function operations are clearly explained with data element examples in a generic table view that can be adapted to the specific flavor of the API in use.

It is important to note that the examples in each chapter are only illustrations and are meant to provide the basis for a better understanding on which fields are mandatory for basic operation utilization. It is not a full explanation of every field that can be utilised for the operation, but rather a guideline to its use.

Receiving A Reply

Reply Structure

Error Messages

Operation: Passive Single Nego Space

The following structure is an example query to create a single negotiated space with the following mandatory elements;

Query Structure

Possible Errors

See "Error Messages" section

Operation: Passive Single Nego Space With Commencement Date

The following is an example of creating a single passive negotiated space with the optional field identifying the negotiated space to become effective for sale on 20/05/01.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Passive Single Nego Space With Expiry Date

The following is an example of creating a single passive negotiated space with the optional field identifying when the negotiated space is to become no longer effective for sale on 25/05/01.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Passive Single Nego Space With Reduction Date & Amount

The following is an example of creating a single negotiated space with the optional fields identifying the date the negotiated space is to be reduced and the amount to reduce it to;

Query Structure

Possible Errors

See "Error Messages" section

Operation: Passive Single Nego Space With Reduction Date & Amount

The following is an example of creating a single negotiated space with the optional fields identifying the date the negotiated space is to be reduced and the amount to reduce it to;

Query Structure

Possible Errors

See "Error Messages" section

Operation: Passive Single Nego Space With Tour Name

The following is an example of creating a single passive negotiated space with the optional field identifying the tour name, HELLO TOURS, for negotiated space.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Passive Single Nego Space With Tour Name & Reference

The following is an example of creating a single passive negotiated space with the optional field identifying the tour reference, 1298B, for the negotiated space with the tour name HELLO TOURS.

Note: it is not possible to specify a tour reference without a tour name.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Passive Single Nego Space With Authorization Code

The following is an example of creating a single passive negotiated space with the optional field identifying an authorization code, BW, for negotiated space.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Passive Single Nego Space With Sign Level

The following is an example of creating a single passive negotiated space with the optional field identifying a sign level handling table to be used in the office ID handling table for the negotiated space.

Note: the sign level for the handling table cannot be specified without specifying an office ID level.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Passive Single Nego Space With Corporate Code

The following is an example of creating a single passive negotiated space with the optional field identifying the corporate code level, 1A0, for the negotiated space instead of an office ID level.

Note: that the corporate code level and the office level share the same field structure element. Therefore, it is not possible to have a corporate code level and an office Id level specified.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Passive Single Nego Space With Corporate Code Level & City

The following is an example of creating a single passive negotiated space with the optional field identifying the corporate code level, 1A0, and a specific city code, PAR, for the negotiated space.

Note:that the city code and the corporate code share the same field and that it may not be specified without the corporate code level.

Query Structure

Possible Errors

See "Error Messages" section

Function: ChangeNegoSpace

Overview

This function allows the agent to change existing negotiated space elements. When changing negotiated space elements, it is necessary to include the following mandatory negotiated space elements, which properly identify the specific negotiated space to modify;

• Airline
• Date of service
• Flight number
• City pair
• Class of service
• Negotiated space owner
• 1A ID

Note: once the negotiated space has been created, an Amadeus system ID (1AID) is assigned to the negotiated space and becomes a mandatory element when requesting a change. If this ID is not known, it may be obtained by retrieving the negotiated space details via the Display Nego Space function.

In addition, if the negotiated space is further detailed with a Tour Name and a tour reference, these items must be included in the change request as well.

Supported Operations

The following operations are supported when changing negotiated space;

Change of allocated seat level

The original number of allocated negotiated seats can be modified to specify a new amount available for sale.

Change of commencement date

A commencement date can be modified to specify a new date for when the sale from the negotiated space may begin.

Change of expiry date

An expiry date can be modified to specify a new date for when the sale of the negotiated space expires and will no longer be available.

Change of reduction date

The reduction date can be modified to specify a new date for when the unsold passive negotiated space levels may be reduced or set to zero.

Change of reduction amount

The reduction amount can be modified to specify a new percentage amount to reduce the unsold negotiated space levels by when the reduction date is reached.

Limitations

At this time, there are no known limitations for the Change Negotiated Space function.

Unsupported Operations

Not applicable.

Prerequisites

A negotiated space must exist on the Amadeus system prior to requesting to change an element. A match on the mandatory elements provided in the change request must be found within the Amadeus system, or an error will be returned.

The User must have the appropriated authorization to update blocks. The User must be owner of the block.

The Amadeus ID for the negotiated space must be specified in the change request. This ID is not known until after the negotiated space is created. This may be retrieved by requesting the negotiated space information via the Display Nego Space function.

Building A Query

Depending on the flavor of the API that is used, each query will follow a given structure. The queries for the function operations are clearly explained with data element examples in a generic table view that can be adapted to the specific flavor of the API in use.

It is important to note that the examples in each chapter are only illustrations and are meant to provide the basis for a better understanding on which fields are mandatory for basic operation utilization. It is not a full explanation of every field that can be utilised for the operation, but rather a guideline to its use.

Receiving A Reply

Reply Structure

Error Messages

Operation: Change Of Allocated Seat Level

The following is an example to change the allocated seats to 28 for the following negotiated space;

Query Structure

Possible Errors

See "Error Messages" section

Operation: Change Of Commencement Date

The following is an example to change the commencement date to 280501 for the following negotiated space;

Query Structure

Possible Errors

See "Error Messages" section

Operation: Change Of Expiry Date

The following is an example to change the expiry date to 240601 for the following negotiated space;

Query Structure

Possible Errors

Expiry date changes restricted

The ability to change the expiry date may be inhibited in the handling table, in which case this error will be returned. Verify that the handling table is set properly, update the handling table if necessary and retry the request.

See also the "Error Messages" section

Operation: Change Of Reduction Date

The following is an example to change the reduction date to 230601 for the following negotiated space;

Query Structure

Possible Errors

See "Error Messages" section

Operation: Change Of Reduction Amount

The following is an example to change the percentage for the reduction amount to 23 for the following negotiated space;

Query Structure

Possible Errors

See "Error Messages" section

Operation: Change Mulitple Elements

It is possible to combine multiple change elements, as the example below illustrates the ability to change the following elements simultaineously;

The elements above are requested to be changed for the following negotiated space;

Query Structure

Possible Errors

See "Error Messages" section

Function: CancelNegoSpace

Overview

This function allows the agent to cancel existing negotiated space items. When canceling negotiated space items, it is necessary to include the following mandatory negotiated space elements, which properly identify the specific negotiated space to modify;

• Airline
• Date of service
• Flight number
• City pair
• Class of service
• Negotiated space owner
• 1A ID

Note: that once the negotiated space has been created, an Amadeus system ID (1AID) is assigned to the negotiated space and becomes a mandatory element when requesting a change. If this ID is not known, it may be obtained by retrieving the negotiated space details via the Display Nego Space function.

In addition, if the negotiated space is further detailed with a Tour Name and a tour reference, these items must be included in the cancel request as well.

Once the cancel request has been processed, the negotiated space item will no longer be accessible and the Amadeus system will notify the appropriate airline so that any unsold seats remaining on the negotiated space may be returned to the normal airline inventory.

Note that only unsold blocks can be deleted.

Supported Operations

The following operations are supported when changing negotiated space;

Cancel Negotiated Space with only mandatory elements

It is possible to cancel a simple negotiated space that is identified with only mandatory elements.

Cancel Negotiated Space with Tour Name

It is possible to cancel a negotiated space that is identified with a tour name.

Cancel Negotiated Space with Tour Name and Tour Reference

It is possible to cancel a negotiated space that identified with a tour name and a tour reference.

Limitations

The following operations are not currently supported for creating negotiated space via the API;

• Cancel nego space specifying a unique record locator
• Cancel nego space specifying an event name

Unsupported Operations

Not applicable.

Prerequisites

A negotiated space must exist on the Amadeus system prior to requesting to cancel it. A match on the mandatory elements provided in the cancel request must be found within the Amadeus system, or an error will be returned.

The User is authorized to delete a block.
The User, when different from an airline agent, is owner of the block.

The Amadeus ID for the negotiated space must be specified in the cancel request. This ID is not known until after the negotiated space is created. This may be retrieved, by requesting the negotiated space information via the Display Nego Space function.

Only unsold blocks can be deleted.

Building A Query

Depending on the flavor of the API that is used, each query will follow a given structure. The queries for the function operations are clearly explained with data element examples in a generic table view that can be adapted to the specific flavor of the API in use.

It is important to note that the examples in each chapter are only illustrations and are meant to provide the basis for a better understanding on which fields are mandatory for basic operation utilization. It is not a full explanation of every field that can be utilised for the operation, but rather a guideline to its use.

Receiving A Reply

Reply Structure

Error Messages

Operation: Cancel Negotiated Space With Only Mandatory Elements

The following example is a request to cancel the following negotiated space item;

Query Structure

Possible Errors

See "Error Messages" section

Operation: Cancel Negotiated Space With Tour Name

The following example is a request to cancel the associated negotiated space item specifying the tour name of HELLO TOURS;

Query Structure

Possible Errors

See "Error Messages" section

Operation: Cancel Negotiated Space With Tour Name And Tour Reference

The following example is a request to cancel the associated negotiated space item specifying the tour name of HELLO TOURS with a tour reference 129B;

Note: a tour name is mandatory for this cancel request, as the tour reference may not be specified without the tour name.

Query Structure

Possible Errors

See "Error Messages" section

Function: DisplayNegoSpace

Overview

This function allows the agent to retrieve the details of existing negotiated space. Once the negotiated space has been created, it is possible to search and retrieve the following detailed information regarding the space;

• Amadeus Nego ID
• Airline
• Flight number
• Flight departure date
• City pair
• Class of service
• Commencement date
• Reduction date
• Reduction amount
• Expiry date
• Airline Nego ID
• Owner ID
• Tour name
• Tour reference
• Number of seats allotted
• Number seats sold
• Number of seats remaining to sell
• Type of space: Active, Interactive or Passive
• Authorization code

In addition to the fields returned above, the retrieved information will also indicate the following;

• If the negotiated space has not been acknowledged by the airline, only in the cases of active or interactive types, the retrieval information will indicate a pending acknowledgment.
• If a change request has been made to increase or decrease the allotted seats and the airline has not acknowledged the change request, the retrieval information will indicate the pending acknowledgement and the new allotment requested.

Supported Operations

Limitations

At this time, there are no known limitations when using the Display Nego Space function.

Unsupported Operations

Not applicable.

Prerequisites

An agreement must exist between the airline and the negotiated space owner/agent for data retrieval. Negotiated space matching the search criteria must exist or an error will be returned.

Building A Query

Depending on the flavor of the API that is used, each query will follow a given structure. The queries for the function operations are clearly explained with data element examples in a generic table view that can be adapted to the specific flavor of the API in use.

It is important to note that the examples in each chapter are only illustrations and are meant to provide the basis for a better understanding on which fields are mandatory for basic operation utilization. It is not a full explanation of every field that can be utilised for the operation, but rather a guideline to its use.

Receiving A Reply

Reply Structure

All negotiated space items found matching the criteria to the retrieval request will be returned.

The following is an example of a successful retrieval request containing 2 matching negotiated space elements to the request.

Matching element number one is
(/negotiatedSpaceInfo[1]/negotiatedSpaceDetails/...)
which is identified by [1] on the display given below, followed by matching element number two which is
(/negotiatedSpaceInfo[2]/negotiatedSpaceDetails/...)
identified by [2]. All subsequent matching items will be indexed ([x]) in a similar manner:
(/negotiatedSpaceInfo[x]/negotiatedSpaceDetails/...).

Error Messages

Operation: Retrieve By Airline & Flight Departure Date

The following example is a request to retrieve all negotiated space allotments matching the minimum criteria below;

Query Structure

Possible Errors

See "Error Messages" section

Operation: Retrieve By Airline & Flight Number

The following example is a request to retrieve all negotiated space allotments matching the minimum criteria below;

Query Structure

Possible Errors

See "Error Messages" section

Operation: Retrieve By Airline & Number Suffix

The following example is a request to retrieve all negotiated space allotments containing the mandatory criteria and optional flight number suffix below.

In the case where the suffix is specified in conjunction with the mandatory flight date element instead of a flight number the reply will contain all flight numbers departing on a specific date with the particular suffix specified in the retrieve request.

Note: the flight number suffix may be specified with the mandatory flight departure date element as well.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Retrieve By Airline & Class Of Service

The following example is a request to retrieve all negotiated space allotments containing the mandatory criteria and optional flight number suffix below.

In the case where the class of service is specified in conjunction with the mandatory flight date element instead of a flight number the reply will contain all flight numbers departing on a specific date with the class of service specified in the retrieve request.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Retrieve By Airline & City Pair

The following example is a request to retrieve all negotiated space allotments containing the mandatory criteria and optional flight number suffix below.

In the case where the city pair is specified in conjunction with the mandatory flight number element instead of a flight departure date the reply will contain all flight departures for the specified flight number matching the city pair specified.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Retrieve By Airline & Commencement Date

The following example is a request to retrieve all negotiated space allotments containing the mandatory criteria and optional flight number suffix below, Note that the commencement date may be specified with the mandatory flight departure element as well.

In the case where the commencement date is specified in conjunction with the mandatory flight date element instead of a flight number, the reply will contain all flight numbers for the date specified with a matching commencement date to the one specified in the retrieve request.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Retrieve By Airline & Expiry Date

The following example is a request to retrieve all negotiated space allotments containing the mandatory criteria and optional flight number suffix below.

Note: that the expiry date may be specified with the mandatory flight number element as well.

In the case where the expiry date is specified in conjunction with the mandatory flight number element instead of a flight departure date, the reply will contain all flight departures for the specified flight number containing the expiry date specified.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Retrieve By Airline & Allocated Seat Number

The following example is a request to retrieve all negotiated space allotments containing the mandatory criteria and optional flight number suffix below;

Note: the number of allocated seats may be specified with the mandatory flight departure element as well.

**Be aware that this is corresponding to the number of allocated seats and is not associated to the number of remaining seats to be sold.**

In the case where the number of allocated seats is specified in conjunction with the mandatory flight date element instead of a flight number, the reply will contain all flight numbers for the date specified with the number of allocated seats specified in the retrieve request.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Retrieve By Airline & Reduction Date

The following example is a request to retrieve all negotiated space allotments containing the mandatory criteria and optional reduction date below.

Note: that the reduction date may be specified with the mandatory flight number element as well.

In the case where the reduction date is specified in conjunction with the mandatory flight number element instead of a flight departure date, the reply will contain all flight departures for the specified flight number containing the reduction date specified.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Retrieve By Airline & Reduction Amount

The following example is a request to retrieve all negotiated space allotments containing the mandatory criteria and optional reduction amount below;

**Be aware that the reduction amount is associated to a percentage amount**

Note: the reduction amount may be specified with the mandatory flight number element as well.

In the case where the reduction amount is specified in conjunction with the mandatory flight number element instead of a flight departure date, the reply will contain all flight departures for the specified flight number containing the reduction amount specified.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Retrieve By Airline & Tour Name

The following example is a request to retrieve all negotiated space allotments containing the mandatory criteria and optional tour name below;

Note: the tour name may be specified with the mandatory flight departure element as well.

In the case where the tour name is specified in conjunction with the mandatory flight date element instead of a flight number, the reply will contain all flight numbers for the date specified with a matching tour name to the one specified in the retrieve request.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Retrieve By Airline & Tour Reference

The following example is a request to retrieve all negotiated space allotments containing the mandatory criteria and optional tour reference below.

In the case where the tour reference is specified in conjunction with the mandatory flight date element instead of a flight number, the reply will contain all flight numbers for the date specified with a matching tour reference to the one specified in the retrieve request.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Retrieve By Airline & Authorization Code

The following example is a request to retrieve all negotiated space allotments containing the mandatory criteria and optional authorization code below.

Note: that the authorization code may be specified with the mandatory flight departure element as well.

In the case where the authorization code is specified in conjunction with the mandatory flight date element instead of a flight number, the reply will contain all flight numbers for the date specified with a matching authorization code to the one specified in the retrieve request.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Retrieve By Airline & Airline Negotiated Space ID

The following example is a request to retrieve all negotiated space allotments containing the mandatory criteria and optional airline nego space ID below.

Note: the airline negotiated space ID may be specified with the mandatory flight departure element as well.

As the airline negotiated space ID, in most cases, is unique system identifier in the particular airline system for a particular negotiated space allotment, only one negotiated space allotment might be returned. If the airline has a group of allotments associated to one ID, then the group will be returned.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Retrieve By Airline & Amadeus Negotiated Space ID

The following example is a request to retrieve all negotiated space allotments containing the mandatory criteria and optional Amadeus nego space ID below.

Note: the Amadeus negotiated space ID may be specified with the mandatory flight departure element as well.

As the amadeus negotiated space ID is not necessarily a unique system identifier for a particular negotiated space allotment, one or multiple allotments containing the space ID may be returned.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Retrieve By Airline & Days Of Operation

The following example is a request to retrieve all negotiated space allotments containing the mandatory criteria and optional days of operation below. Notice that the days of operation are concatenated in the entry field.

Note: that although the days of operation may be specified with the mandatory flight departure element, it really serves no purpose to do such a combination as the days of operation are validated against the flight departure date. Therefore, if the days of operation do not match the day of departure specified the search will result in an error.

However, the days of operation can be particularly useful when used in combination with the effective and discontinue date elements.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Retrieve By Airline & Multiple Options

There are no restrictions on the combination of any optional elements. Therefore all optional elements may be combined in one entry to apply the maximum restriction for the reply.

The following example is a request to retrieve all negotiated space allotments containing the mandatory criteria and optional elements below

Query Structure

Possible Errors

See "Error Messages" section

Operation: Retrieve By Inactive Negotiated Space Only

The following example is a request to retrieve all negotiated space allotments rendered inactive by a schedule change for LH flight 111

Note: that the inactive indicator may be specified with the mandatory flight departure element as well.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Retrieve By Owner Negotiated Space Only

The following example is a request to retrieve all negotiated space allotments with a specific flight departure date that are associated to the requestor

Note: this option is really only applicable to requesting airline offices and not agencies. As security measures automatically restrict an agency to viewing only the negotiated space allotments associated to the requesting agency office id, it is not necessary to specify the owner indicator. Airline offices, on the other hand, will view all negotiated space allotments for the particular airline unless they specify the owner indicator to narrow the reply to only those associated to the requesting airline office ID.

There are no restrictions for an agency specifying this optional element. Therefore, no error messages are returned in such a case but no additional editing is performed either.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Retrieve By Effective Date

The following example is a request to retrieve all negotiated space allotments containing the mandatory criteria with a specific effective date

Note: that the effective date may be specified with the mandatory flight departure element as well.

In the case where the effective date is specified in conjunction with the mandatory flight date element instead of a flight number, the reply will contain all flight numbers for the date specified with a matching effective date to the one specified in the retrieve request. i.e., a list of all flight numbers for all departure dates that contain the effective date.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Retrieve By Ending Date

The following example is a request to retrieve all negotiated space allotments containing the mandatory criteria with a specific ending date.

Note: that the ending date may be specified with the mandatory flight departure element as well.

In the case where the ending date is specified in conjunction with the mandatory flight date element instead of a flight number, the reply will contain all flight numbers for the date specified with a matching ending date to the one specified in the retrieve request. i.e., a list of all flight numbers for all departure dates that contain the ending date.

Query Structure

Possible Errors

See "Error Messages" section

Function: RetrieveSeatMap

Overview

Seat maps may be requested for flights of Amadeus system user airlines and other airlines that hold an interactive seat map agreement with Amadeus. An interactive seat map agreement must exist for the requested airline code or an error will result.

At the time of the seat map request, the Amadeus system will verify the operation of the flight on the specified date of departure for the selected city pair. If the flight does not operate on the given date for the given city pair, an error will be returned.

It is not mandatory for an airline to file a seat map for all flights. Thus, the process may pass the flight operational check but will still return an error indicating that a seat map does not exist for the specified flight request.

Note: By default, all seats on a flight are occupied or free. The default is specified in the cabin description : SeatOccupationDefault. In the reply, in the row details, if several seat references are omitted for seats, the default should be applied.

Supported Operations

Limitations

Not applicable.

Unsupported Operations

The following operations are not supported via the Request Seat Map API function at this time;

• Direct Access Seat Maps
• Request Seat Map by PNR Segment Number
• Request Seat Map by Air Availability Segment Number

The following characteristic identification codes are not processed at this time (only a 1 character class of service identifier type is expected and processed at this time):

Prerequisites

An interactive seat map agreement must exist between the specific airline and Amadeus.

Note: this support is provided for airlines having an interactive seat map interface with Amadeus.

Building A Query

Depending on the flavor of the API that is used, each query will follow a given structure. The queries for the function operations are clearly explained with data element examples in a generic table view that can be adapted to the specific flavor of the API in use.

It is important to note that the examples in each chapter are only illustrations and are meant to provide the basis for a better understanding on which fields are mandatory for basic operation utilization. It is not a full explanation of every field that can be utilised for the operation, but rather a guideline to its use.

Mandatory Elements

The following elements are mandatory when requesting a seat map:

• Airline Code
• Flight Number
• Date of Departure
• Departure City
• Arrival City

Optional Elements

In addition to the mandatory elements, the following are optional elements that may be included in the request:

• Class of Service
• Frequent Flyer Card and Passenger Name
• Record Locator

Receiving A Reply

The seat map information for each carrier holding an interactive seat map agreement will be returned in a common form.

Standard Elements

The following standard elements are commonly returned for every seat map request:

• Cabin Details
• Equipment Code
• Individual Seat Information:
  Seat Row Number
  Column Description
  Seat Availability
  Seat Characterisitics
  

Common Seat Map Codes

Each seat map is returned with common symbols representing the specific details of the aircraft. The following is the common legend used in the Request SeatMap Replies:

Reply Structure

The following illustrates a successful RequestSeatMapReply structure in the API.

Note: the sample below is a partial sample with a repition of only 3 segment row information elements. In a normal full reply, this information would be repeated to cover the total number of existing rows of the aircraft.

Error Messages

The following common errors may be returned at any time to the user when processing a query;

Invalid City/Airport Code

This error is returned if an invalid city or airport code is requested.

Seat Map Not Available For This Carrier

This error is returned if a seat map agreement does not exist for the carrier specified in the request.

Check Class of Service

This error is returned if the class of service specified is not valid.

Check Flight Number

This error is returned if the flight number entered in the request exceeds the five characters or an alpha other than A-B-C-D is entered as a fifth flight character.

Seat Map Not Available For This Carrier

This error is returned when an interactive seat map agreement does not exist between the requested carrier and Amadeus or if a seat map has not been created for the flight carrier.

Operation: Seat Map With Mandatory Elements

The example below illustrates a Request Seat Map Query with mandatory elements:

Query Structure

Possible Errors

See "Error Messages" section

Operation: Seat Map For Specific Class of Service

The example below illustrates a Request Seat Map Query with mandatory element information with an optional class of service specified;

Query Structure

Possible Errors

See "Error Messages" section

Operation: Seat Map For Specific Frequent Flyer

The example below illustrates a Request Seat Map Query with just specifying the Frequent Flyer Card number.

The membershipLevel value is a precalculated denomination associated to the Frequent Flyer card number/holder that originates from the Profiles database or an associated carrier database. It should be noted that the 'membershiplevel' is different for all carriers.

For example, the value 1 indicates means the 'membership level' as known by the carrier that holds the frequent flyer card. And the value 2 indicates the 'membership level' as defined by the Airlines Alliance the carrier belongs to (if any).

It is possible to know the membershipLevel value in advance by creating a PNR, as the PoweredPNR reply, will return the values in the PrioryCode/Priority details.

Note: It is important to enter the carried code (e.g. LH) ahead of the cardholder number in the frequentTravelerIdentCode field.

Query Structure

Possible Errors

See "Error Messages" section

Function: FlightInfo

Overview

The Flight Information function provides Amadeus end-users with up-to-date information related to the operation of a particular flight before, during and after departure. Similarly, it provides irregularity and supplementary codes, which may be found in Availability, or Schedule displays to show a change in the flight operation.

Flight Information data (FLIFO) are stored in the Amadeus Central System as a result of:

• STATIC flight UPDATES done via SSIM message or SSIM tape load.
• OPERATIONAL UPDATES done via MVT and DIV.

The Display (DO) entry is used to display the latest known Flight Operational Information related to one flight/date.

Supported Operations

The Flight Information function allows for the following operations, this depend on options used in the input query:

• Display Flight information for flight number on current date.
• Display Flight information for flight number on specified date.
• Display Flight information for flight number on specified date on a leg.
• Display Flight information for flight number on specified date from a board point.

Limitations

The following Time Mode options T12 and T24 that are used for requesting a flight operational information display are not currently supported in the API.

Unsupported Operations

History entry is not supported (DH).

Prerequisites

Building A Query

Depending on the flavor of the API that is used, each query will follow a given structure. The queries for the function operations are clearly explained with data element examples in a generic table view that can be adapted to the specific flavor of the API in use.

It is important to note that the examples in each chapter are only illustrations and are meant to provide the basis for a better understanding on which fields are mandatory for basic operation utilization. It is not a full explanation of every field that can be utilised for the operation, but rather a guideline to its use.

Receiving A Reply

Reply Structure

The following example illustrates a successful request for flight information:

Error Messages

The errors listed here can be encountered while using the PoweredAir interface and the Flight Information function.

Please note that 'Check City Pair' is returned when:

• the query is done for an incorrect city pair.
• the query does not pass initial validation (for instance if the flight number does not exist).
• the flight date is outside the system range.

Operation: Airline Code And Flight Number

Basic flight information request based on airline code and flight number.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Date Specified

Flight information request with date specified.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Full Request Per Itinerary

Flight information request for itinarary.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Full Request Per Leg

Flight information request per leg.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Request Per Boardpoint

Flight information request per board point.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Full Request Per Segment

Flight information request per segment.

Query Structure

Possible Errors

See "Error Messages" section

Operation: Change Of Gauge Flight Information In Reply

This example illustrates a request for flight Information for flight UA 121, in this specific case the Reply includes the ChangeOfGauge information.

The legDetails/complexingFlightIndicator set to 2 is the indicator in the reply that denote a Change Of Gauge flight, see Reply below:

Query Structure

Possible Errors

See "Error Messages" section.

Function: RebookAirSegment

Overview

The RebookAirSegment function enables you to rebook existing segments in a PNR. It is possible to make changes to both new and retrieved PNRs but not to group PNRs with more than 9 seats. Also, you cannot rebook open segments, information segments, non-participating carrier segments, or passive segments.

Supported Operations

The RebookAirSegment function can be used to change:

• A class of service in one or several segments
• A date in one or several segments
• A flight number in one or several segments
• A combination of class, date, and flight number

Limitations

If segments that are to be rebooked are married, the airline will need to have a SBF indicator set in the APT so the rebook of a married segment can be accepted, Otherwise the one of the following responses will be given:

• Not authorized for this airline
• Not allowed married segments
• Unsuccessful rebook

Unsupported Operations

Not applicable.

Prerequisites

The segments to be rebooked and the PNR must exist.

Building A Query

TBD

Receiving A Reply

Reply Structure

The following RebookAirSegmentReply response shows the reply when segment two's class have been changed from F to C.

Error Messages

TBD

Operation: Class Rebook

This example is for the rebook of the second segment from F Class to C Class.
PNR:

RP/MUC1A0701/MUC1A0701 BM/PR 5JAN04/1329Z YPPUGA


API/TEST

LH 744 F 08MAR 1 FRABKK HL1 2130 1 2200 1410+1 *1A/E*

LX 182 J 09MAR 2 BKKSIN HK1 2 1530 1845 *1A/E*

AP MUC - AMADEUS DEFAULT OFFICE - A

TK OK05JAN/MUC1A0701

Query Structure

Possible Errors

See "Error Messages" section.

Operation: Class Rebook after PricePNRWithLowerFare

This example is the same as the previous one, but in the case where rebook is performed following a PricePNRWithLowerFare request, and the reference of the recommendation selected by the user (number 2) is transmitted in the rebook:
PNR:

RP/MUC1A0701/MUC1A0701 BM/PR 5JAN04/1329Z YPPUGA


API/TEST

LH 744 F 08MAR 1 FRABKK HL1 2130 1 2200 1410+1 *1A/E*

LX 182 J 09MAR 2 BKKSIN HK1 2 1530 1845 *1A/E*

AP MUC - AMADEUS DEFAULT OFFICE - A

TK OK05JAN/MUC1A0701

Query Structure

Possible Errors

See "Error Messages" section.

Operation: Rebook Two Segment Classes

This example shows the rebook of:

• LH 744 from class F to class C
• LX 182 from class J to class C

PNR:

RP/MUC1A0701/MUC1A0701 BM/PR 5JAN04/1331Z YPPUGE


API/TEST

LH 744 F 08MAR 1 FRABKK HL1 2130 1 2200 1410+1 *1A/E*

LX 182 J 09MAR 2 BKKSIN HK1 2 1530 1845 *1A/E*

AP MUC - AMADEUS DEFAULT OFFICE - A

TK OK05JAN/MUC1A0701

Query Structure

Possible Errors

See "Error Messages" section.

Operation: Rebook Flight Number

Rebook flight LH 744 to flight LH 9762.
PNR:

RP/MUC1A0701/MUC1A0701 BM/PR 5JAN04/1336Z YPPUGN


API/TEST

LH 778 F 08MAR 1 FRASIN HK1 2140 1 2210 1650+1 *1A/E*

AP MUC - AMADEUS DEFAULT OFFICE - A

TK OK05JAN/MUC1A0701

Query Structure

Possible Errors

See "Error Messages" section.

Operation: Rebook Segment Date

Rebook the second segment from 8/03 to 9/03.
PNR:

RP/MUC1A0701/MUC1A0701 BM/PR 5JAN04/1336Z YPPUGN


API/TEST

LH 778 F 08MAR 1 FRASIN HK1 2140 1 2210 1650+1 *1A/E*

AP MUC - AMADEUS DEFAULT OFFICE - A

TK OK05JAN/MUC1A0701

Query Structure

Possible Errors

See "Error Messages" section.