latestOpenAPI 3.0.12026-08-102668257.3 KB
8e9a8f8010ab
Shopping and Ticketing
Retrieve Booking
Dependency: Order function should be called in prior to this call.
Please refer to the below information for the usage of the queryOrderDetails.do API.
- All the parameters can be used together, if required.
- “OrderNo” is “required” if “airlinePNR” and “carrier” cannot be provided upon calling the API. Inversely, “airlinePNR” and “carrier” are “required” if “OrderNo” cannot be provided. All remaining fields in the request are optional.
- The PNR (Passenger Name Record) for an airline ticket order or a luggage purchase order must be kept consistent, as per airline regulations.
- The input parameters orderNo, airlinePNR, carrier, and other optional fields will be validated together to ensure they belong to the same order data source. If any of these input parameters do not match with others, the API will return an error.
- Airline ticket orders and associated post-booking ancillary orders can be retrieved using the following methods: (airline ticket orders + post-booking ancillary orders):
- orderNo
- airlinePNR + carrier
- orderNo + airlinePNR + carrier
- orderNo + airlinePNR + carrier + other optional parameters
- In case the parameters of “airlinePNR” and “carrier” cannot identify an unique order (e.g BC - PNR is made up with 4 number), customer needs to enter additional parameters such as "name" for identification. In such scenarios, API will respond with error msg ”Multi-orderNos are identified, please request again with extra parameters added.”
Endpoint: https://sandbox.atriptech.com/queryOrderDetails.do
post/queryOrderDetails.do
Headers
Acceptstring required
Content-Typestring required
Accept-Encodingstring required
x-atlas-client-idstring required
x-atlas-client-secretstring required