Overview

NDC (New Distribution Capability) is a data exchange format based on Offer and Order management processes for airlines to create and distribute relevant offers to the customer.

The NDC Gateway API is the single point of access to route all the traffic to a third party vendor (Navitaire) implementing the features defined in the standard.

Enrollment Process

The NDC Gateway API is protected both by the use of API Keys to identify the API consumer app and through JWT tokens that verify your New Skies agent. On top, our production environment is protected by an IP whitelist.

API Key

You may request your API Key from within TUI's developer portal at https://developer.tui/. If you haven't done so already, you must first register as a developer identifying flight-ndc-gateway-navitaire as the "API Product" and the email address api.flightproduction@tui.com as the "Partner Manager Email" (see more). Once the registration is approved, you may create and manage your Apps directly to access to the NDC Gateway API. Please be precise when naming your App, including a clear reference to identify yourself in the prefix (e.g. travelparadise.fr-packagesearch-app) as it will be required to complete the approval process and obtain the API Key. A valid API Key will be required on all requests performed to the NDC Gateway API.

JWT Tokens

When initiating a new working session, you will be required to create a new JWT Token that will be used throughout the rest of the API calls in the session. To obtain these tokens, you will need to logon using the New Skies Agent credentials to start a session. If you have lost your New Skies Agent credentials, need a password reset or need a new agent, please reach out to us at api.flightproduction@tui.com with your request.

IP Whitelist

Access to the NDC Gateway production environment is restricted via an IP address filter. After you have submitted your workflow validation form, if approved, your production IP addresses will be added to our whitelist, granting you access to the API.

Also, please take in account that accessing the NDC Gateway API production environment from any non-production environment is forbidden.

Testing Environment

To assist with the integration with the NDC Gateway, you may use our playground (non-production) environment by using its specific URL (see here). Same as the production environment, the playground environment requires both the API Key and JWT Token authorization methods.

However, while you may reuse the same API key created for the production environment, the credentials needed for the JWT tokens are independent from the ones from the production environment. To request New Skies agent credentials for the non-prod environment, please send an email to api.flightproduction@tui.com, with the following details:

Subject: New Skies Agent Request (non-prod)

Message Content: It should contain your application name and the contact address to send the credentials to.

IP whitelisting is not needed for the non-production environments.

Please remember that performing tests pointing to our production API is strictly prohibited!

Workflow Validation

Access to the production environment requires a workflow validation prior to go-live. You will need to provide the following details:

• Contact details (general email address of your company)
• App name used on the developer portal for registration
• Production environment IP addresses or ranges
• Other environment IP addresses or ranges (e.g. your test/development environment)
• Brief description of your use case
• Endpoints used by your workflow, including a short description of the purpose of each request
• Overall workflow diagram
• Expected throughputs (requests per minute)

We encourage you to define and test your use cases using the playground environment first, so you can share the details needed to facilitate the validation and approval process.

Additionally, you will be provided with a test spreadsheet containing a set of test cases that must be executed against the playground environment. The completed results must be attached to your validation request so we can verify that your integration works correctly.

Please be aware that missing information may delay the whitelisting and go-live.