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 | 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 | 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 | 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 |