Handling ApiData and Redress Number

Workflow description

The usage of ApiData and RedressNumber is not limited to one workflow, the data can be transmitted during creation of a booking and all post-booking transactions.

XML Elements

Here is a sample element of a passenger, containing ApiData and RedressNumber:

Show/Hide Response

<Pax>
   <IdentityDoc>
      <ExpiryDate>2021-12-01</ExpiryDate>
      <GenderCode>M</GenderCode>
      <GivenName>TEST</GivenName>
      <IdentityDocID>123456789</IdentityDocID>
      <IdentityDocTypeCode>PT</IdentityDocTypeCode>
      <IssuingCountryCode>DE</IssuingCountryCode>
      <Surname>TESTER</Surname>
   </IdentityDoc>
   <Individual>
      <Birthdate>1970-01-01</Birthdate>
      <GenderCode>M</GenderCode>
      <GivenName>TEST</GivenName>
      <IndividualID>IN1</IndividualID>
      <Surname>TESTER</Surname>
      <TitleName>MR</TitleName>
   </Individual>
   <PaxID>PX1</PaxID>
   <PTC>ADT</PTC>
   <RedressCase>
      <Country>
         <CountryCode>US</CountryCode>
         <CountryName>United States</CountryName>
      </Country>
      <CountryCode>US</CountryCode>
      <RedressCaseID>1234567</RedressCaseID>
   </RedressCase>
</Pax>

Please note, that in the RedressCase-element, both the elements “Country” and “CountryCode” are mandatory in the NDC schemas. However, the element “Country” could also be left empty (e.g. <Country/>)

Also, although the element “RedressCase” can be present multiple times in NDC, AirBroker currently only supports one RedressNumber per passenger.

Change RedressNumber

To change a RedressNumber, the update workflow is simplified, because there is no update inquiry necessary. A sample can be found at Sample: Change RedressNumber