.. _Handling-ApiData-and-RedressNumber: *********************************** Handling ApiData and Redress Number *********************************** .. raw:: html

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. .. raw:: html

XML Elements

Here is a sample element of a passenger, containing ApiData and RedressNumber: .. toggle-header:: :header: **Show/Hide Response** .. code-block:: xml 2021-12-01 M TEST 123456789 PT DE TESTER 1970-01-01 M TEST IN1 TESTER MR PX1 ADT US United States US 1234567 | 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. ) Also, although the element "RedressCase" can be present multiple times in NDC, AirBroker currently only supports one RedressNumber per passenger. .. raw:: html

Change RedressNumber

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