latestOpenAPI 3.0.12026-08-102668257.3 KB

8e9a8f8010ab

Shopping and Ticketing

Seat Availability

Dependency: Verify or getOffer function should be called in prior to this call.

In a booking process, please call the 'seatAvailability' API to get seat availability information after price verification via 'verify' or 'getOffer'. Steps:

  1. API sequence
    • Search - Verify- seatAvailability - Order - Pay
    • getOffer - seatAvailability - Order - Pay
  2. Pass 'offerId' in 'seatAvailability' requests:
    • From 'verify': Use sessionId directly. From 'getOffer': Use its offerId.
  3. In the Order step, use the productCode to add specific seat to the ticket order.

Endpoint: https://sandbox.atriptech.com/seatAvailability.do

post/seatAvailability.do

Headers

Acceptstring required
Content-Typestring required
Accept-Encodingstring required
x-atlas-client-idstring required
x-atlas-client-secretstring required

Request body

sessionIdstring required

ThesessionIdreturned by price verification api(verify.do). Only required in Non-independent mode.

offerIdstring required

TheofferIDreturned by get offer api(getOffers.do). Only required in Non-independent mode.

carrierstring required

The IATA code of MSC(known as Most Significant Carrier) of the itinerary.

Response

status214 | 215 | 216 | 217 | 218 | 219 | 220 | 221 | 223 required
msgstring

It serves as an additional description of the response result. Especially when the interface reports an error (status !=0), it is usually a human-readable error message. Note: Do not use this field in any programming scenarios. For example, do not judge whether the interface responds successfully based on this field. Instead, you should only determine it by checking whether the status is equal to0at any time.