API Integration related FAQs

Question 1: What are the Airlines and city pairs available in sandbox?

Answer: The sandbox environment allows you to test functions. We provide routes for 10 airlines to ensure you can test various scenarios. You can find available airline and route information in the API document (). Navigate to: API Reference → Atlas Sandbox → Sandbox Test Routes.

Question 2: Can you add specific airlines as per our requirement in sandbox?

Answer: The sandbox environment allows you to test functions. We provide routes for 9 airlines to ensure you can test various scenarios. You can find available airline and route information in the API document (). Navigate to: API Reference → Atlas Sandbox → Sandbox Test Routes.

Of course, if you'd like to test a specific airline or route, feel free to share your testing scenarios and desired airlines or routes with us. Our team will promptly respond to your request.

Question 3: Can we create a booking with up to 9 passengers?

Answer: Many airlines don't provide the maximum available seats for specific fares in their responses. To maintain high bookability, we generally allow bookings for up to 4 passengers by default. We've expanded the maximum seats to 9 for some carriers based on our customers' needs and airlines’ capability. If you require this feature for specific airlines, please let us know, and our team will promptly address your request.

Question 4: Who will support us during the integration process?

Answer: We will initiate a kick-off call where a walk-through will be done for the whole implementation process. The Director - Customer Solutions and the Sales contact will be your support during the integration process.

Question 5: What are the different APIs that Atlas provides for integration?

Answer: Please refer to API documentation in ATRIP where all the available APIs are listed.

Question 6: Can you provide a list of Atlas APIs?

Answer: Please refer to API documentation in ATRIP where all the available APIs are listed.

Question 7: What is the sandbox endpoint for Atlas API?

Question 8: What is the meaning of display currency in your API document?

Answer: This currency and the related amount is converted from the settlement currency using the Atlas currency exchange rate. This amount is only for display purposes and will not be used for fare comparison or accounting purposes.

Question 9: Do you have free Cabin and checked-in baggage information in search API response?

Answer: Yes. Both cabin and checked-in baggage are available in not only search API, but also verify and order API response. Please refer to the "baggageElements" tag.

Question 10: What support will be provided to your customer during the implementation of Atlas's API?

Answer: Atlas will assign a project team to support the customer's integration of Atlas' API. Customers will have access to a preferred communication platform (such as Slack) for the entire integration process. Multiple resources will be available on this platform.

Question 11: What support will be provided to the customer after the implementation of Atlas's API to ensure desired and optimal results are achieved?

Answer: After integration, our growth team will collaborate with your growth team to increase transactions. Meanwhile, if you have any questions about integration, our team is always available to assist you.

Question 12: How many records does Atlas return in the search request? What is the sorting order?

Answer: We have the backend configuration for the response records. The default is 100. The sorting is by fares from low to high.

Question 13: Is there any option to filter the search results?

Answer: The customer can filter the search results using the "airlines" element in the search.do request. Up to 5 airlines can be filtered in the search.

Question 14: Does Atlas have Special Fare with passenger restrictions?

Answer: Special Fare with passenger restrictions like age and nationality are not supported currently.

Question 15: What does TransactionFeePerPax mean?

Answer: Please ignore the field “transactionFeePerPax” as it is a historic field. It's replaced by these two elements: “transactionFee” is the fee negotiated between Customers and Atlas, and "TransactionFeeMode" is the criteria for calculating the transaction fee as per the contractual agreement.

Question 16: What’s the usage of seat count in the search response?

Answer: We do our best to provide the lowest fare to our customers. To achieve this, we collect the fares for the number of seats which we understand would provide us with the best fares. This is the maximum number of seats that can be booked in a single booking with this fare.

Question 17: Why is the Tax breakdown missing in the API response?

Answer: We collect the fares from the airline search page on their website. A lot of LCCs don't provide the tax breakdown in their search response. Hence, we do not provide this information in our search.do response.

Question 18: What is the max time gap allowed between search and revalidation?

Answer: The routingIdentifier is valid for 2 hours. Please note that it is best to verify the fare at the earliest as, when the time gap is longer, the price change possibility will be higher.

Question 19: What is the max time gap allowed between revalidation and order?

Answer: The sessionID is valid for 30 minutes. Please note that it is best to place the order at the earliest as, when the time gap is longer, the price change possibility will be higher.

Question 20: Can I use a different count of passengers in the order step other than search & revalidation steps?

Answer: We accept different passenger counts at various stages, with two restrictions:

The verify passenger count should be equal to or greater than the search passenger count, and equal to or less than the seat count in the search response.
The order passenger count should be equal to or greater than the verify passenger count, and equal to or less than the seat count in the verify response.

Question 21: What will you do when the order hold function happens?

Answer: We do not have an order "hold" function. We provide 30 minutes for each order after it is generated. You can pay for it during this period.

Question 22: Will you hold inventory when the order API calls, if yes, then what is the mechanism to release the inventory?

Answer: We provide 30 minutes to pay for the order. You may consider this as the "hold" function. We manage this feature at the backend with the airlines to provide the best and the most inexpensive content to our customers. We will hold the inventory after the order API calls (wherever available with the airline), and we have our own mechanism to release the inventory. The mechanism varies for different airlines. We can't provide you a function to release the inventory if you request to release it. This will not impact your transaction with Atlas.

Question 23: How do we get the test API credentials?

Question 24: Does Atlas have an option to get fares in user-requested currency?

Answer: Currently, we give the results with the currency which we will settle with the customer (transacting currency). Atlas has also added a new parameter (displayCurrency) for conversion into any currency of the customer's choice. This converted amount is just for information purposes and does not impact billing.

Question 25: How to get special service information like meals, baggage, seat map apart from search and validation API response also? Can we control this information not to be passed in the search response as this will increase response size?

Answer: Currently, Atlas provides two types of ancillaries in the ticketing flow: baggage and seats. For baggage, information is available in both search and verify responses, and it cannot be removed. Regarding concerns about data size, we accept GZip compression, which effectively mitigates this issue. For seats, we offer a dedicated function to provide seat maps and seat availability. This function can only be called after the verify call.

Question 26: Does order API hold the inventory?

Answer: We do not have an order "hold" function. We provide 30 minutes for each order after it is generated. You can pay for it during this period.

Question 27: Can the customer hold the inventory? If yes, what is the mechanism to release it?

Question 28: While going through the Segment Element schema, a few critical nodes are missing like booking class, fare basis, etc. Why?

Answer: We collect the fares from the airline search page on their website. A lot of LCCs don't provide all the possible flight and fare information on the search screen. Hence, a lot of information you receive in the GDS may not be available for LCC carriers. Our API element to get the booking class (RBD) is the "cabin" element.

Question 29: Can a customer modify booking APIs to perform actions like cancellation of PNR, partial cancellation, adding special service meal, baggage, and seats?

Answer: At present, we have post-ticketing baggage and refund functionality via API as well as in ATRIP. We are evolving our post-ticketing features and will add more functionality in the coming months.

Question 30: Can we shop an airline for live inventory?

Question 31: Are credit card surcharges added to the price in your search API?

Answer: We have done thorough analysis and understand the surcharges applicable for different airlines. Wherever applicable, the credit card surcharges are added to the total price of the fare in the search.do API request.

Question 32: What FX exchange rate do you use to convert POS currency prices into the currency setting agreed with Atlas?

Answer: We use the Mastercard exchange rate for converting the currency into the transacting currency.

Question 33: What is the Atlas bookability rate?

Answer: Atlas is currently running at a bookability rate of 97% via our cache results, meaning in only an average of 3 cases per 100 is there a fare change from our cache prices at the ticketing stage.

Question 34: Can the same routingIdentifier be used after a time gap (2-24 hrs) to re-price the fare?

Answer: Sorry, it's not available now. If the workflow is to confirm the booking after a period of time after the initial search, you will need to conduct a search again and then revalidate and get the present price from the airline.

Question 35: Is the vendor currency always the same as the currency of the point of journey commencement?

Answer: The vendor currency is the currency in which Atlas pays the airline. The vendor currency is available in the API responses where Atlas accepts VCC mode of payment from customers. However, the currency is not always the same as the point of journey commencement. The logic depends on: 1) Airline route’s original pricing; 2) Some currencies not supported by Atlas, which are converted into a supported currency.

Question 36: Is pricing with account number/corporate number supported?

Answer: We can't support this feature generally at the moment. Could you please provide specific user scenarios? Our team will review them and get back to you.

Question 37: Are connecting flights supported?

Answer: Yes. We support all the flights available on the airline’s list of routes.

Question 38: Is open-jaw, multi-city, circle trip supported?

Answer: At the moment, we do not support open-jaw, multi-city, and circle trips.

Question 39: Is a mix of carriers within a single transaction supported (e.g., LS+ G9)?

Answer: Generally, we don't offer mixed carrier options. However, for round-trip search, we provide a configuration that allows you to receive one-way + one-way fares if they're cheaper than the round-trip fare.

Question 40: Is credit card payment supported?

Answer: Yes. We accept credit card payment as a pass-through method, which means we will send your card to the airline directly to be charged by the airline. The airline may have restrictions on certain cards, and hence the payment can get declined.

Question 41: Are connecting flights displayed in the search response?

Answer: Yes, connecting flights are also available in the search response.

Question 42: Does Atlas support infant passenger type?

Answer: Yes. Infant passenger type is supported on Atlas' platform. There may be a few airlines where infants are not supported, which will be addressed in the search response "infantAllowed."

Question 43: What is the format of the Atlas schema?

Answer: Atlas schema is a RESTful API in JSON format.

Question 44: Do you have a Postman project for your API?

Answer: Yes. You can download the Postman project from ATRIP. The project is available in ATRIP → API Document → API Reference → Atlas Sandbox → UAT Submission Guide.

Question 45: What credit card details do we use in sandbox while creating a booking via VCC mode of payment?

Answer: You may use any fictitious details for the VCC details in the sandbox environment.

Question 46: Does Atlas support fare families?

Answer: We do not support fare families/bundles at the moment. We are working on the development of this product and expect to release it in 2025. If you don't mind, could you please share your user scenario for fare families?

Question 47: Are there any checks for duplicate bookings? If so, who is checking? Atlas or airline?

Answer: We have a duplicate booking check. We will compare the booking request with PNRs created in the last 10 days and check for duplication with existing PNRs within the Atlas system. This reduces errors during the ticketing process.

Question 48: How does Atlas construct options with connection flights? Is it by minimum connection time (shortest waiting time)? Is it by the cheapest price? Does Atlas cut some options based on criteria?

Answer: Atlas does not construct any options at its end for connecting flights. Whatever options are available with the airline are captured and provided to our customers during the search.

Question 49: Does Atlas compare the price returned in Verify with the price sent back in Order at the moment of fulfillment?

Answer: Yes, we compare the price during the booking with the verification price.

Question 50: If there is any price difference, how would Atlas react? Would it block the transaction with an error message?

Answer: Atlas would cancel the booking and send the error code "308 (Price changed)." If the customer has negotiated for Atlas to contact their operations team before canceling the order, we will get in touch via the preferred communication medium.

Question 51: What is the transaction fee returned in the SEARCH response?

Answer: The “transactionFee” is the fee negotiated between customers and Atlas. This amount should be read with "TransactionFeeMode." Please ignore the field "transactionFeePerPax" as it is a historic field.

Question 52: Are the flight options and their availability returned from Atlas cache?

Answer: Yes, we have a robust cache mechanism with a high success rate and a response speed of less than 500ms. To achieve this, we provide the flight options and availability from our cache.

Question 53: What happens if there are no seats available (all seats sold out) at the moment of Verify?

Question 54: What happens if the available fare is sold out and only a more expensive option is available?

Answer: Atlas would provide the price change information in the "priceChange" array at the bottom of the verify response.

Question 55: What about credit card payment fees? Are they added to the fare?

Answer: We have done thorough analysis and understand the surcharges applicable for different cards. Wherever applicable, the credit card surcharges are added to the total price of the fare in the search.do API request.

Question 56: How do we know what fields are mandatory in the booking request?

Answer: The mandatory information required in the booking request will be provided in the verification response as shown in the bookingRequirements array. We have an in-house table that regularly checks the requirements for the airlines and keeps it updated.

Question 57: Do we need to add the passport information for all passenger types?

Answer: Yes, if mentioned as "required" in the booking requirements info in the verify response, the passport information needs to be added for all passenger types. The mandatory information will be available in the verify.do response in the bookingRequirements array.

Question 58: Are all fields in the pay.do request for VCC pass-through mandatory?

Answer: Yes. These fields have been kept "mandatory" because some airlines need all the information. There is no way to identify which airline needs it as the policy of the airline may change from time-to-time.

Question 59: Why might ticketing in the sandbox environment take more than 10 minutes?

Answer: This is a sandbox environment used for various tests. These issues may occur in this environment. Sometimes the ticketing needs to be manually pushed in the sandbox environment.

Question 60: In which cases might there be more than one airlinePNR code?

Answer: To provide the lowest possible fare, two airlines may be combined to provide the cheapest option for a round-trip. As the itinerary has two different airlines, there will be two airlinePNRs in the airlinePNRs element.

Question 61: Can we send an Order request again with the same order number as originally done?

Answer: Once an order is created, it cannot be amended. If a new order with identical information is submitted, it will be rejected as a duplicate. You must wait for the original order to expire before submitting a new one.

Question 62: What is the contact phone number format?

Answer: Please follow this format: XXXX (digital country code) - XXXXXXXX (phone number). Examples: 0001-87291810, 0086-13928109091, 0971-19201998. There is a limit of 30 characters (including the hyphen) for this field.

Question 63: What is tktLimitTime from the Order response, and what is its impact?

Answer: The tktLimitTime defines the time within which the payment needs to be made for the booking. This time limit is as per the SGT time zone. If the payment is not done within this time, the booking will expire.

Question 64: Can we test the API functionality before partnering with Atlas?

Answer: Yes, you can test Atlas API functionality before making a commitment. Please fill out the contact form, and we will get in touch with you within two working days. To protect our partner airlines, we need to confirm your details and get you to sign an NDA. After verification, test credentials will be sent to your inbox.

Question 65: Are there any restrictions on the API functionality for any of the airlines?

Answer: We strive to offer maximum opportunities for both our partner airlines and travel agencies. As new features are integrated, functionality is added to airlines incrementally.

Question 66: Does Atlas support promotional fare or promotional code-based pricing?

Answer: We currently offer general promotional fare functionality but don't support promo codes by default. For specific airlines, we may have this capability. Please leave a message if you're interested, and our team will contact you for details.

Question 67: Is there a timeout limit for Atlas APIs?

Answer: Yes, the timeout limits are as follows:

search.do: No limit defined
realTimeSearch.do: 120 seconds
verify.do: 15 seconds
order.do: 15 seconds for normal booking, 120 seconds for real-time booking
pay.do: No limit defined

Question 68: What is the API response time for each Atlas API?

Answer: Average response times are:

search.do: <500ms (98% of responses returned in less than 500ms)
realTimeSearch.do: 25 seconds
verify.do: 8 seconds (90% of responses returned in less than 8 seconds)
order.do: 8 seconds (90% of responses returned in less than 8 seconds)
pay.do: 2 seconds (90% of responses returned in less than 2 seconds)

Question 69: Can users change the currency to view ticket prices in their local currency?

Answer: Yes. Customers can use the parameter displayFare in the search and verify APIs to get the amount in their chosen currency. This fare is for display purposes only and will not impact billing.

Question 70: How many results does the search query return, and what is the default sorting order?

Answer: By default, the search query returns up to 100 results, sorted by fares from low to high.

Question 71: Can we allow users to change the passenger count in the order step from what they entered in the search and revalidation steps?

Answer: Yes, with restrictions:

The verify passenger count must be equal to or greater than the search passenger count and equal to or less than the seat count in the search response.
The order passenger count must be equal to or greater than the verify passenger count and equal to or less than the seat count in the verify response.

Question 72: Does the OrderAPI hold the inventory? If yes, for how long?

Answer: Yes, inventory is held for 30 minutes after the order is generated. Payment must be made during this time.

Question 73: Can we release the inventory held at our end?

Answer: Inventory is managed at the backend. While we hold inventory for 30 minutes, there is no function to release it on request. This does not impact your transaction with Atlas.

Question 74: Atlas's obligations to maintain API connectivity.

Answer: We guarantee API connectivity 99.9%.

Question 75: Does Atlas have processes in place to monitor performance and trigger notifications to Sabre?

Answer: Yes. We monitor our vendors (airlines) round the clock. If vendor API quality does not meet expectations, we disable the vendor pricing in the search (shopping) API while continuing to check the API quality.

Question 76: What Data Protection measures does Atlas have in place for GDPR and PCI DSS?

Answer: Atlas is both PCI DSS and GDPR compliant.

Question 77: What Security standards does Atlas have in place to prevent breaches?

Answer: Atlas uses Alibaba Cloud Container Service and follows Alibaba Cloud security best practices. We also use GCP Container and follow GCP security best practices.

Question 78: Does Atlas have a Disaster Recovery plan?

Answer: We use three data centers in an “Active-Active-Active” mode, mitigating the risk of data loss for customers.

Question 79: What is the SLA to resolve errors where the Atlas API or service is unavailable or impaired?

Answer:

Severity 1: 30 minutes.
Severity 2: 3 hours.
Severity 3: 24 hours.
Non-critical issues: 2 days.

Question 80: Where will we find API documentation?

Question 81: Does Atlas provide monitoring console/dashboards?

Answer: Yes. A dashboard provides segment information, and more features are continuously being added.

Question 82: Is there any backend module available other than API for creating bookings in case of failover?

Answer: Not currently. We are exploring the possibility of booking via a portal in the future.

Question 83: What should we do if we encounter API failure?

Answer: Use the ATRIP web portal for post-ticketing services or contact the API support team.

中文版本

问题1：沙盘环境中提供了哪些航空公司和城市对？

问题2：我们可以根据需要在沙盘环境中添加特定航空公司吗？

当然，如果您希望测试特定航空公司或航线，请随时与我们分享您的测试场景和所需的航空公司或航线。我们的团队将及时回应您的请求。

问题3：我们可以为多达9名乘客创建预订吗？

答：许多航空公司在其响应中并不提供特定票价的最大可用座位。为了保持高预订可行性，我们通常默认允许最多4名乘客预订。根据我们客户的需求和航空公司的能力，我们已经为某些航空公司将最大座位数扩展到9。如果您需要该功能适用于特定航空公司，请告诉我们，我们的团队将及时处理您的请求。

问题4：在整合过程中谁会给我们提供支持？

答：我们将启动一次启动电话，在整个实施过程中将进行一次介绍。客户解决方案总监和销售联系人将在整合过程中为您提供支持。

问题5：Atlas提供了哪些不同的API用于整合？

答：请参阅ATRIP中的API文档，其中列出了所有可用的API。

问题6：您能提供Atlas API的列表吗？

答：请参阅ATRIP中的API文档，其中列出了所有可用的API。

问题7：Atlas API的沙盘端点是什么？

问题8：API文档中的显示货币是什么意思？

答：此货币及相关金额是根据Atlas货币汇率从结算货币转换而来的。此金额仅供显示目的，不会用于票价比较或会计目的。

问题9：在搜索API响应中，您是否提供免费的舱内和托运行李信息？

答：是的。不仅在搜索API中，舱内和托运行李信息也在验证和订单API响应中提供。请参考“baggageElements”标签。

问题10：在实施Atlas的API过程中，将会提供哪些支持给您的客户？

答：Atlas将分配一个项目团队来支持客户整合Atlas的API。客户将可以使用首选通信平台（例如Slack）进行整个整合过程的沟通。该平台上将提供多种资源。

问题11：在实施Atlas的API后，将提供哪些支持以确保实现期望和最佳结果？

答：在整合后，我们的增长团队将与您的增长团队合作，以增加交易量。与此同时，如果您对整合有任何问题，我们的团队随时可用以协助您。

问题12：Atlas在搜索请求中返回多少条记录？排序顺序是什么？

答：我们对响应记录进行了后端配置。默认情况下为100条。按票价从低到高排序。

问题13：可否对搜索结果进行筛选？

答：客户可以使用搜索请求中的“airlines”元素对搜索结果进行筛选。在搜索中最多可以筛选5家航空公司。

问题14：Atlas是否有带有乘客限制的特殊票价？

答：目前不支持带有年龄和国籍等乘客限制的特殊票价。

问题15：“TransactionFeePerPax”是什么意思？

答：请忽略“transactionFeePerPax”字段，因为它是一个历史字段。它已被以下两个元素取代：“transactionFee”是客户和Atlas之间协商的费用，“TransactionFeeMode”是根据合同协议计算交易费的标准。

问题16：搜索响应中的座位数量有什么用？

答：我们尽力为客户提供最低票价。为了实现这一目标，我们收集了我们认为可以提供最低票价的座位数量的票价。这是可以在单次预订中以该票价预订的座位的最大数量。

问题17：为什么API响应中缺少税费细目？

答：我们从航空公司网站的机票搜索页面上收集票价。许多低成本航空公司在其搜索响应中不提供税费的细目。因此，我们在我们的search.do响应中不提供这些信息。

问题18：搜索和重新验证之间允许的最大时间间隔是多长？

答：routingIdentifier有效期为2小时。请注意，最好尽早验证票价，因为时间间隔越长，票价变动的可能性就越大。

问题19：重新验证和订单之间允许的最大时间间隔是多长？

答：sessionID有效期为30分钟。请注意，最好尽早下订单，因为时间间隔越长，票价变动的可能性就越大。

问题20：在订单步骤中，除了搜索和重新验证步骤使用的乘客数量外，可以使用不同数量的乘客吗？

答：我们接受在不同阶段使用不同数量的乘客，但有两个限制：

验证乘客数量应等于或大于搜索乘客数量，且等于或小于搜索响应中的座位数量。
订单乘客数量应等于或大于验证乘客数量，且等于或小于验证响应中的座位数量。

问题21：订单保留功能发生时会怎么做？

答：我们没有订单“保留”功能。在订单生成后，我们提供30分钟的时间进行支付。

问题22：下订单时是否会保留库存？如果会的话，释放库存的机制是什么？

答：我们提供30分钟的时间进行订单支付。您可以将此视为“保留”功能。我们在后端管理此功能，以与航空公司合作为客户提供最佳和最经济的内容。我们将在订单API调用后保留库存（如果在航空公司处提供），并且我们有自己的机制释放库存。释放库存的机制因航空公司而异。如果您要求释放库存，我们无法为您提供释放库存的功能。这不会影响您与Atlas的交易。

问题23：我们如何获得测试API凭据？

问题24：Atlas是否有以用户请求的货币获取票价的选项？

答：目前，我们使用与客户结算的货币（交易货币）提供结果。Atlas还添加了一个新参数（displayCurrency）用于转换为客户选择的任何货币。此转换金额仅供信息用途，并不影响计费。

问题25：除了搜索和验证API响应外，如何获取特殊服务信息（如餐食、行李、座位图）？我们可以控制此信息不传递到搜索响应中以减小响应大小吗？

答：目前，Atlas在机票销售流程中提供两种附加服务：行李和座位。行李信息在搜索和验证响应中都可以获得，并且无法移除。至于数据大小方面的担忧，我们接受GZip压缩，这有效地减轻了这个问题。对于座位，我们提供专门的功能来提供座位图和座位可用性。此功能只能在验证调用后调用。

问题26：订单API会保留库存吗？

答：我们没有订单“保留”功能。在订单生成后，我们提供30分钟的时间进行支付。

问题27：客户可以保留库存吗？如果可以，释放库存的机制是什么？

答：我们提供30分钟的时间用于订单支付。您可以将此视为“保留”功能。我们在后端管理此功能，以与航空公司合作为客户提供最佳和最经济的内容。我们将在订单API调用后保留库存（如果在航空公司处提供），并且我们有自己的机制释放库存。释放库存的机制因航空公司而异。如果您要求释放库存，我们无法为您提供释放库存的功能。这不会影响您与Atlas的交易。

问题28：在查看Segment Element模式时，为什么缺少一些关键节点，如预订等级、票价基础等？

答：我们从航空公司网站的机票搜索页面上收集票价。许多低成本航空公司在其搜索页面上并不提供所有可能的航班和票价信息。因此，您在GDS中获得的很多信息可能不适用于低成本航空公司。我们的API元素用于获取预订等级（RBD）的是“cabin”元素。

问题29：客户能否修改预订API以执行取消PNR、部分取消、添加特殊服务（例如餐食、行李、座位）等操作？

答：目前，我们通过API和ATRIP提供售后服务的行李和退款功能。我们正在不断完善后续服务功能，并将在未来几个月内增加更多功能。

问题30：我们能否查询航空公司的实时库存？

问题31：在您的搜索API中是否包含信用卡附加费用？

答：我们已经进行了深入分析，了解了不同航空公司适用的附加费用。在适用的情况下，信用卡附加费用会被加到search.do API请求的票价总额中。

问题32：您使用何种外汇汇率将POS货币价格转换为与Atlas达成协议的货币设置？

答：我们使用Mastercard的汇率将货币转换为交易货币。

问题33：Atlas的预订可行性率是多少？

答：目前，Atlas在我们的缓存结果中的预订可行性率为97%，意味着每100次中仅平均有3次在票务阶段与我们缓存价格不同。

问题34：在时间间隔（2-24小时）后能否重复使用相同的routingIdentifier来重新定价票价？

答：抱歉，目前不支持。如果工作流程是在进行初始搜索后一段时间内确认预订，您需要再次进行搜索，然后重新验证并从航空公司获取当前价格。

问题35：供应商货币是否始终与旅程始发地点的货币相同？

答：供应商货币是Atlas向航空公司支付的货币。供应商货币在接受客户的VCC（供应商支付卡）支付方式的API响应中可以看到。然而，货币并不始终与旅程始发地点的货币相同。逻辑取决于：1）航线的原始定价；2）Atlas不支持的一些货币将被转换为支持的货币。

问题36：是否支持带有账号/公司编号的定价？

答：目前我们一般不支持此功能。请提供具体的用户场景吗？我们的团队将对其进行评估并回复您。

问题37：是否支持联程航班？

答：是的。我们支持航空公司路线列表中提供的所有航班。

问题38：是否支持开放式来回程、多目的地旅行、环形旅行？

答：目前我们不支持开放式来回程、多目的地旅行和环形旅行。

问题39：是否支持在单笔交易中混合使用不同航空公司（例如LS+ G9）？

答：一般来说，我们不提供混合航空公司的选项。但是对于往返搜索，我们提供了一个配置，可以使您收到单程+单程的票价，如果它们比往返票价更便宜的话。

问题40：是否支持信用卡支付？

答：是的。我们接受信用卡支付作为过渡支付方式，这意味着我们将您的信用卡直接发送给航空公司进行支付。航空公司可能对某些卡有限制，因此支付可能会被拒绝。

问题41：在搜索响应中是否显示联程航班？

答：是的，联程航班也会在搜索响应中显示。

问题42：Atlas是否支持婴儿乘客类型？

答：是的。Atlas平台支持婴儿乘客类型。可能有一些航空公司不支持婴儿乘客，该信息将在搜索响应的“infantAllowed”中得到体现。

问题43：Atlas架构的格式是什么？

答：Atlas的架构是JSON格式的RESTful API。

问题44：您是否为您的API提供Postman项目？

答：是的。您可以从ATRIP下载Postman项目。该项目在ATRIP → API文档 → API参考 → Atlas沙盒 → UAT提交指南中可获取。

问题45：在沙盒环境中使用VCC支付模式创建预订时，我们使用哪些信用卡详情？

答：您可以在沙盒环境中使用任意虚构的信用卡详细信息进行VCC支付。

问题46：Atlas是否支持票价套餐？

答：我们目前不支持票价套餐/捆绑包。我们正在开发这一产品，并预计将于2025年发布。如果您不介意，请分享您对票价套餐的用户场景？

问题47：是否有重复预订检查？如果有，是Atlas还是航空公司进行检查？

答：我们对重复预订进行了检查。我们将比较预订请求与过去10天内创建的PNR，并检查在Atlas系统内现有PNR的重复情况。这可以减少在出票过程中的错误。

问题48：Atlas如何构建带有联程航班的选项？是通过最短转机时间（等待时间最短）吗？还是通过最便宜的价格？Atlas是否会根据标准删减一些选项？

答：Atlas并不会为联程航班在自身端构建任何选项。我们会捕捉航空公司提供的任何选项，并在搜索过程中呈现给我们的客户。

问题49：在履行时，Atlas是否会将验证返回的价格与订单中返回的价格进行比较？

答：是的，我们会将预订时的价格与验证价格进行比较。

问题50：如果存在价格差异，Atlas会如何做出反应？会阻止交易并显示错误消息吗？

答：Atlas将取消预订并发送错误代码“308（价格变动）”。如果客户已经与Atlas就取消订单之前联系其运营团队进行协商，我们将通过首选的沟通媒介与客户联系。

问题51：SEARCH响应中返回的交易费是什么？

答： "transactionFee"是客户和Atlas之间协商的费用。此金额应与“TransactionFeeMode”一同阅读。请忽略字段“transactionFeePerPax”，因为它是一个历史字段。

问题52：来自Atlas缓存的航班选项及其可用性是如何返回的？

答：是的，我们有一个强大的缓存机制，成功率很高，响应速度低于500毫秒。为此，我们从缓存中提供航班选项和可用性。

问题53：如果在验证时没有座位可用（所有座位已售完），会发生什么？

问题54：如果可用票价售罄，只有更贵的选项可用会发生什么？

答：Atlas将在验证响应底部的“priceChange”数组中提供价格变更信息。

问题55：信用卡付款费用会被加到票价中吗？

答：我们已经进行了彻底分析，了解了适用于不同信用卡的附加费用。在适用的情况下，信用卡附加费用会被加到search.do API请求中的票价总额中。

问题56：如何确定预订请求中的哪些字段是强制性的？

答：预订请求中所需的强制性信息将在验证响应的bookingRequirements数组中提供。我们有一个内部表格，定期检查航空公司的要求并进行更新。

问题57：是否需要为所有乘客类型添加护照信息？

答：是的，如果在验证响应中的预订要求信息中标记为“必填”，则需要为所有乘客类型添加护照信息。强制性信息将在验证.do响应的bookingRequirements数组中提供。

问题58：VCC过渡支付的pay.do请求中的所有字段是否都是强制性的？

答：是的。这些字段被设置为“强制”，因为一些航空公司需要所有信息。由于航空公司的政策可能会不时变更，因此无法确定哪些航空公司需要这些信息。

问题59：为何在沙盒环境中出票会超过10分钟？

答：这是一个用于各种测试的沙盒环境。这些问题可能在此环境中发生。有时需要在沙盒环境中手动进行出票。

问题60：在哪些情况下可能会有不止一个航空公司PNR代码？

答：为了提供尽可能低的票价，两家航空公司可能合作提供往返的最便宜选项。由于行程包括两家不同航空公司，因此在airlinePNRs元素中将会有两个航空公司PNR。

问题61：我们可以使用与最初相同的订单号再次发送订单请求吗？

答：一旦创建订单，就不能对其进行修改。如果提交了具有相同信息的新订单，它将被拒绝为重复订单。您必须等待原始订单过期后再提交新订单。

问题62：联系电话号码的格式是什么？

答：请按照以下格式：XXXX（数字国家代码）- XXXXXXXX（电话号码）。例如：0001-87291810，0086-13928109091，0971-19201998。此字段的字符限制为30个（包括连字符）。

问题63：订单响应中的tktLimitTime是什么，有什么影响？

答：tktLimitTime定义了需要在预订中进行支付的时间。这个时限按照新加坡时间中心时区规定。如果在此时间内未完成支付，预订将会过期。

问题64：在与Atlas合作之前，我们可以测试API功能吗？

答：是的，您可以在与Atlas达成承诺之前测试Atlas API功能。请填写联系表格，我们将在两个工作日内与您联系。为了保护我们的合作航空公司，我们需要确认您的详细信息并签署保密协议。验证后，测试凭证将发送至您的收件箱。

问题65：对任何航空公司的API功能是否有任何限制？

答：我们努力为我们的合作航空公司和旅行社提供最大的机会。随着新功能的整合，功能会逐渐增加到航空公司。

问题66：Atlas是否支持促销票价或基于促销码的定价？

答：目前，我们提供一般的促销票价功能，但默认情况下不支持促销码。对于特定航空公司，我们可能具有此功能。如果您对此感兴趣，请留言，我们的团队将与您联系以获取详细信息。

问题67：Atlas的API是否有超时限制？

答：是的，超时限制如下：

Search.do：未定义限制
RealTimeSearch.do：120秒
Verify.do：15秒
Order.do：正常预订15秒，实时预订120秒
pay.do：未定义限制

问题68：Atlas的每个API的响应时间是多少？

答：平均响应时间如下：

search.do：500毫秒以下（98%的响应在500毫秒内返回）
realTimeSearch.do：25秒
verify.do：8秒（90%的响应在8秒内返回）
order.do：8秒（90%的响应在8秒内返回）
pay.do：2秒（90%的响应在2秒内返回）

问题69：用户可以更改货币以查看本地货币的机票价格吗？

答：可以。客户可以在搜索和验证API中使用displayFare参数来获取其选择货币的金额。此金额仅用于显示目的，不会影响账单。

问题70：搜索查询会返回多少结果，以及默认的排序顺序是什么？

答：默认情况下，搜索查询会返回多达100个结果，按照票价从低到高排序。

问题71：用户可以在订单步骤中更改乘客数量，与他们在搜索和重新验证步骤中输入的数量不同吗？

答：可以，有一些限制：

验证乘客数量必须等于或大于搜索乘客数量，并且等于或小于搜索响应中的座位数量。
订单乘客数量必须等于或大于验证乘客数量，并且等于或小于验证响应中的座位数量。

问题72：订单API会保留库存吗？如果会，会保留多长时间？

答：会的，订单生成后将会保留库存30分钟。在此期间必须完成支付。

问题73：我们可以释放我们持有的库存吗？

答：库存由后端管理。虽然我们会在30分钟内持有库存，但没有根据请求释放库存的功能。这不会影响您与Atlas的交易。

问题74：Atlas保持API连接的义务是什么？

答：我们保证API连接率为99.9%。

问题75：Atlas是否有监控性能并触发通知至Sabre的流程？

答：是的。我们全天候监控供应商（航空公司）。如果供应商API质量达不到预期，我们会在搜索API中禁用供应商定价，同时继续监测API质量。

问题76：Atlas针对GDPR和PCI DSS采取了哪些数据保护措施？

答：Atlas符合PCI DSS和GDPR标准。

问题77：Atlas采取了哪些安全标准以防止违规？

答：Atlas使用阿里巴巴云容器服务，并遵循阿里巴巴云的安全最佳实践。我们还使用GCP容器，并遵循GCP的安全最佳实践。

问题78：Atlas是否有灾难恢复计划？

答：我们采用“主-主-主”工作模式的三个数据中心，降低了客户数据丢失的风险。

问题79：在Atlas API或服务不可用或受影响时解决错误的SLA是多少？

答：

严重性1：30分钟。
严重性2：3小时。
严重性3：24小时。
非关键问题：2天。

问题80：我们在哪里可以找到API文档？

答：全面的API文档可在ATRIP中找到。

问题81：Atlas是否提供监控控制台/仪表板？

答：是的。仪表板提供分段信息，而且还在不断增加更多功能。

问题82：除了API外，在故障转移情况下是否有其他后端模块可用于创建预订？

答：目前没有。我们正在探索未来通过门户进行预订的可能性。

问题83：如果遇到API故障，我们应该怎么做？

答：使用ATRIP网页门户进行售后服务，或联系API支持团队。

PreviousFeatures & Content Related FAQs NextPayments related FAQs

Last updated 5 months ago

Was this helpful?