Versions Compared

Old Version 3

changes.mady.by.user Alvaro Chaparro

Saved on

compared with

New Version Current

changes.mady.by.user Alvaro Chaparro

Saved on

Key

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

...

Excerpt
nameSenderSection

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

Info

Attribute

Contact@ContactTypeContactType

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

Info

Attribute

Number@CountryCodeCountryCode

Phone number to contact the Travel Agency, with CountryCode.

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

All Request messagesOrderChangeNotif

Sender / ORA_Sender / Name

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

Alphabetical

Iberia

All Request messagesOrderChangeNotif

Excerpt
nameParticipantSection

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

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: https://transform.atlassian.net/wiki/spaces/NDCDOC/pages/3968073922/Party+Elements#6.-When-using-IATA-Delegation .

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

Info

Attribute

Contact@ContactTypeContactType

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

Info

Attribute

TravelAgencyParticipant@SequenceNumber

AggregatorParticipant@SequenceNumberSequenceNumber

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

Info

Attribute

AggregatorParticipant@SequenceNumberSequenceNumber

Sequence number related to the Participantsirrespective 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

This element is returned in all services except:

OrderViewRSAll 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

Excerpt
nameRecipientSection

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

...

Expand
titleExample Sender with no Aggregator (Direct Connect)) in request messages and in the OrderViewRS
Code Block
languagexml
<Party>
	<Sender>
		<TravelAgencySender>
			<Name>TEST TRAVEL AGENCY</Name>
			<Contacts>
				<Contact>
					<EmailContact>
						<Address>agencia@prueba.com</Address>
					</EmailContact>
					<PhoneContact>
						<Application>MOBILE</Application>
						<Number>+34#########</Number>
					</PhoneContact>
					<Name>
						<Surname>Perez-Nieto</Surname>
						<Given>Pepe</Given>
					</Name>
				</Contact>
			</Contacts>
			<IATA_Number>########</IATA_Number>
			<AgencyID>TESTTRAVELAGENCY</AgencyID>
		</TravelAgencySender>
	</Sender>
</Party>

2. TravelAgencySender with one or more Aggregators:

Expand
titleExample TraveAgencySender TravelAgencySender and Aggregator Participant in request messages:
Code Block
languagexml
<Party>
    <Sender>
        <TravelAgencySender>
			<Name>TEST TRAVEL AGENCY</Name>
			<Contacts>
				<Contact>
					<EmailContact>
						<Address>agencia@prueba.com</Address>
					</EmailContact>
					<PhoneContact>
						<Application>MOBILE</Application>
						<Number>+34#########</Number>
					</PhoneContact>
					<Name>
						<Surname>Perez-Nieto</Surname>
						<Given>Pepe</Given>
					</Name>
				</Contact>
			</Contacts>
			<IATA_Number>########</IATA_Number>
			<AgencyID>TESTTRAVELAGENCY</AgencyID>
		</TravelAgencySender>
	</Sender>
	<Participants>
		<Participant>
			<AggregatorParticipant SequenceNumber="1">
				<AggregatorID>########</AggregatorID>
			</AggregatorParticipant>
		</Participant>
	</Participants>
</Party>

Expand
titleExample TravelAgencySender and two Aggregator Participants in request messages:
Code Block
languagexml
<Party>
	<Sender>
        <TravelAgencySender>
			<Name>TEST TRAVEL AGENCY</Name>
			<Contacts>
				<Contact>
					<EmailContact>
						<Address>agencia@prueba.com</Address>
					</EmailContact>
					<PhoneContact>
						<Application>MOBILE</Application>
						<Number>+34#########</Number>
					</PhoneContact>
					<Name>
						<Surname>Perez-Nieto</Surname>
						<Given>Pepe</Given>
					</Name>
				</Contact>
			</Contacts>
			<IATA_Number>########</IATA_Number>
			<AgencyID>TESTTRAVELAGENCY</AgencyID>
		</TravelAgencySender>
	</Sender>
	<Participants>
		<Participant>
			<AggregatorParticipant SequenceNumber="1">
				<AggregatorID>########</AggregatorID>
			</AggregatorParticipant>
		</Participant>
		<Participant>
			<AggregatorParticipant SequenceNumber="2">
				<AggregatorID>########</AggregatorID>
			</AggregatorParticipant>
		</Participant>
	</Participants>
</Party>

...

Expand
titleExample Corporate with TravelAgencyParticipant in request messages:
Code Block
languagexml
<Party>
	<Sender>
		<CorporateSender>
			<ID>XXXXXXXX</ID>
		</CorporateSender>
	</Sender>
	<Participants>
		<Participant>
			<TravelAgencyParticipant SequenceNumber="1">
				<Name>AgencyName</Name>
				<Contacts>
					<Contact>
						<EmailContact>
							<Address>AgencyMail@xxx.com</Address>
						</EmailContact>
						<PhoneContact>
							<Application>BUSINESS</Application>
							<Number>+34#########</Number>
						</PhoneContact>
						<Name>
							<Surname>MartÌnez<<Surname>Martinez</Surname>
							<Given>Pepe</Given>
						</Name>
					</Contact>
				</Contacts>
				<IATA_Number>########</IATA_Number>
				<AgencyID>TravelAgent</AgencyID>
			</TravelAgencyParticipant>
		</Participant>
	</Participants>
</Party>

4. CorporateSender with just

...

TravelAgencyParticipant:

Expand
titleExample Corporate with TravelAgencyParticipant in request messages:
Code Block
languagexml
<Party>
		<Sender>
		<CorporateSender>
			<ID>XXXXXXXX</ID>
		</CorporateSender>
	</Sender>
	<Participants>
		<Participant>
		<TravelAgencyParticipant SequenceNumber="1">
				<Name>AgencyName</Name>
				<Contacts>
					<Contact>
						<EmailContact>
							<Address>AgencyMail@xxx.com</Address>
						</EmailContact>
						<PhoneContact>
							<Application>BUSINESS</Application>
							<Number>+34#########</Number>
						</PhoneContact>
						<Name>
							<Surname>MartÌnez<<Surname>Martinez</Surname>
							<Given>Pepe</Given>
						</Name>
					</Contact>
				</Contacts>
				<IATA_Number>########</IATA_Number>
				<AgencyID>TravelAgent</AgencyID>
			</TravelAgencyParticipant>
			</Participant>
	</Participants>
</Party>

5. CorporateSender with

...

TravelAgencyParticipant and Aggregator Participant:

Expand
titleExample Corporate with TraveAgencyParticipant TravelAgencyParticipant and Aggregator Participant in request messages:
Code Block
languagexml
<Party>
	<Sender>
		<CorporateSender>
			<ID>XXXXXXXX</ID>
		</CorporateSender>
	</Sender>
	<Participants>
		<Participant>
			<TravelAgencyParticipant SequenceNumber="1">
				<Name>AgencyName</Name>
				<Contacts>
					<Contact>
						<EmailContact>
							<Address>AgencyMail@xxx.com</Address>
						</EmailContact>
						<PhoneContact>
							<Application>BUSINESS</Application>
							<Number>+34#########</Number>
						</PhoneContact>
						<Name>
							<Surname>Martínez<<Surname>Martinez</Surname>
							<Given>Pepe</Given>
						</Name>
					</Contact>
				</Contacts>
				<IATA_Number>########</IATA_Number>
				<AgencyID>firstAgency</AgencyID>
			</TravelAgencyParticipant>
		</Participant>
		<Participant>
			<AggregatorParticipant SequenceNumber="2">
				<AggregatorID>########</AggregatorID>
			</AggregatorParticipant>
		</Participant>
	</Participants>
</Party>

...

Expand
titleExample TravelAgencySender with AggregatorParticipant using IATA Delegation in request messages
Code Block
languagexml
<Party>
	<Sender>
<TravelAgencySender>
			<Name>TEST TRAVEL AGENCY</Name>
			<Contacts>
				<Contact>
					<EmailContact>
						<Address>agencia@prueba.com</Address>
					</EmailContact>
					<PhoneContact>
						<Application>MOBILE</Application>
						<Number>+34#########</Number>
					</PhoneContact>
					<Name>
						<Surname>Perez-Nieto</Surname>
						<Given>Pepe</Given>
					</Name>
				</Contact>
			</Contacts>
			<IATA_Number>########</IATA_Number>
			<AgencyID>TESTTRAVELAGENCY</AgencyID>
		</TravelAgencySender>
	</Sender>
	<Participants>
		<Participant>
			<TravelAgencyParticipant SequenceNumber="2">
				<IATA_Number>78298065<Number>12345678</IATA_Number>
				<AgencyID>Barceló<<AgencyID>Travel Agency</AgencyID>
			</TravelAgencyParticipant>
		</Participant>
		<Participant>
			<AggregatorParticipant SequenceNumber="3">
				<AggregatorID>00010113<<AggregatorID>11111111</AggregatorID>
			</AggregatorParticipant>
		</Participant>
	</Participants>
</Party>

REMEMBER - - When using IATA Delegation, the Sender is always the Servicing IATA and the TravelAgencyParticipant is always the Responsible IATA. Therefore, no Type element is necessary to identify the role each is playing.

...

Expand
titleExample Corporate with TraveAgencyParticipants TravelAgencyParticipants and Aggregator Participant in request messages:
Code Block
languagexml
<Party>
	<Sender>
		<CorporateSender>
			<ID>IN3401ES<<ID>IN0000ES</ID>
		</CorporateSender>
	</Sender>
	<Participants>
		<Participant>
			<TravelAgencyParticipant SequenceNumber="1">
				<Type>SERVICING_IATA</Type>
				<IATA_Number>11112220<Number>12345678</IATA_Number>
				<AgencyID>AGENCY_B<<AgencyID>Travel Agency</AgencyID>
			</TravelAgencyParticipant>
		</Participant>
		<Participant>
			<TravelAgencyParticipant SequenceNumber="2">
				<Type>RESPONSIBLE_IATA</Type>
				<IATA_Number>78298065<Number>12345678</IATA_Number>
				<AgencyID>Barceló<<AgencyID>Travel Agency</AgencyID>
			</TravelAgencyParticipant>
		</Participant>
		<Participant>
			<AggregatorParticipant SequenceNumber="3">
				<AggregatorID>00010113<<AggregatorID>11111111</AggregatorID>
			</AggregatorParticipant>
		</Participant>
	</Participants>
</Party>

REMEMBER - - When CorporateSender is included in the Party section of the message, the Type element must be included for each of the TravelAgencyParticipants to indicate the role each of them is playing in the delegation process.

New NDC Footer.pngImage Added