Sign in
latestOpenAPI 3.0.12026-08-102668257.3 KB

8e9a8f8010ab

Shopping and Ticketing

Get Luggage

In a booking process, please call the 'getLuggage' API to get precise baggage quotes after price verification via 'verify' or 'getOffer'. Steps:

  1. API sequence
    • Search - Verify- getLuggage - Order - Pay
    • getOffer - getLuggage - Order - Pay
  2. For exact baggage prices, request 'getLuggage'.
  3. Pass 'offerId' in 'getLuggage' requests:
    • From 'verify': Use sessionId as offerId
    • From 'getOffer': Use its offerId directly.
  4. 'getLuggage' returns all flight segments' baggage data, each identified by a unique productCode.
  5. In the Order step, use the productCode to add specific baggage products to the ticket order.

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

post/getLuggage.do

Headers

x-atlas-client-idstring required

api access id

x-atlas-client-secretstring required

api access secret

Accept-Encodingstring

建议设置该请求头，能很大程度地减小网络传输报文的大小

Acceptstring required
Content-Typestring required

Request body

offerIdstring required

ThesessionIdreturned by verify api(verify.do)

maxResponseTimeinteger nullable

Query timeout, unit: milliseconds, default 5000ms. <br> Note: Due to network transmission and computational performance impacts, the client may still receive a normal result (rather than a timeout) even if this duration is exceeded. This time is used to control the overall response time of the interface within a certain range, with an error generally not exceeding a few hundred milliseconds.<br> If you have strict requirements for the timeout, it is recommended to set the timeout of your HTTP toolkit. If the HTTP toolkit you are using does not support this capability, you may need to leverage other tools—related capabilities are generally provided in most programming languages.

Response

status212 | 214 | 205 | 299 | 9999 required
  • 212: illegal parameter.
  • 214: offer not exists.
  • 205: timed out.
  • 299: airline error.
  • 9999: system error.
msgstring nullable

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. <br> Note: Do not use this field in any programming scenarios, such as judging whether the interface response is successful based on this field. You should always judge solely based on whether the status is equal to 0.