Webhook 注册与事件
Atlas API webhook 注册和事件查询参考,用于端点设置、更新和事件对账。
常见问题
何时应注册 webhook URL?
何时应查询事件?
履约流程订单应如何使用 webhook 和事件查询?
本页面涵盖内容
后续步骤
典型流程
在需要时使用此功能
注册范围
相关页面
application/jsonapplication/jsongzip<YOUR_CLIENT_ID><YOUR_CLIENT_SECRET>The URL for receiving webhook notifications
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.
application/jsonapplication/jsongzip<YOUR_CLIENT_ID><YOUR_CLIENT_SECRET>Incident ID
Order number
Incident type:
email.schedulechange: Schedule Change-Email Notificationabnormal.cancelled: Unacounted Cancellationorder.schedulechange: Schedule Change-API Notification
Order's pnr.
Order's passenger names.
Order's passenger Email. Email address passed to the Airline.
Airline IATA code.
A list containing incident stauses
0: Unconfirmed1: Confirmed
Incident Receiving Time Start Format: yyyy-MM-dd HH:mm:ss UTC+08:00
Incident Receiving Time End Format: yyyy-MM-dd HH:mm:ss UTC+08:00
Departure Time Start(Departure local time) Format: yyyy-MM-dd HH:mm:ss
Departure Time End(Departure local time) Format: yyyy-MM-dd HH:mm:ss
Pagination
1Number of records per page
Current pagination
Page size
Total number of records
Last updated
Was this helpful?

