Working with NDC Exchange

Accessing Production

Sellers will use one of two URL’s in your flow to access NDC Exchange 2.0 API and endpoints. Refer to the table below for each service and associated URL.

Production Service Endpoints

Accessing the Sandbox Environment

Sellers will use one of two URL’s in your flow to access the sandbox for NDC Exchange 2.0 API and endpoints. Refer to the table below to the service and associated URL.

Sandbox Service Endpoints

API Key

To access the NDC Exchange 2.0 Platform API, each seller should provide the “apikey” in the HTTP header. For NDC Exchange 1.0, “X-apiKey” was the value used in the HTTP header; however, for NDC Exchange 2.0 this value is now “apikey”. Please be sure to make this important change or you will experience an Authentication Error (400 Bad Request).

NOTE: OrderCreateRQ requires two additional headers (see below).

The API key is a unique authorization key issued by ATPCO. Currently, API keys for sellers are manually generated by ATPCO.

POST https://gold.services.atpco.net/ndcexchange/agg/ndc/17.2/v1/AirShopping

Request Headers

apikey: XXXXXXXXXXXXXXXXXXXXXX

Content-Type: application/xml

Accept: */*

Host: gold.services.atpco.net

Accept-Encoding: gzip, deflate, br

Connection: keep-alive

In addition to the above, when conducting an OrderCreateRQ, you must submit an additional two mandatory HTTP headers in OrderCreate Request.

First Mandatory HTTP Header:

• Name: TX-Proxy-Key
• Value: XXXXXXXXXXXXXXXXXXXXXXXX (value send to each seller)

Second Mandatory HTTP Header:

• Name: tx-http-timeout:
• Value: 120

TraceID

To enable us to follow up your transactions associated to your requests/responses in the sandbox, we need you to turn on trace and provide the transaction ID.

Ensure you have set orc-debug = “true” to pass in the header.

When retrieving the responses for tech support, you need to capture the value of “HTTP header orc-transaction-id” value and insert in the Transaction ID/Trace field in the ticket.

SOAP Message

Message Structure Example

This is the general structure of any messages accepted by ATPCO NDC Exchange 2.0 (Aggregation Service).

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:atpco="https://prod.services.atpco.net/ndcexchange/NDC/schema/v1">
    <soapenv:Header/>
    <soapenv:Body>
        <atpco:NDCMSG_Envelope>
            <NDCMSG_Header>
                <Sender>
                    <SellerID>atpco.ndcx.key.SELLER-SPECIFIC-KEY</SellerID>
                </Sender>
                <Recipient>
                    <Address>
                        <Company>YY</Company><!--This is the airline code for which the message is intended.-->
                    </Address>
                </Recipient>
                <SchemaType>NDC</SchemaType>
                <SchemaVersion>YY.2017.2</SchemaVersion>
            </NDCMSG_Header>
            <NDCMSG_Body>
                <NDCMSG_Payload>
                    <![CDATA[
                    
<IATA_NDC_Message>
[...]
</IATA_NDC_Message>

					]]>
				</NDCMSG_Payload>
			</NDCMSG_Body>
		</atpco:NDCMSG_Envelope>
	</soapenv:Body>
</soapenv:Envelope>

IATA NDC Message

Message Structure Example

This is the general structure for supported IATA 17.2 messages.

<IATA_NDC_Message Version="2017.2" EchoToken="ET" TimeStamp="2021-04-08T10:18:42.087-04:00" TransactionIdentifier="1" SequenceNmbr="1" xmlns="http://www.iata.org/IATA/EDIST/2017.2">
	<PointOfSale>
		<Location>
			<CountryCode>US</CountryCode>
		</Location>
	</PointOfSale>
	<Document>
		<Name>ATPCO AGG NDCx 2.0</Name>
		<ReferenceVersion>IATA NDC 17.2</ReferenceVersion>
	</Document>
	<Party>
		<Sender>
			<TravelAgencySender>
				<PseudoCity>XXX</PseudoCity>
				<IATA_Number>0000XXXX</IATA_Number>
				<AgencyID>XXX</AgencyID>
			</TravelAgencySender>
		</Sender>
	</Party>
	<Parameters>
		<Languages>
			<LanguageCode>en-CA</LanguageCode>
		</Languages>
		<CurrCodes>
			<FiledInCurrency>
				<CurrCode>USD</CurrCode>
			</FiledInCurrency>
		</CurrCodes>
	</Parameters>

[...]

</IATA_NDC_Message>