For the complete documentation index, see llms.txt. This page is also available as Markdown.

行李

Atlas API 行李端点参考,用于查询行李选项、获取行李报价,并在预订中添加行李服务。

💬 需要帮助? 如果遇到问题,请在帮助中心咨询 Eva,快速获取诊断建议。

咨询 Eva

使用此端点进行流入行李查询。

GetLuggage 调用规则

在有效的预订链中使用 getLuggage.do

支持的请求上下文:

  • verify.do 返回的 sessionId,作为 offerId 发送

  • getOffers.do 返回的 OfferId

如何处理响应

getLuggage.do 返回当前行程的行李产品。

每个产品都有一个 productCode

在选择行李时,将该 productCode 用于 order.do

注意事项

  • 在目标行程确认后查询行李

  • 保持当前预订上下文的行李映射一致

  • 对于联程航班,保持同一方向连接航段的行李选择一致

有关共享规则和计数详情,请使用 API 请求限制

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

Last updated

Was this helpful?