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

座位

Atlas API 座位端点参考,用于查询可用座位、选择座位,并将座位附加服务加入预订。

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

咨询 Eva

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

SeatAvailability 调用规则

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

支持的请求上下文:

  • verify.do 返回的 sessionId

  • getOffers.do 返回的 OfferId

不支持的请求上下文:

  • 仅航班信息

区域处理

全球客户

保持当前流程。

像以前一样使用 sessionIdOfferId

中国 OTA 场景

某些上游座位请求仅包含航班信息。

对于这种情况,保留 verify.do 返回的 sessionId

当座位请求到达时,将航班与缓存的 sessionId 进行匹配。

如果匹配成功,使用该 sessionId 调用 seatAvailability.do

如果不存在匹配,则将其视为纯询价请求。

Atlas 不支持这种情况。

变更原因

此规则确保座位定价和履约与实际预订链保持一致。

同时也减少了无效的航司侧查询。

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

Seat Availability

post

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

Header parameters
AcceptstringRequiredExample: application/json
Content-TypestringRequiredExample: application/json
Accept-EncodingstringRequiredExample: gzip
x-atlas-client-idstringRequiredExample: NAR65434_api_1
x-atlas-client-secretstringRequiredExample: <YOUR_CLIENT_SECRET>
Body
sessionIdstringRequired

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

offerIdstringRequired

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

carrierstringRequired

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

Responses
200Success
application/json
statusinteger · enumRequired
  • 214: Session ID invalid or expired.
  • 215: Segment index missing.
  • 216: Seat selection failed.
  • 217: Unknown error.
  • 218: The airline don’t support seat selection currently.
  • 219: The route don’t support seat selection currently.
  • 220: illegal request parameter.
  • 221: Fare family is empty and not configured with lowest price fare family.
  • 223: The ratio of seat quotation requests to payment orders has exceeded the allowed threshold.
Possible values:
msgstring · nullableOptional

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.

post/seatAvailability.do
200Success

Last updated

Was this helpful?