API Workflow#
1.
Data Return Specifications
Only return data for passenger types specified in the request (e.g., if adult fares are requested, do not return child/infant fares).
When the Search interface receives a request with no available content, return an empty data format:
{
"status": 0,
"msg": "success",
"shopsign": [],
"flight": []
}
Price fluctuations are allowed but must be monitored.
Booking relies on the flight and price information returned by the Verify interface.
Required API#
2.
Price Verification（Verify）
4.
Get Pending Ticketing Orders
6.
Cancel or Order Status Push
7.
Flight Reschedule Notification：Notify us in case where there is a flight reschedule/cancellation.
Optional API#
1.
Get Order Details(openIssueOrderInfo）
3.
Query Ancillary Order List
5.
Query Ancillary Order Detail
Function Overview#
Share business direct connection API to access the following core functions:Price Verification (Verify)
Order cancellation (Cancel)
Technical support#
| Support type | Contact information |
|---|
| Technical Consultation | it.flight@oneworldtrip.cn |
| Business Connection | Contact Your Exclusive Business Manager |
Development standards#
Unified Interface Standard#
Unified use of UTF- 8 encoding
Only supports HTTP POST method
The request body must comply with the JSON specification
Use vendor code to identify supplier identity
Enable IP whitelist verification mechanism
Data return rules#
1.
Passenger type consistency: The passenger type returned must strictly match the requested parameters, and it is prohibited to return redundant passenger type data
2.
The error code specification strictly follows the error code types and formats defined in the document
Modified at 2025-10-11 01:52:59
