Ctrlk
💬 Need Help? Click Me
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Baggage

Atlas API getLuggage.do reference for retrieving baggage products and productCode values for order creation.

💬 Need help? If you're stuck, ask Eva in the Help Center for instant diagnostics.

Ask Eva

Use this endpoint for inflow baggage lookup.

getLuggage.do shares one 60 QPM ancillary pool with seatAvailability.do.

Over-limit requests return HTTP 429 Too Many Requests.

Wait for the returned retryAfter value before retrying.

GetLuggage call rules

Use getLuggage.do inside a valid booking chain.

Supported request context:

  • sessionId returned by verify.do, sent as offerId

  • OfferId returned by getOffers.do

What to do with the response

getLuggage.do returns baggage products for the current itinerary.

Each product has a productCode.

Use that productCode in order.do when baggage is selected.

Notes

  • query baggage after the target itinerary is confirmed

  • keep baggage mapping consistent for the current booking context

  • for connecting flights, keep baggage selection consistent across connected segments in the same direction

Use API Request Limits for shared rules and counting details.

Get Luggage

post

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

Header parameters
x-atlas-client-idstringRequired

api access id

Example: NAR65434_api_1
x-atlas-client-secretstringRequired

api access secret

Example: changeit
Accept-EncodingstringOptional

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

Example: gzip
AcceptstringRequiredExample: application/json
Content-TypestringRequiredExample: application/json
Body
offerIdstringRequired

ThesessionIdreturned by verify api(verify.do)

Example: 85540632-ef14-4cb2-900e-453ef0a19477
maxResponseTimeinteger · nullableOptional

Query timeout, unit: milliseconds, default 5000ms.
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.
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.

Default: 5000
Responses
200Success
application/json
statusinteger · enumRequired
  • 212: illegal parameter.
  • 214: offer not exists.
  • 205: timed out.
  • 299: airline error.
  • 9999: system error.
Possible values:
msgstring · nullableOptional

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, 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.

post/getLuggage.do
200Success
PreviousSeatNextCreate Order

Last updated

Was this helpful?