Passengers & Their Information
For Passenger Contact information please see:
Order Contacts & Communications
Passenger Type Codes
The following are the types of passengers supported by Iberia NDC.
Code | Value | Description |
|---|---|---|
ADT | Adult | Standard adult passenger |
CHD | Child | Children between the ages of 2 and 11 inclusive for the entire duration of the itinerary |
INF | Infant in lap | Infants under the age of two for the entire duration of the itinerary, who do not occupy a seat. |
Identity
The NDC OrderCreate supports two elements where identity information can be sent, FOID and IdentityDocument.
FOID
This is a legacy concept taken from the SSR FOID in the IATA AIRIMP, but still used today in legacy systems.
Today we accept only Passport (PP) and National ID (NI).
This information today, in our NDC API and in the underlying legacy systems, is used to define the Form of ID of passengers for the following three purposes.
Spanish Resident Discount, where, national ID is mandatory for adults 14 years and older.
Flights departing certain markets (POC), for example Peru (PE) and Ecuador (EC).
Services operated by Renfe, National ID is mandatory.
Two different passengers can only introduce the same document identification if market is different from ES (Due to some countries allowing multipax passports)
IdentityDocument
Today this element is used, in our NDC API for the following purposes:
Spanish Discounts (Resident & Large Family)
Fiscal Identity
APIS (Advance Passenger Information System)
The following are the document types we accept:
Used For | IdentityDocumentType Code |
|---|---|
Spanish Resident Discount Certificate Number | F1 |
Spanish Large Family Discount Certificate Number | AI |
FiscalID | F |
Passport | PT |
National ID Card | 709 |
Permanent Resident Card | 710 |
Redress Number | AEA |
Visa | VI |
Known Traveller Number | CR |
As of November 2025, if no FOID element is sent, and identity information is required, then Iberia will use the first instance of IdentityDocument information, for a passenger, with passport (PT), National ID Card (709) or Permanent Resident Card (710) to fill the need.
As these two elements in the NDC messages serve the same purpose, our intention is to use the IdentityDocument and eventually phase out the use of the FOID element. In the meantime, we will do that mentioned in the previous paragraph. In the OrderViewRS messages you may receive the same document information in both the IdentityDocument and FOID elements.
FiscalID
This should be the relevant fiscal information required by certain government authorities.
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
PP/A1234546789
This fiscal information will be transmitted to the relevant government authorities in whatever way the market requires. This means it may be included on the tickets, and or any other reporting files send to the governments that legally require it.
Frequent Flyers
We now accept Frequent Flyer details in the AirShoppingRQ message, in addition to the OfferPriceRQ and OrderCreateRQ.
In addition, in the AirShoppingRQ and OfferPriceRQ we now accept the AirlineDesignator and AccountNumber only, with or without the name elements.
Upon receiving the name elements in the OrderCreateRQ we will validate them against those for the Frequent Flyer details, and if validation fails an error will be returned, and the booking will fail.
If Frequent Flyer details are included in the AirShoppingRQ and OfferPriceRQ, but have been omitted from the OrderCreate, then we will proceed to create the booking with the Frequent Flyer details stored in the Offer. Therefore if the Frequent Flyer details are not required in the Order, then the Shopping process needs to be initiated again from the beginning.
If Frequent Flyer details are sent in the shopping flow (AirShopping or OfferPrice) then any applicable tier information will be used to obtain any applicable benefits, such as when Ancillary Services are requested using the ServiceList and/or SeatAvailability.
If Frequent Flyer information is included in the OrderCreate that is different to that send in the shopping flow, then the booking will fail and an error will be returned.
As of today, we accept only one Frequent Flyer number per adult or child passenger.
If multiple Iberia or Other Airlines (OAL) Frequent Flyers are sent for a passenger, they are ignored and a warning is returned in the response.
If multiple Frequent Flyers are sent for a passenger, then if only one of them is Iberia then it will be used, and the OAL ones will be ignored. A warning will be returned indicating that we have ignored the OAL ones.
If just one OAL FF is included, then this will be added to the booking without validation.
The Frequent Flyer details are passed as follows:
With name:
<Passenger PassengerID="ADT_01">
<PTC>ADT</PTC>
<Individual>
<GivenName>ARMANDO</GivenName>
<Surname>JALEIO</Surname>
</Individual>
<LoyaltyProgramAccount>
<Airline>
<AirlineDesignator>IB</AirlineDesignator>
</Airline>
<AccountNumber>28432524</AccountNumber>
</LoyaltyProgramAccount>
</Passenger>Without name:
<Passenger PassengerID="AD_01">
<PTC>ADT</PTC>
<LoyaltyProgramAccount>
<Airline>
<AirlineDesignator>IB</AirlineDesignator>
</Airline>
<AccountNumber>28432524</AccountNumber>
</LoyaltyProgramAccount>
</Passenger>Frequent Flyer numbers can be added or changed in an Order simply using the OrderChange message and including the <PassengerServicing> section with the new information.
<Query>
<OrderID>IB1223c05e830541c684ea8818a89a4e5aOP</OrderID>
<PassengerServicing>
<New PassengerID="ADULT_01">
<LoyaltyProgramAccount>
<!--Passenger's FQTV details-->
<Airline>
<AirlineDesignator>IB</AirlineDesignator>
</Airline>
<AccountNumber>12341234</AccountNumber>
</LoyaltyProgramAccount>
<ActionType>Add</ActionType>
</New>
</PassengerServicing>
</Query>The deletion of an existing Frequent Flyer number from a booking is not presently available.
Iberia Club
We accept Frequent Flyer numbers of any airline, although we only validate Iberia Club. Accrual of Avios is only on those airlines with whom we have agreements, such as our Oneworld Alliance partners.
We only accept one Frequent Flyer number in the booking for each adult or child passenger (not infants). To update/replace an existing Frequent Flyer number you simply include the new one, which will replace the existing.
When the Iberia Club details, are passed to us they are validated, and if successful, used to obtain any applicable benefits, and added to the booking. In subsequent servicing flows any applicable advantages are also applied.
Any purchases prior to the inclusion of validated Iberia Club details in the Order will not benefit from any advantages, and will not be retroactive.
If Iberia Club validation fails, we will continue with the flow and return a warning in the response.
If more than one Iberia Frequent Flyer is sent for a passenger in the AirShopingRQ, OfferPriceRQ or OrderCreateRQ :
The system will ignore them all as this is not possible, and the processing will proceed, and the following warning will be returned in the response:
<NDC_DIST_FF_1001 Code="486"> “Frequent Flyer not included due to system error”.
If multiple airlines Frequent Flyers are sent for a passenger in the AirShopingRQ, OfferPriceRQ or OrderCreateRQ:
If one of them is an Iberia Frequent Flyer:
The system will keep, and use, the Iberia one, and the following warning will be returned:
<NDC_DIST_FF_1002 Code="486"> ”Only the Iberia Frequent Flyer has been included, the rest of the Frequent Flyers from other companies have not been included”.
OAL (Other Airlines) Frequent Flyers
Iberia has reciprocal agreements with Other Airlines (OAL), in particular with those in the Oneworld Alliance, whereby the customer can accrue Avios on each others services. So an Iberia Club member can accrue Avios when flying on a partner carrier, and vice versa.
Several FF sent in an OfferPriceRQ or OrderCreateRQ:
If multiple airlines Frequent Flyers are sent for a passenger in the AirShopingRQ, OfferPriceRQ or OrderCreateRQ:
If all of them are OAL Frequent Flyers (and none are IB):
The system will not use any of them, and the following warning will be returned:
<NDC_DIST_FF_1001 Code="486"> “Frequent Flyer not included due to system error”.
On Business
For more commercial information on On Business please see the On Business web.
This is a type of Frequent Flyer program for SMEs (PyMes). By entering the On Business ID in the booking points can be accrued.
The information is sent to us (only in OrderCreateRQ) in the same way that an Iberia Club is sent, with IB as the airline and the account number always starting with OB.
<LoyaltyProgramAccount>
<Airline>
<AirlineDesignator>IB</AirlineDesignator>
</Airline>
<AccountNumber>OB12345678</AccountNumber>
</LoyaltyProgramAccount>Personal Frequent Flyer Avios can also be earned at the same time if the passengers Frequent Flyer details are also entered in the booking.
Example of Iberia Club with On Business:
<LoyaltyProgramAccount>
<!--Passenger's FQTV (Frequent Traveler) details-->
<Airline>
<AirlineDesignator>IB</AirlineDesignator>
</Airline>
<AccountNumber>21204896</AccountNumber>
</LoyaltyProgramAccount>
<LoyaltyProgramAccount>
<Airline>
<AirlineDesignator>IB</AirlineDesignator>
</Airline>
<AccountNumber>OB12345678</AccountNumber>
</LoyaltyProgramAccount>On Business numbers can be added or changed in an Order in the same way as the Frequent Flyer, simply using the OrderChange message and including the <PassengerServicing> section with the new information.
To update an existing On Business number you simply include the new one.
The deletion of an existing On Business number is not presently available.