Shopping and Ticketing
application/jsonapplication/jsongzip<YOUR_CLIENT_ID><YOUR_CLIENT_SECRET>The trip type(one way or round trip) you want to search.
- 1: Oneway
- 2: Return Trip
1Possible values: Adult passenger count. Please note that the total number of adults(adultNum) and children(childNum) cannot exceed 9.
0Example: 1Child passenger count. Please note that the total number of adults(adultNum) and children(childNum) cannot exceed 9
0Example: 0Infant passenger count, no more than the number of adult
0Example: 0IATA code of the departure city or airport (in capital letters).When the airport code you sent is different from the code of the city where the airport is located, we can recognize that it is an airport, otherwise we will treat it as a city code. We will filter flights based on your departure location type.
LONIATA code of the arrival city or airport (in capital letters).When the airport code you sent is different from the code of the city where the airport is located, we can recognize that it is an airport, otherwise we will treat it as a city code. We will filter flights based on your departure location type.
PARDeparture date, the format is YYYYMMDD
20251010Return date, the format is YYYYMMDD. If you are searching for round-trip, the return date is mandatory.
An array of IATA Codes(in capital letters) of airlines. The result will only contain the airlines specified in the search request.
U2Search for specified departure flights. Each element represents one flight. Connecting flight numbers are separated by "," (comma).
Example:
- ["FR123"]: A direct flight
- ["FR456,FR789"]: A connecting flight
- ["FR123", "FR456,FR789"]: 2 flights, a direct flight and a connecting flight
Search for specified return flights. Each element represents one flight. Connecting flight numbers are separated by "," (comma).
Search only for the lowest fare or for the Fare Families. By default, each flight only returns the lowest fare, and each array element in the response represents: flight - lowest fare. If this parameter is turned on, each element of the search results will be a combination of flight and one of the fares, that is, different elements will have the same flight but different ticket fare.
falseThis is the settlement currency. The 3-letter currency code should be entered. This field is optional, and when you want to settle with Atlas in different currencies (especially when you have opened multiple deposit accounts in different currencies in Atlas), you need to use this parameter.
Identify the source of the search traffic, E.g. Google Flights, Oganic Search, SkyScanner.
Resident discount code
- 100: Missing required request data. Description: You should pass the necessary parameters in the HTTP request body.
- 101: Illegal request data. Description: Check the format of request
- 102: Illegal request param. Description: Some parameters do not meet the requirements. Please adjust them according to the error message.
- 105: OD is not in client's round-trip white list. Description: This city pair has not been whitelisted. Check with your account manager if there is a restriction to your account.
- 106: You are not allowed to search. Description: Check with your account manager if there is a restriction to your account.
- 107: Insufficient balance. Description: The account balance is below the agreed threshold. Top-up your account on a priority.
- 108: Route is restricted / System limitations. Description: The airline has flights and quotations, but Atlas has closed sales for some reasons. The reasons can be 1) The sales were manually closed 2) The system has detected a risk of sold out 3) Prohibitions on nearby flights.
- 109: The number of searches exceeded the limit. Description: The searches per day have exceeded the allowed limit. Check with your account manager if there is a restriction to your account.
- 110: Too many concurrent requests.. Description: The QPS (Queries Per Second) is higher than the allowed limit. If your business requires more resources, please contact your account manager.
- 111: Real time search is not allowed. Description: This feature is not activated for your account. Connect with your account manager if you require this service.
- 112: Timed out. Description: The search request has timed-out. For further details please refer to FAQs --> Atlas API General Information.
- 113: Airline is under maintenance. Description: Airline is in "Inactive" or "Maintenance" status with Atlas. This does not necessarily mean that there is an issue with the Airline website itself. Wait for the status to change to “active”.
- 114: No flights present. Description: This may happen when: - The airline does not fly on that date for the searched city pair. Check the airline website to see if the flight is operational for that date.
- 116: Search data not captured. Description: An error was reported during the search data stoprage at Atlas' end. If this error is not constantly reported, you can try trying again. If the error persists, then it is necessary to contact the account manager.
- 123: Too many requests but too few paid orders. Description: The service has been blocked as the search requests are too many and the paid orders are very less.
- 124: Unsupported settlement currency. Description: The settlement currency is different than what is accepted by Atlas. Change the currency to the currency accepted by Atlas for settlement.
- 126:
requestIddoes not exist or request is already ended. Description: - 900: Unauthorized access. Description: Incorrect credentials Or the account status is incorrect Or try to access other customer's data. Check credentials. If the error still persists, contact your account manager.
- 9999: Inner error. Description: There is a problem or a bug in the system. Contact your account manager.
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>TheroutingIdentifierfrom search response.
The interface timeout(in milliseconds), with a default of 5000ms. Note: Due to the influence of network transmission and computational performance, the client may still receive a normal result (instead of a timeout) when the response duration exceeds. This time is used to control the overall response duration of the interface within a certain range, and the error generally will not exceed several hundred milliseconds. If you have strict requirements for the timeout time, it is recommended that you set the timeout time of your HTTP tool library. If the HTTP tool library you use does not support this capability, you may need to use other tools to achieve it, and most programming languages provide relevant capabilities.
15000The tag to identify which channel does this traffic come from. For example: SkyScanner,Google,Oganic search,etc…
- 200: Illegal routing identifier. Description: The "routingIdentifier" in request contains invalid content. Please check the content of this field to ensure that the content returned by the search is passed back exactly as it is.
- 201: Invalid routing. Description: The airline has flights and quotations, but Atlas has closed sales for some reasons. The reasons can be 1) The sales were manually closed 2) The system has detected a risk of sold out 3) Prohibitions on nearby flights. Try booking after some time.
- 202: Routing identifier expired. Description: The routingIdentifier has a certain validity period. If the “routingIdentifier” is used after this time period, then this error is displayed. Conduct “Search” again and use the new “routingIdentifier”.
- 203: Airline closed. Description: The airline is no longer in business.
- 205: Timed out. Description:
- 207: Flight not available. Description: The required flight is no longer available at the airline's side, possibly due to the flight being sold out.
- 210: Fare family sold out. Description: The flight or the fare family is no longer available with the airline. Conduct the search again and rebook.
- 212: Illegal Request Parameter. Description: Some parameters do not meet the requirements. Please adjust them according to the error message.
- 213: Flight information changed. Description: Conduct the search again and rebook.
- 222: Fail to obtain baggage from airline. Description: Fail to obtain baggage from airline, pls retry the request.
- 299: Verify failed. Description: This is an error for which Atlas needs to take action. In some uncontrollable situations, such as network issues, upgrades, and restarts, 299 errors may occur. It is possible that the airline is not available or there are challenges at Atlas' end. Atlas needs to handle these errors internally.
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.
The unique identifier for this verification. It is required when you call order function to make a reservation to identify which flight and fare the client is choosing.
Max seats allowed when booking. Please refer this element and prevent the end-users to choose more passengers than seat count.
application/jsonapplication/jsongzip<YOUR_CLIENT_ID><YOUR_CLIENT_SECRET>sessionIdreturned by verify response. If you got offer by verify api, then this parameter is required.
offerIDreturned by get offer response. If you got offer by "get offer" api, then this parameter is required.
The tag denoting whether to use Atlas email id for contact information.
true: Use Atlas email as contact email.false: It is determined according to the strategy agreed upon with the customer or the default strategy of the system.
Please refer to the terms and conditions for usage of Atlas email.
falseThe tag to identify which channel does this traffic come from. For example: SkyScanner,Google,Oganic search,etc…
Configuration of ordering when the seat is occupied.
- SIMILAR_SEAT: Select a similar seat automatically
- STOP_SEAT: Stop seat and continue ticketing
- STOP_TICKET: Stop ticketing and cancel the order
The country and language environment preferences of the ticket purchaser/contact person. This information may be useful for certain airlines. For example, airlines will use this information to communicate with users in appropriate languages (e.g., via emails). We have prepared the language environments supported by each airline for your reference: Locale
- 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
- 407: Some mandatory element for the passenger has not been submitted.. Description: Check the information and correct the same and resubmit.
- 408: Passenger can not board alone. Description: Create a new order and add an adult passenger with the child passenger
- 409: Additional baggage does not match the flight segment. Description: Luggage purchased for each segment of a connecting flight must be the same.
- 410: The contact information is not in the correct format.. Description: Check the contact information and confirm that it matches the required format.
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.
Echo thesessionIdin the request parameters.
Echo theofferIdin the request parameters.
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/jsongzipExample: gzip<YOUR_CLIENT_ID>Example: <YOUR_CLIENT_ID><YOUR_CLIENT_SECRET>Example: <YOUR_CLIENT_SECRET>Order number
The redirect localtion to which when users confirm an order on the
FR's confirmation page. If you choose to display the confirmation page in Popup mode, please specify this.
If you want to display the FR's order confirmation page in iframe mode, please specify iframe=true, and in this case, the redirectUri will be ignored.
Maximum response time of the API in milliseconds.
8000- 307: illegal booking request param
- 800: order not exists
- 316: timed out
- 317: airline error
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.
The FR order confirmation page link.
application/jsonapplication/jsongzipNAR65434_api_1<YOUR_CLIENT_SECRET>Order number you want to do the payment.
The payment method you want to use
- 1: balance
- 3: vcc passthough
- 4: BYOA
- 5: MoR
Order number at the customer side.
The tag to identify which channel does this traffic come from. For example: SkyScanner,Google,Oganic search,etc…
- 400: Illegal request param. Description: Check and correct the request parameters according to the error message.
- 401: Later than the payment deadline. Description: Payment for the booking was initiated later than the payment deadline.
- 402: Order status does not support payment. Description: The order status maybe “ticketing” or “ticketed” where the payment has already been made. Check if the order status is unpaid
- 403: Unsupported payment method. Description: The payment method is not supported for this order.
- 404: The order is already paid. Description: Check if the order has been paid. If “yes”, do not send the payment request
- 406: Payment operation is in progress. Description: The previous payment request is still in process. Wait for the airline PNR to be received in the PNR details response.
- 407: Some mandatory element for the passenger has not been submitted.. Description: Check the information and correct the same and resubmit.
- 408: Passenger can not board alone. Description: Create a new order and add an adult passenger with the child passenger
- 409: Additional baggage does not match the flight segment. Description: Luggage purchased for each segment of a connecting flight must be the same.
- 410: The contact information is not in the correct format.. Description: Check the contact information and confirm that it matches the required format.
- 411: Some error happened with the payment gateway. Description: Some error happened with the payment gateway
- 412: No available payment methods. Description: No available payment methods for this order
- 413: Card is not supported. Description: For MoR, the brand of the card sent by customer is not supported by Atlas.
- 414: Card mismatch. Description: The brand of the card sent during payment is inconsistent with the "cardType" sent when generating the order.
- 415: order is not confirmed by user. Description: order is not confirmed by user
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.
Echo the order number
Payment method
application/jsonapplication/jsongzipNAR65434_api_1<YOUR_CLIENT_SECRET>Order number of the order you want to retrieve
The pnrCode is the single reference for the booking. This is the Atlas PNR.
- 800: Order not exists
- 701: Multi-order are identified, please request again with extra parameters added
- 702: airlinePNR and carrier are mandatory to fill in for order retrieval, please check and request again
- 703: No order found, please check the parameter
- 704: Parameters don't match, please check and retry
- 705: Timeout
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
The pnrCode is the single reference for the booking. This is the Atlas PNR.
Order status
-0: Unpaid
-1: Ticketing-in-Process
-2: Ticketed
--3: Cancelled
Ticket status
-0: Ticket not issued
-1: Ticket issued
Total price(not include the technical service fee) of this order in the currency TheAtlas settled with you.
The currency TheAtlas settled with you.
Payment deadline for this order. This time will be displayed in SGT (GMT +8). The format is:yyyy-MM-dd HH:mm:ss
Total price of this order in the vendor's currency, reference for you to generate the specific credit card. If the order does not support VCC passthrough or BYOA, this fare will not be displayed.
The actual price charged by the airline, which is denominated in the airline's currency(vendorCurrency). We will only display the actual amount charged by the airline if the order supports VCC passthrough or BYOA, otherwise, this field will benull.
Total ancillary price of this order in the vendor's currency. If the order does not support VCC passthrough or BYOA, this fare will not be displayed.
Vendor's currency.
Total adult price of this order in the currency TheAtlas settled with you.
Total child price of this order in the currency TheAtlas settled with you.
Total infant price of this order in the currency TheAtlas settled with you.
Total ancillary price of this order in the currency TheAtlas settled with you.
Total technical fees for this order in the currency TheAtlas settled with you.
This tag shows which payment method is supported for that particular booking.
-1: Prepayment Only
-3: Both Credit Card Payment and Prepayment Available
This field has been deprecated, pls usesupportPaymentMethods instead.
This is the mode of payment used to pay for the booking. If the order is not paid, this field will benull.
The link to download the itinerary of the trip.
An error code used to indicate the specific reason for ticket issuance failure. Note that this error code will only be displayed when the order is canceled due to ticket issuance failure.
A brief message used to explain theerrorCode.
A piece of error message on the airline side that is used to explain theerrorCode.
Configuration of ordering when the seat is occupied.
Only used for VCC transparent transmission, indicating whether Atlas has initiated payment operations with the airline using your VCC. true/false/null (meaningless).
-true: Atlas has previously initiated a payment operation with the airline.
-false: Atlas has not initiated a payment operation with the airline.
-null: meaningless
Note:
true only indicates that Atlas has previously initiated a payment operation with the airline, and does not represent the payment result (successful or failed)
application/jsonapplication/jsongzip<YOUR_CLIENT_ID><YOUR_CLIENT_SECRET>Only required in Subsequent Request
The trip type(1=one way or 2=round trip) you want to search
1Possible values: Adult passenger count. Please note that the total number of adults(adultNum) and children(childNum) cannot exceed 9.
0Example: 1Child passenger count. Please note that the total number of adults(adultNum) and children(childNum) cannot exceed 9
0Example: 0Infant passenger count, no more than the number of adult
0Example: 0IATA code of the departure city or airport (in capital letters).When the airport code you sent is different from the code of the city where the airport is located, we can recognize that it is an airport, otherwise we will treat it as a city code. We will filter flights based on your departure location type.
LONIATA code of the arrival city or airport (in capital letters).When the airport code you sent is different from the code of the city where the airport is located, we can recognize that it is an airport, otherwise we will treat it as a city code. We will filter flights based on your departure location type.
PARIATA code of the departure airport
AAAIATA code of the arrival airport
AAADeparture date, the format is YYYYMMDD
20251010Return date, the format is YYYYMMDD. If you are searching for round-trip, the return date is mandatory.
An array of IATA Codes(in capital letters) of airlines. The result will only contain the airlines specified in the search request.
Search for specified departure flights. Each element represents one flight. Connecting flight numbers are separated by "," (comma).
Example:
- ["FR123"]: A direct flight
- ["FR456,FR789"]: A connecting flight
- ["FR123", "FR456,FR789"]: 2 flights, a direct flight and a connecting flight
Search for specified return flights. Each element represents one flight. Connecting flight numbers are separated by "," (comma).
Search only for the lowest fare or for the Fare Families. By default, each flight only returns the lowest fare, and each array element in the response represents: flight - lowest fare. If this parameter is turned on, each element of the search results will be a combination of flight and one of the fares, that is, different elements will have the same flight but different ticket fare.
falseThis is the settlement currency. The 3-letter currency code should be entered. This field is optional, and when you want to settle with Atlas in different currencies (especially when you have opened multiple deposit accounts in different currencies in Atlas), you need to use this parameter.
The currency for the display fares in response. If no display currency is specified, the display amount will be null.
Identify the source of the search traffic, E.g. Google Flights, Oganic Search, SkyScanner.
Is smart search synchronized return, default is asynchronous
Resident discount code
- 100: Missing required request data. Description: You should pass the necessary parameters in the HTTP request body.
- 101: Illegal request data. Description: Check the format of request
- 102: Illegal request param. Description: Some parameters do not meet the requirements. Please adjust them according to the error message.
- 105: OD is not in client's round-trip white list. Description: This city pair has not been whitelisted. Check with your account manager if there is a restriction to your account.
- 106: You are not allowed to search. Description: Check with your account manager if there is a restriction to your account.
- 107: Insufficient balance. Description: The account balance is below the agreed threshold. Top-up your account on a priority.
- 108: Route is restricted / System limitations. Description: The airline has flights and quotations, but Atlas has closed sales for some reasons. The reasons can be 1) The sales were manually closed 2) The system has detected a risk of sold out 3) Prohibitions on nearby flights.
- 109: The number of searches exceeded the limit. Description: The searches per day have exceeded the allowed limit. Check with your account manager if there is a restriction to your account.
- 110: Too many concurrent requests.. Description: The QPS (Queries Per Second) is higher than the allowed limit. If your business requires more resources, please contact your account manager.
- 111: Real time search is not allowed. Description: This feature is not activated for your account. Connect with your account manager if you require this service.
- 112: Timed out. Description: The search request has timed-out. For further details please refer to FAQs --> Atlas API General Information.
- 113: Airline is under maintenance. Description: Airline is in "Inactive" or "Maintenance" status with Atlas. This does not necessarily mean that there is an issue with the Airline website itself. Wait for the status to change to “active”.
- 114: No flights present. Description: This may happen when: - The airline does not fly on that date for the searched city pair. Check the airline website to see if the flight is operational for that date.
- 116: Search data not captured. Description: An error was reported during the search data stoprage at Atlas' end. If this error is not constantly reported, you can try trying again. If the error persists, then it is necessary to contact the account manager.
- 123: Too many requests but too few paid orders. Description: The service has been blocked as the search requests are too many and the paid orders are very less.
- 124: Unsupported settlement currency. Description: The settlement currency is different than what is accepted by Atlas. Change the currency to the currency accepted by Atlas for settlement.
- 126:
requestIddoes not exist or request is already ended. Description: - 900: Unauthorized access. Description: Incorrect credentials Or the account status is incorrect Or try to access other customer's data. Check credentials. If the error still persists, contact your account manager.
- 9999: Inner error. Description: There is a problem or a bug in the system. Contact your account manager.
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.
Unique identifier for the search process.
Informing whether the request has been completed.
-true: Indicates that the search has ended
-false: Indicates that the search is still in progress
application/jsonapplication/jsongzipNAR65434_api_1<YOUR_CLIENT_ID>Number of adults
0Example: 1Number of children
0Example: 0Number of infants
0Example: 0Quotation currency, optional, default will be determined based on a certain strategy, such as the currency of the customer's pre deposit account
USDResident discount code
- 0: success
- 116: airline error
- 112: timed out
- 9999: system error
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, such as judging whether the interface response is successful based on this field. You should always judge solely based on whether the status is equal to 0.
application/jsonapplication/jsongzipNAR65434_api_1<YOUR_CLIENT_SECRET>ThesessionIdreturned by price verification api(verify.do). Only required in Non-independent mode.
TheofferIDreturned by get offer api(getOffers.do). Only required in Non-independent mode.
The IATA code of MSC(known as Most Significant Carrier) of the itinerary.
- 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.
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.
api access id
NAR65434_api_1api access secret
changeit建议设置该请求头,能很大程度地减小网络传输报文的大小
gzipapplication/jsonapplication/jsonThesessionIdreturned by verify api(verify.do)
85540632-ef14-4cb2-900e-453ef0a19477Query timeout, unit: milliseconds, default 5000ms. Note: Due to network transmission and computational performance impacts, the client may still receive a normal result (rather than a timeout) even if this duration is exceeded. This time is used to control the overall response time of the interface within a certain range, with an error generally not exceeding a few hundred milliseconds. If you have strict requirements for the timeout, it is recommended to set the timeout of your HTTP toolkit. If the HTTP toolkit you are using does not support this capability, you may need to leverage other tools—related capabilities are generally provided in most programming languages.
5000- 212: illegal parameter.
- 214: offer not exists.
- 205: timed out.
- 299: airline error.
- 9999: system error.
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, such as judging whether the interface response is successful based on this field. You should always judge solely based on whether the status is equal to 0.
Last updated
Was this helpful?

