Accessing the NDC.ONE APIs

URL construction

The domain “ndc.one” acts as central entry point for all accessible airlines.

The APIs are available through the subdomain “api.ndc.one”.

The client only needs to specify the base path, the carrier and the API version that should be used:

https://{carrier_code}.{environment}.ndc.one/{carrier_code}/{ndc_version}/{operation_path}

Environment:

Every API has an access point for the productive environment as well as for the integration/test environment. The client can select the environment by setting the parameters accordingly:

LIVE: api.ndc.one

TEST: api-test.ndc.one

Carrier code:

To select a carrier, the client must add the official IATA carrier code to the path (see Airline Information). To give an example: For a carrier with IATA code “ZZ” the URL for the live environment would be:

https://zz.api.ndc.one/zz/

NDC version:

Following the carrier code, the API version must be added to the path:

https://zz.api.ndc.one/zz/19_2to/

Operation path:

The last part of the full URL is the operation path, which varies depending on the message the client wants to send (see NDC Message Endpoints below).

Full Example:

https://zz.api.ndc.one/zz/19_2to/order/delivery

Technical Aspects

NDC.one accepts XML-messages using HTTP-communication. HTTP-method and operation paths are listed in the table below.

Base-Authentication

For all transactions, the HTTP-header “Authorization” is required. The value must contain the Base64-encoded user credentials that were provided to the client.:

Username: “ndc”

Password: “nDc123!”

Base64 Encoded (username:password): “bmRjOm5EYzEyMyE=”

Authorization Header: “Basic bmRjOm5EYzEyMyE=”

Content-Encoding

All NDC server instances support GZIP-compressed communication. It is strongly recommended to add the header “Content-Encoding” with the value set to “gzip”.

Content-Type

“Content-Type” for all messages must be set to “application/xml”.

NDC Message Endpoints

Operation	HTTP Path	HTTP Method	Request	Response	Explained in detail
Seatmap	/shopping/seatmap	POST	IATA_SeatAvailabilityRQ	IATA_SeatAvailabilityRS	IATA_SeatAvailabilityRQ/RS
ServiceList	/shopping/serviceList	POST	IATA_ServiceListRQ	IATA_ServiceListRS	IATA_ServiceListRQ/RS
Booking Delivery	/order/delivery	POST	IATA_ServiceDeliveryNotifRQ	IATA_Acknowledgement	IATA_ServiceDeliveryNotifRQ IATA_Acknowledgement
Retrieve Order	/order/retrieve	POST	IATA_OrderRetrieveRQ	IATA_OrderViewRS	IATA_OrderRetrieveRQ
Search Orders	/order/list	POST	IATA_OrderListRQ	IATA_OrderListRS	IATA_OrderListRQ/RS
Cancel Order	/order/cancel	DELETE	IATA_OrderCancelRQ	IATA_OrderCancelRS	IATA_OrderCancelRQ/RS
NDC Schema	/xsd.zip	GET	N/A	N/A	Can be used to retrieve the currently supported xsd-Files defined by IATA.