Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 21 Next »

 New or modified element

To be removed/deprecated

Unique to v2 - Branded Fares

Unique to V1 - Fare Families

Common Sections

 HTTP Header

HTTP Header

NAME

DESCRIPTION

FORMAT

ALLOWED/POSSIBLE VALUES

api_key

Your unique key used to authorize access to the API. update source

Alphanumeric

N/A

 Language, Version and Name Space

Language, Version and Name Space

NAME

DESCRIPTION

FORMAT

ALLOWED/POSSIBLE VALUES

NDC SERVICES

Version

The IATA version of the message

Mandatory for Schema

Numeric

Any

All Services

PrimaryLangID

Two character ISO Language Code, for the agent’s preferred language.

This is used for error messages and some other data such as legal waivers.

2 Alphabetical

  • EN

  • ES

All Services

(except in the OrderChangeNotification)

xmlns

IATA official website

Mandatory for Schema

Alphanumeric

Any

All Services

 Point of Sale

Point of Sale

HEADER NAME

DESCRIPTION

FORMAT

ALLOWED/POSSIBLE VALUES

NDC SERVICES

<PointOfSale>

Location / CountryCode

The point of sale country code.

2 letter country code

List of countries

All request messages

 Document

Document

NAME

DESCRIPTION

FORMAT

ALLOWED/POSSIBLE VALUES

NDC SERVICES

<Document>

ReferenceVersion

The IATA Schema version.

Numeric

Any

 All Services

 Party

Party

Sender Section

NAME

DESCRIPTION

FORMAT

ALLOWED/POSSIBLE VALUES

NDC SERVICES

<Party>

Sender / TravelAgencySender / Name

Agency Name

Iberia will always use the Name stored in our system when the Seller/Sender registered to use our NDC.

Alphanumeric

Any

All Request messages and OrderViewRS

Sender / TravelAgencySender / Contacts / Contact

Attribute

ContactType

Used to indicate to whom to send email confirmation emails and what information to include.

More information can be found here

Only as per allowed values

"itin_only"

or

"itin_and_price"

All Request messages and OrderViewRS

Sender / TravelAgencySender / Contacts / Contact / EmailContact / Address

Email to contact the Travel Agency

Mandatory for schema if 'EmailContact' tag is indicated.

Alphanumeric

Any

All Request messages and OrderViewRS

Sender / TravelAgencySender / Contacts / Contact / PhoneContact / Application

To indicate whether the Travel Agency phone is a fixed line or mobile.

Only as per allowed values

"BUSINESS"

or

"MOBILE"

All Request messages and OrderViewRS

Sender / TravelAgencySender / Contacts / Contact / PhoneContact / Number

Attribute

CountryCode

Phone number to contact the Travel Agency, with CountryCode.

<Number CountryCode="+34">666666666</Number>

Numeric

Any valid telephone number with Country code.

All Request messages and OrderViewRS

Sender / TravelAgencySender / Contacts / Contact / Name / Surname

The surname of the person to contact in the Travel Agency.

Mandatory for schema if 'Name' tag is indicated.

Alphanumeric

Any

All Request messages and OrderViewRS

Sender / TravelAgencySender / Contacts / Contact / Name / Given

The given name of the person to contact in the Travel Agency

Alphanumeric

Any

All Request messages and OrderViewRS

Sender / TravelAgencySender / IATA_Number

Sender IATA identifier:

IATA number (used by IATA accredited Travel Agents)

TIDs number  (recommended if you are not an IATA Accredited agent)

If using the IATA Delegation functionality for Servicing orders, and no CorporateSender information is included in the message, then the Servicing IATA's number is included here.

Numeric

7/8 Numbers

All Request messages and OrderViewRS

Sender / TravelAgencySender / OtherIDs / OtherID

Pseudo IATA (assigned by Iberia)

NDC Mandatory

Numeric

7/8 Numbers

All Request messages and OrderViewRS

Sender / TravelAgencySender / AgencyID

Presently, Iberia does not make use of this field.

Mandatory for Schema.

Alphanumeric

Any

All Request messages and OrderViewRS

Sender / CorporateSender / ID

ID for the Corporate. These are issued by Iberia and British Airways, and are sometimes referred to as a “JBID”.

Not applicable to OrderList.

NDC Mandatory

Alphanumeric

Identifier assigned by Iberia.

All Request messages and OrderViewRS

Sender / ORA_Sender / AirlineID

Code of the Offer/Order Responsible Airline sending the message. Used in the OCN message.

Two Alphabetical Letters

IB

OrderChangeNotif

Sender / ORA_Sender / Name

Name of the Offer/Order Responsible Airline sending the message. Used in the OCN message.

Alphabetical

Iberia

OrderChangeNotif

Participant Section

NAME

DESCRIPTION

FORMAT

ALLOWED/POSSIBLE VALUES

NDC SERVICES

<Party>

Participants / Participant / TravelAgencyParticipant / Name

Travel Agency Name.

This is the Travel Agent who is registered with Iberia and British Airways as managing travel for the above Corporate. A validation check is run against our Sales database.

Alphanumeric

Any

All Request messages, and OrderView when using CorporateSender.

All Servicing Request messages (except OrderListRQ), and OrderView when using IATA Delegation.

Participants / Participant / TravelAgencyParticipant / Type

Only when using IATA Delegation functionality.

Mandatory for IATA Delegation when CorporateSender is used.

This is used to indicate whether the TravelAgencyParticipant is the agency undertaking the Servicing or the agency that created or paid for the order.

see example: Party Elements

Only as per allowed values

"SERVICING_IATA"

or

"RESPONSIBLE_IATA"

This element is returned in all services except:

AirShopping

OfferPrice

OrderCreate

OrderList

Participants / Participant / TravelAgencyParticipant / Contacts / Contact

Attribute

ContactType

Used to indicate to whom to send email confirmation emails and what information to include

Only as per allowed values

"itin_only"

or

"itin_and_price"

All Request messages, and OrderView when using CorporateSender.

All Servicing Request messages (except OrderListRQ), and OrderView when using IATA Delegation.

Participants / Participant / TravelAgencyParticipant / Contacts / Contact / EmailContact / Address

 Email to contact the Agency

 Alphanumeric

Any

All Request messages, and OrderView when using CorporateSender.

All Servicing Request messages (except OrderListRQ), and OrderView when using IATA Delegation.

Participants / Participant / TravelAgencyParticipant / Contacts / Contact / PhoneContact / Application

To indicate whether the Travel Agency phone is a fixed line or mobile.

Only as per allowed values

"BUSINESS"

or

"MOBILE"

All Request messages, and OrderView when using CorporateSender.

All Servicing Request messages (except OrderListRQ), and OrderView when using IATA Delegation.

Participants / Participant / TravelAgencyParticipant / Contacts / Contact / PhoneContact / Number

Phone number to contact the Travel Agency

 Numeric

Any

All Request messages, and OrderView when using CorporateSender.

All Servicing Request messages (except OrderListRQ), and OrderView when using IATA Delegation.

Participants / Participant / TravelAgencyParticipant / Contacts / Contact / Name / Surname

The surname of the person to contact in the Travel Agency.

Mandatory for schema if 'Name' tag is indicated.

  Alphanumeric

Any

All Request messages, and OrderView when using CorporateSender.

All Servicing Request messages (except OrderListRQ), and OrderView when using IATA Delegation.

Participants / Participant / TravelAgencyParticipant / Contacts / Contact / Name / Given

The given name of the person to contact in the Travel Agency

 Alphanumeric

Any

All Request messages, and OrderView when using CorporateSender.

All Servicing Request messages (except OrderListRQ), and OrderView when using IATA Delegation.

Participants / Participant / TravelAgencyParticipant

Attribute

SequenceNumber

Sequence number related to the Participants, irrespective of their type (TravelAgency, Aggregator, etc…), sent in the request.

The order of the sequence number must follow the order in which the parties are connecting to our API. With the highest number being the party whose API key is being used to connect to us, and the lowest number (1) being the party in contact with the travelling passenger.

See example 5 below.

Numeric

All messages when there are more than one Participant.

Participants / Participant / TravelAgencyParticipant / IATA_Number

The Travel Agency’s unique identifier:

IATA number (if you have one)

TIDs number  (recommended if you do not have an IATA)

If using the IATA Delegation functionality for Servicing orders:

  • If no CorporateSender information is included in the message, then the Responsible IATA's number must be included here.

  • If CorporateSender information is included in the message, then the Servicing IATA’s number and the Responsible IATA's number must both be included here with their SequenceNumber and their applicable Type. The Servicing IATA must have the lowest SequenceNumber and the Responsible IATA must be the next number in the sequence. In both cases.

See examples below

7/8 Numeric

The identifier registered with Iberia.

All Request messages, and OrderView when using CorporateSender.

All Servicing Request messages (except OrderListRQ), and OrderView when using IATA Delegation.

 Participants / Participant / TravelAgencyParticipant / AgencyID

Iberia do not presently use this field, although it is mandatory as per the schema.

 Alphanumeric

Any

All Request messages.

 Participants / Participant / AggregatorParticipant

Attribute

SequenceNumber

Sequence number related to the Participants irrespective of their type (TravelAgency, Aggregator, etc…), sent in the request.

The order of the sequence number must follow the order in which the parties are connecting to our API. With the highest number being the party whose API key is being used to connect to us, and the lowest number (1) being the party in contact with the travelling passenger.

See example 5 below.

Numeric

All Request messages.

 Participants / Participant / AggregatorParticipant / AggregatorID

The unique identifier of the Aggregator. This can be any of the following:

IATA number (if you have one)

TIDs number  (recommended if you do not have an IATA)

Pseudo IATA(assigned by Iberia and British Airways)

7/8 Numeric

The identifier registered with Iberia.

This element is returned in all services except:

OrderViewRS

 Participants / Participant / AggregatorParticipant / Name

The name of the Aggregator as stored in our database associated to the AggregatorID. following:

Alphanumeric

The name registered with Iberia.

This element is ONLY used and returned in the:

OrderChangeNotification

Recipient Section - (only for OCN message)

NAME

DESCRIPTION

FORMAT

ALLOWED/POSSIBLE VALUES

NDC SERVICES

<Party>

Recipient / TravelAgencyRecipient / IATA_Number

Used in the OCN message to identify the IATA of the TravelAgency/Seller to whom this message is being directed.

7/8 Numeric

N/A

OrderChangeNotification

Recipient / TravelAgencyRecipient / AgencyID

Used in the OCN message to include the name, as per our database, of TravelAgency/Seller to whom this message is being directed.

Alphanumeric

N/A

OrderChangeNotification

In addition to the Common Sections, this service is called with the following data:

Query

 Query - OrderCreate

NAME

DESCRIPTION

FORMAT

ALLOWED/POSSIBLE VALUES

<Query / Order>

Offer

Attribute

OfferID

Attribute

Owner

Attribute

ResponseID

Id of a returned offer

Airline code

Id of the response

Alphanumeric

Alphabetical

Alphanumeric

Any

Any

Any

Offer / OfferItem

Attribute

OfferItemID

Id for OfferItem

Alphanumeric

Any

Offer / OfferItem / PassengerRefs

Type of passenger

Alphanumeric

Type of Passengers

Offer / OfferItem / ALaCarteSelection / Quantity

Quantity of ancillaries

Mandatory for schema if "ALaCarteSelection" tag is indicated

Numeric

Any

Offer / OfferItem / ALaCarteSelection / SegmentID

Id for the segment that applies the ancillaries

Alphanumeric

Any

Offer / OfferItem / SeatSelection / Row

Row for the seat

Mandatory for schema if "SeatSelection" tag is indicated

Numeric

Any

Offer / OfferItem / Seat Selection / Column

Column for the seat

Mandatory for schema if "SeatSelection" tag is indicated

Alphabetical

Any

Offer / OfferItem / ServiceSelection

Attribute

ServiceID

Id for the special service

NDC Mandatory for Special Needs selections.

Alphanumeric

Any

Offer / OfferItem / ServiceSelection / ServiceDefinitionID

Definition for the special service

Mandatory for schema if "ServiceSelection" tag is indicated

4 Alphabetical

Special Services

<Query / Payments / Payment>

Type

Payment Methods can vary depending on market and type of seller.

Please check here.

Alphabetical

  • CA (Cash)

  • CC (Credit Card)

  • MS (Voucher)

  • SF (ServiceFee)

--  This refers to Cash payment method  --

Method / Cash

Attribute

CashInd

Cash payment method.

Alphabetical

true

Amount

Attribute

Code

Total amount of the offer.

Code refers to currency code for payment.

Numeric

Any

Payer / ContactInfoRefs

Reference for the payer info, that must be associated correctly in the XML below.

In Cash Payment Method is OPTIONAL

Alphanumeric

Any valid reference associated in the XML below.

-- This refers to Credit Card method  – If Secure Payment applies additional info needed is defined below in 3DS INFO --

Method / PaymentCard

Attribute

refs

NDC Mandatory for 3DS and/or installments payment.

This is used to reference the associated 3DS info in PaymentCardSecureInfo ObjectKey, and/or the installment payment info in PaymentFormMetadata MetadataKey.

If both 3DS and installment payments are being used for the same Order, then the two references are included here together separated by a space.

Example: 

<PaymentCard refs="KEY_3DS KEY_QUOTAS">

Alphanumeric

Any

Method / PaymentCard / CardType 

Type of credit card

Alphanumeric

1-6 characters

Method / PaymentCard / SeriesCode

Series Code of credit card

Numeric

1-8 characters

Method / PaymentCard / CardHolderName

Card Holder Name

Alphanumeric

0-50 characters

Method / PaymentCard / CardHolderBillingAddress / Street

Street of the billing address of the cardholder.

NDC Mandatory that at least one field has to be filled in inside "CardHolderBillingAddress" tag.

Alphanumeric

If tag is indicated once, only first 40 characters will be considered

If tag is indicated twice, only first 80 characters will be considered

Method / PaymentCard / CardHolderBillingAddress / CityName

City of the Billing Address of cardholder

NDC Mandatory that at least one field has to be filled in inside "CardHolderBillingAddress" tag.

Alphanumeric

Only first 50 characters will be considered

Method / PaymentCard / CardHolderBillingAddress / StateProv

State Prov. of the Billing Address of cardholder

NDC Mandatory that at least one field has to be filled in inside "CardHolderBillingAddress" tag.

Alphanumeric

1-40 characters

Method / PaymentCard / CardHolderBillingAddress / PostalCode

Postal Code of the Billing Address of cardholder

NDC Mandatory that at least one field has to be filled in inside "CardHolderBillingAddress" tag.

Alphanumeric

2-10 characters

Method / PaymentCard / CardHolderBillingAddress / CountryCode

Country Code of the Billing Address of cardholder

NDC Mandatory that at least one field has to be filled in inside "CardHolderBillingAddress" tag.

Alphabetical

2 characters

Method / PaymentCard / CardNumber

Number of credit card

Numeric

1-9 characters

Method / PaymentCard / EffectiveExpireDate / Expiration

Effective expiration date of the credit card

Numeric

4 characters

Amount

Attribute

Code

Total amount of the offer.

Code refers to currency code for payment.

Numeric

Any

Payer / ContactInfoRefs

Reference for the payer info, that must be associated correctly in the XML below.

Alphanumeric

Any valid reference associated in the XML below.

-- This refers to Voucher payment method  --

Method / Voucher

Voucher payment method.

Alphabetical

true

Method / Voucher / Number 

Number of the voucher

Alphanumeric

any

Amount

Attribute

Code

Total amount of the offer.

Code refers to currency code for payment.

Numeric

Any

Payer / ContactInfoRefs

Reference for the payer info, that must be associated correctly in the XML below.

Alphanumeric

Any valid reference associated in the XML below.

-- This refers to Service Fee method  --

Method / Other / Remarks

Attribute

refs

References for all passengers of the order

Alphanumeric

any

Method / Other / Remarks / Remark

Service Fee payment method

Mandatory for schema if "Remarks" tag is indicated

Alphabetical

ServiceFee

Amount

Attribute

Code

Total amount of the Service Fee

Code refers to currency code for payment.

Numeric

Any

<Query / BookingReferences / BookingReference>

ID

External reference ID

Mandatory for Sender External Reference

Alphabetical

XRef

OtherID

Attribute

Name

This attribute must contain the senders IATA Number and will be matched against the Senders IATANumber from TravelAgencySender

Mandatory for Sender External Reference

Numeric

7/8 Numbers

OtherID

Sender's external reference

Mandatory for Sender External Reference

Alphanumeric

Any (Strings exceeding 30 chars will be truncated)

DataLists

 PassengerList

PassengerList

NAME

DESCRIPTION

FORMAT

ALLOWED/ POSSIBLE VALUES

NDC SERVICES

<DataLists / PassengerList>

Passenger

Attribute

PassengerID

A unique ID for each passenger.

Alphanumeric (Maximum → 20 characters)

This attribute can be filled with any value, but first character cannot be a number digit or a special character.

AirShoppingRQ/RS

OfferPriceRQ/RS

SeatAvailabilityRS

ServiceListRS

OrderCreateRQ

OrderViewRS

OrderChangeRQ

OrderReshopRQ/RS

Passenger / PTC

Passenger Type Code

3 Alphabetical 

Type of Passengers

AirShoppingRQ/RS

OfferPriceRQ/RS

SeatAvailabilityRS

ServiceListRS

OrderCreateRQ

OrderReshopRQ

OrderChangeRQ

OrderViewRS

Passenger / BirthDate

Birthdate of the passenger

Mandatory for secure flights for all passengers.

Mandatory for CHD and INF Passengers

Date (yyyy-mm-dd)

Date depends of the PTC

OrderChangeRQ

OrderCreateRQ

OrderViewRS

Passenger / Individual

Attribute

IndividualID

ID of the passenger (within this specific message), for internal use only.

Must be unique for each passenger in the message and can be referenced in Query / DataLists / ContactList / ContactInformation / IndividualRef

Alphanumeric (Maximum → 20 characters)

This attribute can be filled with any value, but first character cannot be a number digit or a special character.

OrderChangeRQ

OrderCreateRQ

Passenger / Individual / Gender

Gender of the passenger.

In secure flight:

  • Mandatory for infant passengers

  • Mandatory for all other passengers if the title is not indicated

  • Mandatory for secure flights and infant passengers in the OrderCreate message.

Alphabetical

  • Male

  • Female

  • Unspecified

OrderCreateRQ

OrderViewRS

OrderChangeRQ

Passenger / Individual / NameTitle

Title of the passenger
NDC supports followings fields (MR, MRS, MS, MISS).

If another value is introduced no error is shown, it is ignored unless the Secure Flight is involved.

In secure flight:

  • Optional for infant passengers

  • Mandatory for all other passengers if the gender is not indicated.

  • NDC Mandatory for secure flights

Alphabetical

  • MR

  • MRS

  • MS

  • MSS

  • MISS

OrderCreateRQ

OrderViewRS

OrderChangeRQ

Passenger / Individual / GivenName

Name of the passenger (which includes all given names, including first and second names).

Alphabetical

Any

OfferPriceRQ/RS

SeatAvailabilityRS

ServiceListRS

OrderCreateRQ

OrderViewRS

OrderChangeRQ

Passenger / Individual / Surname

Surname of the passenger.

If the name and surnames exceed the maximum number of characters allowed, the original name will be displayed, without trimming.

If agency has specified separated by a special character "@" first and second surname, it will be displayed as introduced with separator → e.g.: De la Morena@López)

Mandatory for schema if 'GivenName' tag is indicated.

Alphabetical

Any

OfferPriceRQ/RS

SeatAvailabilityRS

ServiceListRS

OrderCreateRQ

OrderViewRS

OrderChangeRQ

Passenger / Individual / SurnameSuffix

Can be used to indicate that the individual holds a position, educational degree, accreditation, office, or honor.

Can be used to distinguish between two passengers with exactly the same NameTitle, GivenName and Surname (i.e. John Smith, and John Smith Jr.)

Mandatory if NameTitle, GivenName and Surname are the same for two passengers.

Alphabetical

Any

  • JR

  • SR

OrderCreateRQ

OrderViewRS

OrderChangeRQ

Passenger / LoyaltyProgramAccount / Airline / AirlineDesignator

Frequent Flyer Airline ID

Mandatory if 'LoyaltyProgramAccount' tag is indicated

Alphanumeric

Any

OfferPriceRQ/RS

SeatAvailabilityRS

ServiceListRS

OrderCreateRQ

OrderViewRS

Passenger / LoyaltyProgramAccount / AccountNumber

Frequent Flyer number

On Business number

Mandatory if 'LoyaltyProgramAccount' tag is indicated in OrderCreate or OrderChange

Alphanumeric

Alphanumeric

Any

Any

OfferPriceRQ/RS

SeatAvailabilityRS

ServiceListRS

OrderCreateRQ

OrderViewRS

Passenger / FOID / FOID_Number

Number for the document

Mandatory for schema if 'FOID' tag is indicated.

Alphanumeric

PP (Passport): Any sequence of alpha numeric characters, also "-" and "." characters are accepted.

Valid examples: 1234-ABC, G.12345

NI (National ID): Only alpha numeric characters are allowed

Valid examples:

X1234567S

123456789012A

OrderChangeRQ

OrderCreateRQ

OrderViewRS

Passenger / FOID / FOID_Type

Type of the passenger ID Info

Mandatory for schema if 'FOID' tag is indicated.

2 Alphanumeric

  • PP (Passport) - Not valid for Spanish Resident and Large Family discounts

  • NI (National ID)

OrderChangeRQ

OrderCreateRQ

OrderViewRS

Passenger / InfantRef

Indicates the infant in lap associated to this adult.

If this tag is not indicated in the OrderCreateRQ, the infant in lap will be associated to the first adult in the Order automatically.

Recommended to ensure infant in lap is with correct adult.

Alphanumeric

Reference to infant PassengerID tag

OrderCreateRQ

OrderViewRS

Passenger / IdentityDocument / IdentityDocumentNumber

If Type of document is:

  • F1 - this will be the Spanish Resident certificate number 

(Optional if Spanish DNI/NIE is sent. Validated only if sent without Spanish DNI/NIE)

  • AI - this will be the Large Family certificate number

  • F - this should be the relevant fiscal information for the country.

    • The information should be sent using the following two or three elements separated by obliques "/":

      • Document Type

      • Document Number/ID

      • Company Name (optional)

    • examples:

      • "RUC/12345678X/BIG COMPANY"

      • “CUIL/9393933333

    • This fiscal information will be included on the tickets as required by local laws.

  • If any unacceptable information is sent and not included in the reservation/tickets, a warning message will be returned in the OrderViewRS.

  • Mandatory for schema if 'IdentityDocument' tag is indicated 

    NDC Mandatory for POS: PE, EC, AR and GT (FiscalID). For Infant passengers is not mandatory, so case that this document doesn’t come it will be assign the fiscal documentation from one of the Adults passengers.

Alphanumeric

  • 12 characters maximum for residence document

  • 20 characters maximum for large family document

  • 70 characters maximum for FiscalId

OrderChangeRQ

OrderCreateRQ

OrderViewRS

Passenger / IdentityDocument / IdentityDocumentType

Type of document

Mandatory for schema if 'IdentityDocument' tag is indicated  NDC Mandatory for POS: PE, EC, AR and GT (FiscalID)

2 Alphanumeric

  • F1 (Resident Discount)

  • AI (Additional information, Large Family Discount)

  • F (FiscalId)

  • Any other document

OrderChangeRQ

OrderCreateRQ

OrderViewRS

Passenger / ContactInfoRef

Reference for passenger contact info

Alphanumeric

Any

OrderChangeRQ

OrderCreateRQ

OrderViewRS

Passenger / Remark / Remark

In OrderCreate it is used to communicate the:

Municipality of residence / Community code for large family

<Remark>
  <!--Resident Discount Location Code-->
  <Remark>RESIDENT-380380</Remark>
</Remark>
<Remark>
  <!--Large Family Discount Community Code-->
  <Remark>LARGEFAMILY-380380</Remark>
</Remark>

In OrderView is is used to communicate the:

  • Type of discount applied and the Municipality/Community code for the passenger

  • Verified or not verified resident discount for passenger 

<Remark>
  <Remark>RESIDENT-380380</Remark>
</Remark>
<Remark>
  <Remark>LARGEFAMILY-380380</Remark>
</Remark>
<Remark>
  <Remark>UNVERIFIED RESIDENT STATUS</Remark>
</Remark>

Mandatory for schema if 'IdentityDocument' tag is indicated.

Alphanumeric

  • RESIDENT-Code of Location

  • LARGEFAMILY-Code of Community

INE - Relación de municipios y códigos por provincias

OrderChangeRQ

OrderCreateRQ

OrderViewRS

 ContactList

ContactList

NAME

DESCRIPTION

FORMAT

ALLOWED/POSSIBLE VALUES

NDC SERVICES

<DataLists / ContactList>

ContactInformation

Attribute

ContactID

Id of the contact information

Alphanumeric

Any

OrderCreateRQ
OrderChangeRQ
OrderViewRS
OrderReshopRS

ContactInformation / ContactProvided / ContactType

Identifier of field that agencies can include to specify the information to include in confirmation mails.

  • itin_only (omits the pricing

  • itin_and_price (which is the default value)

  • not_send_mail

Alphabetic

  • itin_only (omits the pricing

  • itin_and_price (which is the default value)

  • not_send_mail

OrderCreateRQ
OrderChangeRQ
OrderViewRS
OrderReshopRS

ContactInformation / ContactNotProvided

It's allowed to refuse to provide contact information for IATA agencies --> The passenger contact must include tag <ContactNotProvided/>

  • The agency's contact details (if any) are assigned to passengers who refuse.

  • If no passenger provides their contact details and not all refuse --> Error "You must indicate if the passengers have refused to provide their contact details"

  • If any passenger provides contact details --> It's optional to refuse

  • If all passengers refuse and no Agency Contact is provided --> Error

  • Refuse Tag for Non IATA Agencies --> Warning and no assignment is done

Empty

Empty

 OrderCreateRQ

ContactInformation / ContactProvided / EmailAddress / EmailAddressValue

Email address of the contact

Alphanumeric

Any

OrderCreateRQ
OrderChangeRQ
OrderViewRS
OrderReshopRS

ContactInformation / ContactProvided / Phone / Label

Identify type of phone number.

If the phone number is from an emergency contact, you must write at the OrderCreateRQ: <label>EMERGENCY</label>

Alphabetic

Any

OrderCreateRQ
OrderChangeRQ
OrderViewRS
OrderReshopRS

ContactInformation / ContactProvided / Phone / CountryDialingCode

Country Code associated to phone number if it is filled

Alphanumeric

Ej: (+34)

OrderCreateRQ
OrderChangeRQ
OrderViewRS
OrderReshopRS

ContactInformation / ContactProvided / Phone / PhoneNumber

Phone number of the contact

Numeric

Any

OrderCreateRQ
OrderChangeRQ
OrderViewRS
OrderReshopRS

ContactInformation / Individual / GivenName

Concatenated Name of emergency contact

Alphabetic

Any

OrderCreateRQ
OrderChangeRQ
OrderViewRS
OrderReshopRS

ContactInformation / Individual / Surname

Concatenated Surname of emergency contact

Alphabetic

Any

OrderCreateRQ
OrderChangeRQ
OrderViewRS
OrderReshopRS

 InstructionsList

InstructionList

NAME

DESCRIPTION

FORMAT

ALLOWED/POSSIBLE VALUES

NDC SERVICES

<DataLists / InstructionsList> 

Instruction

Attribute

ListKey

Id for the instruction to select sport equipment

 

Alphanumeric

 

Any

 

OrderCreateRQ

OrderRetrieveRQ

OrderViewRS

Instruction / FreeFormTextInstruction

Attribute

refs

Reference for passenger and segments associated to selected sport equipment

Alphanumeric

PassengerID and SegmentID

Valid example: “ADULT_01 IB303420231016“

OrderCreateRQ

OrderRetrieveRQ

OrderViewRS

Instruction / FreeFormTextInstruction / Remark

Selected sport equipment code

Alphanumeric

  • BIKE: BAGGAGE/SP/0EC

  • SKII: BAGGAGE/SP/0DD

  • GOLF: BAGGAGE/SP/0D4

  • SURF: BAGGAGE/SP/0D8

  • SCUB: BAGGAGE/SP/0EE

  • FISH: BAGGAGE/SP/0D6

OrderCreateRQ

OrderRetrieveRQ

OrderViewRS

 ServiceDefinitionList

ServiceDefinitionList

NAME

DESCRIPTION

FORMAT

ALLOWED/POSSIBLE VALUES

NDC SERVICES

<DataLists / ServiceDefinitionList>

ServiceDefinition

Attribute

ServiceDefinitionID

ID reference of the service

Alphabetical

Any (e.g.: DEAF, BAGSERVICE-1)

SeatAvailabilityRS
ServiceListRS

OrderCreateRQ
OrderViewRS

ServiceDefinition / Name

Name of the service

Alphanumeric

Any

SeatAvailabilityRS
ServiceListRS

OrderCreateRQ
OrderViewRS

ServiceDefinition / Encoding / RFIC

RFIC of booked ancillaries

Alphabetical

Any (e.g.: A, C)

SeatAvailabilityRS
ServiceListRS
OrderViewRS

ServiceDefinition / Encoding / Subcode

SubCode (RFISC) of booked ancillaries

Alphanumeric

Any (e.g.: 0B5, 0GO)

SeatAvailabilityRS
ServiceListRS
OrderViewRS

ServiceDefinition / BaggageAllowanceRef

Reference associated to hand/checked baggage included in passenger fare.

Alphanumeric

Any

OrderViewRS

ServiceDefinition / Descriptions / Description

Attribute

refs

Passenger identification associated to the service

Alphanumeric

Any

SeatAvailabilityRS
ServiceListRS
OrderViewRS

ServiceDefinition / Descriptions / Description / Text

Description of the service (Limited to 90 characters)

*Additional text is mandatory for DPNA to explain reason for assistance.

Alphanumeric

Any

SeatAvailabilityRS
ServiceListRS
OrderViewRS

ServiceDefinition / BookingInstructions / SSRCode

Ancillary SSR type on booking (used for legacy system compatibility)

Alphabetical

  • Ancillaries:

    • XBAG - Baggage

    • BDPR - Priority Boarding

    • BIKE - Bicycle (Sport Equipment)

    • SPEQ - Sport Equipment

    • RQST - Seat

  • Special Needs:

    • BLND - Blind Passenger

    • DEAF - Deaf Passenger

    • WCHR - Wheelchair for ramp

    • WCHS - Wheelchair for steps

    • DPNA - Disabled Passenger Needs Assistance*

SeatAvailabilityRS
ServiceListRS

OrderCreateRQ
OrderViewRS

ServiceDefinition / BookingInstructions / Method

Method. Always value= SSR

Alphabetical

SSR

SeatAvailabilityRS
ServiceListRS
OrderViewRS

ServiceDefinition / ServiceBundle

Contains one or more ServiceDefinitionRef when buying more that one of the same service

Alphanumeric

Any

ServiceListRS

ServiceDefinition / Detail / ServiceItemQuantityRules / MaximumQuantity

Maximum quantity of service

Numeric

Any

ServiceListRS

Metadata

 Forms of Payment

NAME

DESCRIPTION

FORMAT

ALLOWED/POSSIBLE VALUES

NDC SERVICES

<Metadata / Other / OtherMetadata / PaymentFormMetadatas>

PaymentFormMetadata

Attribute

refs

Reference from<PaymentCard ObjectKey>

Alphanumeric

Any

OfferPriceRS

PaymentFormMetadata

Attribute

MetadataKey

For 3DS info, this key is mandatory and can be filled in with any value:

“KEY_3DS”

For installments payment info, this key needs to match with installments reference in PaymentCard Refs:

“KEY_QUOTAS”

Alphanumeric

Any

OfferPriceRS

OrderCreate & OrderChange for payment in installments

For all payments made by Credit Card.

“KEY_AUTHORIZATION_CODE_1”

Alphanumeric

Any

OrderCreate & OrderChange - Payment

PaymentFormMetadata / Text

Installments payment info.

Number of installments and interest rate applied by card issuer.

Examples:

<Text>installments/1/0.00</Text>

<Text>installments/3/1.23</Text>

<Text>installments/9/variable</Text>

Alphanumeric

installments/n/X.XX

where n=number of installments.

where X.XX=interests rate in %

Valid example: installments/3/0.00

OfferPriceRS

OrderCreate & OrderChange for payment in installments

Authorization code payment info.

Example:

<Text>Authorization/2XS56F</Text>

Alphanumeric

Any

OrderCreate & OrderChange - Payment

PaymentFormMetadata / AugmentationPoint / AugPoint

Attribute

Owner

Airline code associated to 3DS Payment, in this case IB.

Alphabetical

IB

OrderCreate & OrderChange - Payment

PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment

Attribute

xsi:schemaLocation

Reference to IATA 3DS new schema info xsd for Secure Payment.

Alphanumeric

3-D Secure Payment

OrderCreate & OrderChange - Payment

PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment

Attribute

xmlns

Reference to IATA 3DS new schema info for Secure Payment.

Alphanumeric

3-D Secure Payment

OrderCreate & OrderChange - Payment

Mandatory if 'AugPoint ' tag is indicated

PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment

Attribute

xmlns:xsi

Reference to IATA 3DS new schema info for Secure Payment.

Alphanumeric

3-D Secure Payment

OrderCreate & OrderChange - Payment

Mandatory if 'AugPoint ' tag is indicated

PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment / PaymentCardSecureInfo

Attribute

ObjectKey

This Attribute is used to reference the applicable PaymentCard in the Payments section of this message.

Alphanumeric

Any

OrderCreate & OrderChange - Payment

PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment / PaymentCardSecureInfo / PaymentFunctions / PaymentMethodCriteria / PaymentCardCriteria / SecurePayerAuthenticationVersion / CardEnrollmentVersionText

The version of 3D-Secure for which the card is enrolled.

Alphanumeric

This field must contain the specific 3DS version used for authentication:

  • 1.0.2

  • 2.1.0

  • 2.2.0

OrderCreate & OrderChange - Payment

NDC Mandatory

PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment / PaymentCardSecureInfo / PaymentFunctions / PaymentMethodCriteria / PaymentCardCriteria / SecurePayerAuthenticationVersion / SupportedVersionText

Version of 3D-Secure supported. This tag is mandatory for schema.

Alphanumeric

This field must contain the specific 3DS version used for authentication:

  • 1.0.2

  • 2.1.0

  • 2.2.0

OrderCreate & OrderChange - Payment

Mandatory if 'PaymentCardSecureInfo' tag is indicated

PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment / PaymentCardSecureInfo / PaymentFunctions / PaymentProcessingDetails / PaymentMethod / PaymentCard / SecurePaymentVersion1 / PayerAuthenticationResponseText

Contains the indicators and fields that convey the result of the 3D Secure authentication transaction. Applicable for 3D Secure Version 1.x.x This tag is NDC mandatory for version 1.x.x and if is not included, an error will be returned.

This field is the authentication response for the 3-D Secure transaction. It is used to determine whether or not the customer has been authenticated by the card issuer. It must be included in the final authorization request. Example: eJzVWFmzosgSfudXdPQ8Gt1sbkzYRhQ7KCjI/sYOsimgoL/+lp7Tp5c5t2d67tMw8yv/WqiluJXS8WyyVFEQT28qz

Alphanumeric

Any

OrderCreate & OrderChange - Payment

NDC Mandatory for 3DS version 1.x.x

PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment / PaymentCardSecureInfo / PaymentFunctions / PaymentProcessingDetails / PaymentMethod / PaymentCard / SecurePaymentVersion2 / AuthenticationMerchantName

Contains all information for the result of 3D-Secure authentication process. Applicable for 3D Secure Version 2.x.x

This field is related to name of the merchant assigned by the Acquirer or Payment System.

Alphanumeric

Maximum → 40 characters

Any

OrderCreate & OrderChange - Payment

PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment / PaymentCardSecureInfo / PaymentFunctions / PaymentProcessingDetails / PaymentMethod / PaymentCard / SecurePaymentVersion2 / AuthenticationValue

Contains all information for the result of 3D-Secure authentication process. Applicable for 3D Secure Version 2.x.x

This field is related to 3DS authentication value returned. It is a cryptographic value generated by the ACS to provide a way, during authorisation processing, for the authorisation system to validate the integrity of the authentication result. The AV algorithm is defined by each Payment System.

Alphanumeric

Maximum → 28 characters

Any

OrderCreate & OrderChange - Payment

PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment / PaymentCardSecureInfo / PaymentFunctions / PaymentProcessingDetails / PaymentMethod / PaymentCard / SecurePaymentVersion2 / DirectoryServerTrxID

Contains all information for the result of 3D-Secure authentication process. Applicable for 3D Secure Version 2.x.x

This field is related to DS (Directory Server) transaction ID returned. Universally unique transaction identifier assigned by the Directory Server (DS) to identify a single transaction.

Alphanumeric

Maximum → 36 characters

Any

OrderCreate & OrderChange - Payment

PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment / PaymentCardSecureInfo / PaymentFunctions / PaymentProcessingDetails / PaymentMethod / PaymentCard / SecurePaymentVersion2 / ElectronicCommerceInd

Contains all information for the result of 3D-Secure authentication process. Applicable for 3D Secure Version 2.x.x

This field is related to 3DS ECI (electronic commerce indicator). Payment System-specific value provided by the ACS or DS to indicate the results of the attempt to authenticate the Cardholder.

This tag is NDC mandatory for version 2.x.x and if is not included, an error will be returned.

Some ECI values and the meaning of this is the following:

  • 01 → Authentication could not be completed but a proof of authentication attempt was provided SLI = 1 → MasterCard

  • 02 → Cardholder was successfully authenticated (SLI = 2) → MasterCard

  • 05 → This value means that the cardholder was authenticated by the issuer by verifying the cardholder’s password or identity information. The value is returned by the ACS in the Payer Authentication Response message when the cardholder successfully passed 3-D Secure payment authentication → Visa

  • 06 → This value means that the merchant attempted to authenticate the cardholder, but either the cardholder or issuer was not participating. The value should be returned by the ACS in the Authentication Response message for an Attempt Response. Additionally, merchants may use an ECI 6 in the authorization request when a Verify Enrollment of N is received from the Visa Directory Server → Visa

  • 07 → This value is set by the merchant when the payment transaction was conducted over a secure channel (for example, SSL/TLS), but payment authentication was not performed, or when the issuer responded that authentication could not be performed. An ECI 7 applies when either the Verify Enrollment or the Payer Authentication Response contains a U for Unable to Authenticate → Visa

Numeric

Two characters

Any

OrderCreate & OrderChange - Payment

NDC Mandatory for 3DS version 2.x.x

PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment / PaymentCardSecureInfo / PaymentFunctions / PaymentProcessingDetails / PaymentMethod / PaymentCard / SecurePaymentVersion2 / ProgramProtocolText

Contains all information for the result of 3D-Secure authentication process. Applicable for 3D Secure Version 2.x.x

This field is related to Program Protocol.

Alphanumeric

Any

OrderCreate & OrderChange - Payment

PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment / PaymentCardSecureInfo / PaymentFunctions / PaymentProcessingDetails / PaymentMethod / PaymentCard / SecurePaymentVersion2 / TrxStatusReasonText

Contains all information for the result of 3D-Secure authentication process. Applicable for 3D Secure Version 2.x.x

This field provides information on why the Transaction Status field has the specified value

Alphanumeric

Two characters

Any

OrderCreate & OrderChange - Payment

PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment / PaymentCardSecureInfo / PaymentFunctions / PaymentProcessingDetails / PaymentMethod / PaymentCard / SecurePaymentVersion2 / TrxStatusText

Contains all information for the result of 3D-Secure authentication process. Applicable for 3D Secure Version 2.x.x

This field indicates whether a transaction qualifies as an authenticated transaction or account verification.

Alphabetic

One character

Any

OrderCreate & OrderChange - Payment

PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment / PaymentCardSecureInfo / PaymentFunctions / PaymentProcessingDetails / PaymentMethod / PaymentCard / SecureProgram / EnrollmentStatusText

Contains all information for the result of 3D-Secure authentication process. Applicable for 3DS.

3D Secure Program Enrollment Status. Examples → CardNotEnrolled, CardEnrolled, CardMayBeEnrolled, Unknown

Alphabetic

Any

OrderCreate & OrderChange - Payment

PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment / PaymentCardSecureInfo / PaymentFunctions / PaymentProcessingDetails / PaymentMethod / PaymentCard / SecureProgram / SecurePaymentProgramName

Contains all information for the result of 3D-Secure authentication process. Applicable for 3DS.

Name of the secure payment program. Example → Verified by Visa.

Alphanumeric

Any

OrderCreate & OrderChange - Payment

PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment / PaymentCardSecureInfo / PaymentFunctions / PaymentProcessingDetails / PaymentMethod / PaymentCard / SellerOwnCardInd

Contains all information for the result of 3D-Secure authentication process. Applicable for 3DS.

When TRUE, indicates the seller is using their own card. If FALSE, customer card is being used.

Boolean

true/false

OrderCreate & OrderChange - Payment

Example OrderCreateRQ:

 XML Sample
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
   <soapenv:Header/>
   <soapenv:Body>
      <OrderCreateRQ Version="5.000" xmlns="http://www.iata.org/IATA/EDIST/2017.2">
         <PointOfSale>
            <Location>
               <CountryCode>ES</CountryCode>
            </Location>
         </PointOfSale>
         <Document>
            <ReferenceVersion>5.000</ReferenceVersion>
         </Document>
         <Party>
            <Sender>
               <TravelAgencySender>
                  <Name>AgencyName</Name>
                  <Contacts>
                     <Contact>
                        <EmailContact>
                           <Address>ibprueb2@gmail.com</Address>
                        </EmailContact>
                        <PhoneContact>
                           <Application>BUSINESS</Application>
                           <Number>+34666554433</Number>
                        </PhoneContact>
                        <Name>
                           <Surname>Martínez</Surname>
                           <Given>Pepe</Given>
                        </Name>
                     </Contact>
                  </Contacts>
                  <IATA_Number>12345678</IATA_Number>
                  <AgencyID>TRAVEL AGENCY</AgencyID>
               </TravelAgencySender>
            </Sender>
         </Party>
         <Query>
            <Order>
               <Offer OfferID="IB700fb61f0530487abb23d62f37d536c6OC" Owner="IB" ResponseID="Qm9va2luZ0AxNjI3NDYxNzk2ODY4LUdjUmtu">
                  <OfferItem OfferItemID="IB700fb61f0530487abb23d62f37d536c6OC_01">
                     <PassengerRefs>ADULT_01 ADULT_02 ADULT_03 ADULT_04</PassengerRefs>
                  </OfferItem>
               </Offer>
               <!--Introducción de los servicios especiales-->
               <Offer OfferID="ALACARTE_SSR_IB7e5c68abeb5e482c839c6efbdf4472ac" Owner="IB" ResponseID="Qm9va2luZ0AxNjI3NDYxNzk2ODY4LUdjUmtu">
                  <OfferItem OfferItemID="IB700fb61f0530487abb23d62f37d536c6OC_DEAF">
                     <PassengerRefs>ADULT_01</PassengerRefs>
                     <ServiceSelection ServiceID="SSR_SN_c9db38dc-ada9-4955-b9db-7a16875ed74f">
                        <ServiceDefinitionID>SPECIAL_NEED-DEAF</ServiceDefinitionID>
                     </ServiceSelection>
                  </OfferItem>
                  <OfferItem OfferItemID="IB700fb61f0530487abb23d62f37d536c6OC_SVAN">
                     <PassengerRefs>ADULT_01</PassengerRefs>
                     <ServiceSelection ServiceID="SSR_SN_5e6fb112-7c1d-4242-92a4-b7b48408cacf">
                        <ServiceDefinitionID>SPECIAL_NEED-SVAN</ServiceDefinitionID>
                     </ServiceSelection>
                  </OfferItem>
               </Offer>
            </Order>
            <Payments>
               <Payment>
                  <Type>MS</Type>
                  <Method>
                     <Voucher>
                        <Number>BONO100EUR</Number>
                     </Voucher>
                  </Method>
                  <Amount Code="EUR">1243.56</Amount>
                  <Payer>
                     <ContactInfoRefs>Payer</ContactInfoRefs>
                  </Payer>
               </Payment>
               <Payment>
                  <Type>CA</Type>
                  <Method>
                     <Cash CashInd="true"/>
                  </Method>
                  <Amount Code="EUR">0</Amount>
                  <Payer>
                     <ContactInfoRefs>Payer</ContactInfoRefs>
                  </Payer>
               </Payment>
            </Payments>
            <DataLists>
               <PassengerList>
                  <Passenger PassengerID="ADULT_01">
                     <PTC>ADT</PTC>
                     <Birthdate>1993-12-23</Birthdate>
                     <Individual IndividualID="IND_ADULT_01">
                        <Gender>Male</Gender>
                        <NameTitle>MR</NameTitle>
                        <GivenName>ADULTO</GivenName>
                        <Surname>UNO PRUEBA</Surname>
                     </Individual>
                     <FOID>
                        <FOID_Number>12345678Z</FOID_Number>
                        <FOID_Type>NI</FOID_Type>
                     </FOID>
                     <ContactInfoRef>REFUSE_CONTACT</ContactInfoRef>
                  </Passenger>
                  <Passenger PassengerID="ADULT_02">
                     <PTC>ADT</PTC>
                     <Birthdate>1987-08-23</Birthdate>
                     <Individual IndividualID="IND_ADULT_02">
                        <Gender>Female</Gender>
                        <NameTitle>MRS</NameTitle>
                        <GivenName>ADULTA</GivenName>
                        <Surname>UNA PRUEBA</Surname>
                     </Individual>
                     <FOID>
                        <FOID_Number>75481546P</FOID_Number>
                        <FOID_Type>NI</FOID_Type>
                     </FOID>
                     <ContactInfoRef>REFUSE_CONTACT</ContactInfoRef>
                  </Passenger>
                  <Passenger PassengerID="ADULT_03">
                     <PTC>ADT</PTC>
                     <Birthdate>1993-12-23</Birthdate>
                     <Individual IndividualID="IND_ADULT_03">
                        <Gender>Male</Gender>
                        <NameTitle>MR</NameTitle>
                        <GivenName>ADULTO</GivenName>
                        <Surname>TRES PRUEBA</Surname>
                     </Individual>                     
                     <FOID>
                        <FOID_Number>25369424X</FOID_Number>
                        <FOID_Type>NI</FOID_Type>
                     </FOID>
                     <ContactInfoRef>REFUSE_CONTACT</ContactInfoRef>
                  </Passenger>
                  <Passenger PassengerID="ADULT_04">
                     <PTC>ADT</PTC>
                     <Birthdate>1987-08-23</Birthdate>
                     <Individual IndividualID="IND_ADULT_04">
                        <Gender>Female</Gender>
                        <NameTitle>MRS</NameTitle>
                        <GivenName>ADULTA</GivenName>
                        <Surname>CUATRO PRUEBA</Surname>
                     </Individual>
                     <FOID>
                        <FOID_Number>74582559E</FOID_Number>
                        <FOID_Type>NI</FOID_Type>
                     </FOID>
                     <ContactInfoRef>REFUSE_CONTACT</ContactInfoRef>
                  </Passenger>
               </PassengerList>
               <ContactList>
                  <ContactInformation ContactID="Payer">
                     <ContactType>Payer</ContactType>
                     <ContactProvided>
                        <EmailAddress>
                           <EmailAddressValue>pasajeroib@bylup.com</EmailAddressValue>
                        </EmailAddress>
                     </ContactProvided>
                     <IndividualRef>IND_ADULT_01</IndividualRef>
                  </ContactInformation>
                  <ContactInformation ContactID="REFUSE_CONTACT">
                     <ContactNotProvided/>
                  </ContactInformation>
               </ContactList>
               <ServiceDefinitionList>
                  <ServiceDefinition ServiceDefinitionID="SPECIAL_NEED-DEAF">
                     <Name>Deaf Passenger</Name>
                     <Descriptions>
                        <Description refs="ADULT_01">
                           <Text>Request Service Animal if travelling with one*/?()</Text>
                        </Description>
                     </Descriptions>
                     <BookingInstructions>
                        <SSRCode>DEAF</SSRCode>
                     </BookingInstructions>
                  </ServiceDefinition>
                  <ServiceDefinition ServiceDefinitionID="SPECIAL_NEED-SVAN">
                     <Name>Service Animal</Name>
                     <Descriptions>
                        <Description refs="ADULT_01">
                           <Text>Service Animal travelling in the cabin with Blind, Deaf, Disabled passengers or Certified Instructors. Specify breed and weight of animal</Text>
                        </Description>
                     </Descriptions>
                     <BookingInstructions>
                        <SSRCode>SVAN</SSRCode>
                     </BookingInstructions>
                  </ServiceDefinition>
               </ServiceDefinitionList>
            </DataLists>
         </Query>
      </OrderCreateRQ>
   </soapenv:Body>
</soapenv:Envelope>

Response Body

OrderViewRS

Examples of messages with complete flows can be downloaded from here.

Error messages

For further information about all kind of error messages, please go to the following link:

Errors

  • No labels