Versions Compared

Version Old Version 5 New Version 6
Changes made by

Alvaro Chaparro

Alvaro Chaparro

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Excerpt
nameQuery_Common

Query - Common

NAME

DESCRIPTION

FORMAT

ALLOWED/POSSIBLE VALUES

NDC SERVICES

<Query> (Common)

OrderID

Order ID previously generated

Alphanumeric

Any

IATA Schema

Expand
titleExample
Code Block
languagexml
<Query>
	<OrderID>IB2f9657fdab8e458e90a30e15fd1d1f19OC</OrderID>
</Query>

Query - AcceptRepricedOrder

The PriceGuaranteeTimeLimit (PGTL) element will appear in all Offers and Orders for all markets. Note that this element will have the same value as the PaymentTimeLimit (PTL), except for those markets where the new Reprice on hold is required.

The first market requiring this is Argentina. The PGTL element will be different to the PTL, forcing all users to use the new Reprice on hold functionality.

The price of an Order on hold (un paid) is only guaranteed until the PGTL expires, after which the new Reprice functionality must be used together with the OrderChange-Accept function.

The PTL, is not affected and if expires, the Order is no longer available.

There are three scenarios:

  1. Before both the PTL and the PGTL expire,

    1. This is as today, whereby any Reprice will return the same price and conditions (including PGTL) given when booked. An OrderChange-Payment can be sent to fulfill the Order.

  2. After both the PTL and the PGTL have expired.

    1. The Order is cancelled, you need to create a new one.

  3. After the PGTL has expired, but before the PTL expires. In this case, you must Reprice the Order, as per the following flow:

    1. Send a new OrderReshopRQ-Reprice to get the applicable fare and conditions

    2. If the price has not changed, send an OrderChange-Payment

    3. If the price has changed the system will generate a new Offer which must be accepted using the OrderChange-Accept. Once accepted it can be paid for. The steps would be as per the following:

Then in the OrderChangeRQ> you can:

  • Accept the modification of the order: <AcceptRepricedOrder> you will have the new PGTL with the original PTL from the Order. The PGTL will never be greater than the PTL, the Order has to be paid before the PTL expires.

  • If the Order has ancillaries, you will get a warning message at OrderReshop-Reprice indicating that they have not been repriced: “Repricing is not allowed for additional services”, as the prices, today, are maintained at the original cost.

  • When accepting the reprice, an OrderView is generated ONLY with the repriced Flight OrderItems and their associated costs, and if you try to pay this value, and your Order has other OrderItems (such as ancillaries) you will get an error “Incorrect amount”. You must do an OrderRetrieve to recover a complete OrderView, with all the OrderItems of the Order and their costs. After that, you can pay by OrderChange-Payment.

Excerpt
nameQuery_AcceptRepricedOrder

Query - AcceptRepricedOrder

NAME

DESCRIPTION

FORMAT

ALLOWED/POSSIBLE VALUES

NDC SERVICES

<Query / AcceptRepricedOrder> (Pay on hold PNR flow)

ResponseID

ID of response from previous order reshop reprice

Alphanumeric

Any

Iberia NDC in case of previous order reshop reprice

Expand
titleExample
Code Block
languagexml
<AcceptRepricedOrder>
	<ResponseID>Qm9va2luZ0AxNjk3Nzg5ODA2MDU1LUVDSG8x</ResponseID>
</AcceptRepricedOrder>

Excerpt
nameQuery_PassengerServicing

Query - PassengerServicing

NAME

DESCRIPTION

FORMAT

ALLOWED/POSSIBLE VALUES

NDC SERVICES

<Query / PassengerServicing> (Update contact info flows, name, e-mail, phone, frequent flyer info…)

New

Info

Attribute

PassengerID

The unique identifier of the Passenger whose information is being updated.

Alphanumeric

The PassengerID obtained from the previous OrderViewRS having previously retrieved the Order.

IATA Schema if 'PassengerServicing / New' tag is indicated.

New / ContactInfoRef

Contact info reference, which contact info filled in below will update original contact info.

Alphanumeric

Any

Iberia NDC in case of:

  • Contact info (email & phone) correction flow

New / Individual / Given

Name of the passenger to change

Alphanumeric

Any

Iberia NDC in case of:

  • Name correction flow

New / Individual / Surname

Surname of the passenger to change

  • (Agency can specify separated by a special character "@" first and second surname → Ex: De la Morena@López)

Alphanumeric

Any

IATA Schema if 'New / Individual' tag is indicated

New / LoyaltyProgramAccount / Airline / AirlineDesignator

Airline ID associated to frequent flyer number

Alphanumeric

Any

Iberia NDC in case of:

  • Add/Update Frequent Flyer Number

New / LoyaltyProgramAccount / AccountNumber

Frequent Flyer or On Business number account

Alphanumeric

Any

Iberia NDC in case of:

  • Add/Update Frequent Flyer Number

  • Add/Update On Business Number

New / ActionType

Action type

Alphabetical

  • Add

  • Remove

Iberia NDC in case of:

  • Name correction flow

  • Contact info (email & phone) correction flow

  • Add/Update Frequent Flyer Number

  • Add/Update On Business Number

New / IdentityDocument / IdentityDocumentNumber

Identity document number

Alphanumeric

Any

New / IdentityDocument / IdentityDocumentType

Type of identity document

Alphanumeric

Any

New / IdentityDocument / IssuingCountryCode

Country code for identity document issuing

Alphabetical

List of Countries

New / IdentityDocument / ExpiryDate

Expire date for identity document

Date

Any future date

New / IdentityDocument / Birthplace

Birth place for the identity document holder

Alphabetical

List of Countries

New / IdentityDocument / Visa / VisaNumber

New visa number

Numeric

Any

New / IdentityDocument / Visa / VisaType

New type of visa

Alphabetical

Any

Previous

Info

Attribute

PassengerID

Passenger ID, which info will be updated

PassengerID attribute value can be indicated in PassengerID attribute from AirShopping request.

Alphanumeric

Alphanumeric

Type of Passengers

Value indicated in PassengerID attribute from AirShopping request

IATA Schema if 'PassengerServicing / Previous' tag is indicated.

Previous / Individual / GivenName

Old passenger given name, not mandatory, but if informed and does not match, an error will be shown

Alphanumeric

Any

Previous / Individual / Surname

Old passenger surname, not mandatory, but if informed and does not match, an error will be shown

Alphanumeric

Any

IATA Schema if 'Previous / Individual' tag is indicated

Previous / ContactInfoRef

Old contact info reference

Alphanumeric

Any

Previous / ActionType

Action type

Alphabetical

  • Add

  • Remove

Expand
titleExample
Code Block
languagexml
<Query>
      <OrderID>xxxxxxxxxxxxxxxxxxx</OrderID>
      <PassengerServicing>
         <New PassengerID="ADULT_01">
            <LoyaltyProgramAccount>
               <Airline>
                  <AirlineDesignator>IB</AirlineDesignator>
               </Airline>
               <AccountNumber>#########</AccountNumber>
            </LoyaltyProgramAccount>
            <ActionType>Add</ActionType>
         </New>
      </PassengerServicing>
</Query>

...