Versions Compared

Old Version 2

changes.mady.by.user Valentina Maio

Saved on

compared with

New Version 3

changes.mady.by.user Alvaro Chaparro

Saved on

Key

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

...

Section Elements

Insert excerpt
NDC2:New 17.2 COMBINEDNDC2:New 17.2 COMBINEDAPI Messages with Examples
API Messages with Examples
nameLegend
nopaneltrue

Excerpt
nameSenderSection

Sender Section

NAME

DESCRIPTION

FORMAT

ALLOWED/POSSIBLE VALUES

NDC SERVICES

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

Sender / TravelAgencySender / Contacts

Info

Attribute

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

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

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

Sender / TravelAgencySender / Contacts / Contact / PhoneContact

Info

Attribute

Number@CountryCode

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

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

Sender / TravelAgencySender / Contacts / Contact / Name / Given

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

Alphanumeric

Any

All Request messages

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

Sender / TravelAgencySender / OtherIDs / OtherID

Pseudo IATA (assigned by Iberia)

NDC Mandatory

Numeric

7/8 Numbers

All Request messages

Sender / TravelAgencySender / AgencyID

Presently, Iberia does not make use of this field.

Mandatory for Schema.

Alphanumeric

Any

All Request messages

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

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 messages

Sender / ORA_Sender / Name

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

Alphabetical

Iberia

All Request messages

...

Expand
titleExample TravelAgencySender with AggregatorParticipant using IATA Delegation
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</IATA_Number>
				<AgencyID>Barceló</AgencyID>
			</TravelAgencyParticipant>
		</Participant>
		<Participant>
			<AggregatorParticipant SequenceNumber="3">
				<AggregatorID>00010113</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 and Aggregator Participant:
Code Block
languagexml
<Party>
	<Sender>
		<CorporateSender>
			<ID>IN3401ES</ID>
		</CorporateSender>
	</Sender>
	<Participants>
		<Participant>
			<TravelAgencyParticipant SequenceNumber="1">
				<Type>SERVICING_IATA</Type>
				<IATA_Number>11112220</IATA_Number>
				<AgencyID>AGENCY_B</AgencyID>
			</TravelAgencyParticipant>
		</Participant>
		<Participant>
			<TravelAgencyParticipant SequenceNumber="2">
				<Type>RESPONSIBLE_IATA</Type>
				<IATA_Number>78298065</IATA_Number>
				<AgencyID>Barceló</AgencyID>
			</TravelAgencyParticipant>
		</Participant>
		<Participant>
			<AggregatorParticipant SequenceNumber="3">
				<AggregatorID>00010113</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.