The "City pairs API" can be used to download the city pairs supported by Atlas as well as by the airlines. The customer can use this structured data and transfer the city pair information into their mid-back office systems.
This API is only available in the production environment.
Order number.
At least one of the order number, receiving time and/or creation time must be specified for querying.
emailReceivingDateStartstring | nullableOptional
Start of the receiving time.
The time Atlas received the airline's email.
Format: yyyy-MM-dd hh:mm:ss UTC+08:00
emailReceivingDateEndstring | nullableOptional
End of the receiving time.
The time Atlas received the airline's email.
Format: yyyy-mm-dd hh:mm:ss UTC+08:00.
You can only query data for up to one month at a time
createTimeStartstring | nullableOptional
Start of creation time.
Create Time is the time when Atlas created this email record in the Email list. Generally, it will be later than the receiving time.
Format: yyyy-mm-dd hh:mm:ss UTC+08:00
createTimeEndstring | nullableOptional
End of creation time.
Create Time is the time when Atlas created this email record in the Email list. Generally, it will be later than the receiving time.
Format: yyyy-MM-dd hh:mm:ss UTC+08:00
You can only query data for up to one month at a time.
emailCategoriesstring | nullableOptional
Atlas email categories. Atlas categorizes emails but does not guarantee accuracy in classification.
-Travel Itinerary
-Schedule Change
-Payment Due
-Payment Success
-Receipt
-Trip Reminder
-PNR Cancellation Success
-Advertisement
-Duplicated Schedule Change
-Verification
-Unaccounted Cancellation
-Promo code
pageIndexstring | nullableOptionalDefault: 1
pageSizestring | nullableOptionalDefault: 100
Responses
200Success
application/json
post
/queryMail.do
200Success
Extract PNR
post
This API is used to directly connect to airlines and extract PNR information. The content displayed by this API reflects the current PNR information on the airline side, such as flight schedule and ticket status. Atlas extracts airline information truthfully and will not do any modification.
Order number. It can be an order for ticketing, or an order for add bags. The format of each kind of order is different.
userNamestringRequired
This is to identifier the operator's name in client's system, Atlas will grant access to this operator and track his/her actions in Atlas customer service portal.
rolestringRequired
This is to identify the operator's role. Atlas will grant access to this operator according to the role assigned. Here are the acceptable options:
Customer service : Access to manage orders and request post ticketing services
Finance : Access to manage the balance and check statements
Developer : Access to manage the system configurations
POST /regenerateOrder.do HTTP/1.1
Host:
Accept: text
Content-Type: application/json
Accept-Encoding: text
x-atlas-client-id: text
x-atlas-client-secret: text
Content-Length: 44
{
"originalOrderNo": "AAYDY20250816162229555"
}
POST /stopTicket.do HTTP/1.1
Host:
Accept: text
Content-Type: application/json
Accept-Encoding: text
x-atlas-client-id: text
x-atlas-client-secret: text
Content-Length: 36
{
"orderNo": "ZNMKU20220119160129691"
}
{
"status": 0,
"msg": "We are trying to intercept the ticket issuance. Please check the order status for result after 8 minutes"
}
POST /balance.do HTTP/1.1
Host:
Accept: text
Content-Type: application/json
Accept-Encoding: text
x-atlas-client-id: text
x-atlas-client-secret: text
Content-Length: 19
{
"currency": "text"
}
