Party and Sender Definition


Data Model

Definition

Every API request should contain the <Party>  element to identify the requesting party.

 User Guidance

<Party>

ElementDetailsOptional/Mandatory
<Party>
M
<Sender>Message sender informationM
<TravelAgencySender>

Specify the travel agency details

Populate TravelAgencySender section only if the request is originated by the Travel Agent

M
<Name>

Travel agency name

Example: ABC

O
<Contacts>

This is an optional element in NDC schema but for calling BA service this must be passed with requesting agent’s email address only if the requesting agent is an IATA agent

O
<Contact>
M
<AddressContact>

Agents Address Details

O
<Street>Street. Examples: Main Street, 100 Main StreetO
<CityName>City (e.g., Dublin), town, or postal stationO
<StateProv>State or province code. Examples: NY, QUEO
<PostalCode>Postal code. Examples: 11001, 11001-2345O
<CountryCode>Country Code. Examples: US, FRO
<EmailContact>
O
<Address>

Travel agency’s email address

Example: abc@tc.com

 This is the requesting agent’s email address

M
<OtherIDs>

Specify Non-IATA agent details

O
<OtherID>

Non-IATA agent code

Example: 01010101
M
<IATA_Number>

Travel agent’s IATA number

Example: 12345678

O
<AgencyID>

Travel agency name

Example: ABC

M
<CorporateSender>

Specify corporate details

Populate CorporateSender section only if the request is originated by the Corporate


<ID>

Corporate’s JBID

Example: IN0000FR

Unique ID provided by BA

M
<IATA_Number>

Corporate’s IATA or non-IATA number

Example: 12345678

Do not populate this section if Travel Management Company (TMC) is creating a booking on behalf of the corporate

(info)Note: This is an optional element in NDC schema. Populate this element with the requesting corporate’s IATA or non-IATA number only if the corporate is directly creating booking with BA via NDC Services

O
ElementDetailsOptional/Mandatory
<Participants>

Specify Service Provider details

O
<Participant>
M
<TravelAgencyParticipant>Populate this section only if the participant is a Travel Management Company (TMC) and is creating a booking for the corporate customer i.e., the request is originated by the corporateO
SequenceNumber (Attribute)

Unique number

M
<Contacts>

This is an optional element in NDC schema. Populate this section with the requesting agent’s (TMC’s) email address only if the requesting agent is an IATA agent

O
<Contact>
M
<EmailContact>
O
<Address>

Travel agency’s(TMC’s) email address

Example: abc@tc.com 

This is the requesting agent’s email address
M
<OtherIDs>

Specify Non-IATA agent details

O
<OtherID>

TMC’s Non-IATA agent code

Example: 01010101
M
<IATA_Number>

Travel agent’s (TMC’s) IATA number

Example: 12345678

O
<AgencyID>

Travel agency name

Example: ABC

M
<AggregatorParticipant>

Unique number

O
SequenceNumber (Attribute)

Unique number

M
<Name>

Service Provider name

Example: XYZ

O
<AggregatorID>

Service Provider ID provided by BA

Example: 00123456

All BA NDC services will validate this ID and allow only if the AggregatorID provided is valid

M