Other Functions
application/jsonapplication/jsongzip<YOUR_CLIENT_ID><YOUR_CLIENT_SECRET>The order number of the original ticket order you want to regenerate
ACFIO20231207174449854- 301: Session does not exist or timed out. Description: The "sessionID" has a validity of 2 hrs. If the “sessionID” is used after this time period, then this error is displayed
- 302: The target flight is no longer available. Description: In the period between verify and book, the flight has been sold out. This can also be due to the number of passengers booked. The number of pax when booking and the number of pax when verifying may be different. When create a booking, the price is verified based on the actual number of pax booked
- 303: Airline closed. Description: Airline has either ceased to exist or not operational.
- 304: Verify failed. Description: In some uncontrollable situations, such as network issues, upgrades, and restarts, 304 error may occur, but not many. If there are many 304 errors, it is possible that the airline is not available or some technical issue at Atlas' end. Contact your account manager if this error keeps on repeating.
- 305: Invalid routing. Description: When generating an order, the system found that the flight was no longer sold for various reasons, such as 1) L2B 2) The system has identified that there may be a risk of the flight being sold out 3) The airline's sales have been closed
- 307: Illegal booking request parameters. Description: Some request parameters have problem. Please check the message.
- 308: Price changed. Description: The price has changed between the price verification and order. Please verify the price again and generate the order.
- 309: Ancillary not found. Description: Incorrect ancillary product code has been entered. Check and enter the correct ancillary product code.
- 310: Infant not allowed. Description: The offer does not support infant. Create a new booking without infant passenger type.
- 312: Too many seats booked. Description: The number of pax booked exceeds the remaining (or allowed) seats on the current flight.
- 313: Fare family sold out. Description: Selected offer is no longer available. Conduct the search again and rebook.
- 315: Not enough seats. Description: Seats have been sold out
- 316: Timed out. Description: There is a time-out error at the airline’s end
- 317: Booking unsuccessful with Airline. Description: An error has happened at the airline’s end.
- 318: Check if a booking with the same passenger details and flight numbers exists. After confirming, ignore this booking.
- 319: Flight information has changed. Description: Re-verify the price (query the latest flight information) and generate the order.
- 320: The requested seats were not found or they are already occupied. Description: Rebook seats and submit a new order.
- 321:
- 322: Seat price changed. Description: Seat price changed. Re-query the seat map and select seats
- 323: The format of the e-mail in the contact information is incorrect
- 324: Airline system issues. Description: Retry after some time. If the issue persists, please contact our operations team.
- 325: The airline has deemed the passenger unserviceable
- 326: Your account balance on the airline side is insufficient(BYOA scenario)
- 327: Passenger information does not meet the requirements. Description: Check and correct the passenger information according to the error message
- 328: Selected seat is no longer available. Description: The selected seat has been occupied.
- 329: No payment method is available. Description: No payment method is available. Please check whether the quotation currency or account configuration is correct.
- 330: operation is in progress. Description: operation is in progress
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.
Order number of the created order.
The pnrCode is the single reference for the booking. This is the Atlas PNR, not airline's.
Total price(not including service fee) of this order in the currency TheAtlas settled with you
Total technical fees for this order in the currency TheAtlas settled with you.
The currency TheAtlas settled with you.
Total price of this order in the vendor's currency, reference for you to generate the specific credit card.
Vendor's currency.
Payment deadline for this order. This time will be displayed in SGT (GMT +8). The fromat is:yyyy-MM-dd HH:mm:ss.
If the api returns error code318(duplicate booking), then the list will contain duplicate order numbers.
application/jsonapplication/jsongzip<YOUR_CLIENT_ID><YOUR_CLIENT_SECRET>The order number of the ticket order you want to stop ticket issuance.
-0: success
-other: fail
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>A series of conditions for matching orders
Atlas order number. Accurate matching
TESTA20241122090710695The airline PNR(not Atlas's). If the airline pnr of the order contains any of the given values, it will be returned.
The name of the passenger(last name/first name). If the passenger in the order includes the given value, it will be returned.
Accurate matching，match based on the contact email provided by the customer
IATA code of the departure city
IATA code of the arrival city
Date of departure. The format is:yyyyMMdd
The start time of order creation. This is in UTC. The format is:yyyy-MM-dd'T'HH:mm:ss'Z'.
The end time of order creation. This is in UTC. The format isyyyy-MM-dd'T'HH:mm:ss'Z'
If the airlines of the order contains any of the given values, it will be returned
Start from: 1
1Number of records to be displayed on each page.
20It 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>Atlas order number
application/jsonapplication/jsongzip<YOUR_CLIENT_ID><YOUR_CLIENT_SECRET>The currency of your balance account
application/jsonapplication/jsongzip<YOUR_CLIENT_ID><YOUR_CLIENT_SECRET>-1: Airline routes
-2: Atlas routes
IATA Code of departure city.
IATA Code of departure country.
IATA Code of arrival city or airport
IATA Code of arrival country.
An array of IATA Codes of airlines. The routes within the airlines will be returned.
100001application/jsonapplication/jsongzip<YOUR_CLIENT_ID><YOUR_CLIENT_SECRET>Order number. At least one of the order number, receiving time and/or creation time must be specified for querying.
Start of the receiving time. The time Atlas received the airline's email. Format: yyyy-MM-dd hh:mm:ss UTC+08:00
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
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
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.
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
1100-true: There is also the next page
-false: There is not the next page
application/jsonapplication/jsongzipExample: gzip<YOUR_CLIENT_ID>Example: <YOUR_CLIENT_ID><YOUR_CLIENT_SECRET>Example: <YOUR_CLIENT_SECRET>The airline PNR
2-letter IATA code for the airline
The maximum response duration, in milliseconds. Note: This time is estimated due to the impact of network transmission.
15000Airline PNR(not Atlas)
BSG768TicketedPossible values: pnr usage status
The currency of fare
USDapplication/jsonapplication/jsongzipExample: gzip<YOUR_CLIENT_ID>Example: <YOUR_CLIENT_ID><YOUR_CLIENT_SECRET>Example: <YOUR_CLIENT_SECRET>Order number. It can be an order for ticketing, or an order for add bags. The format of each kind of order is different.
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.
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
Admin : Full access
A url with token to access to Atlas customer service portal.
0: success
2: System error
3: unauthorized access
Error message.
The 'msg' element is for description of the results. Please DO NOT use this field to check the success or failure of the request. Only use the 'status' code to check the result.
Last updated
Was this helpful?