This Acceptable Use Policy outlines the terms under which customers may access and use the Bonotel Interface API. By using the API, customers agree to adhere to this policy and any amendments that may be made from time to time.

Customers are granted a Shopping Look-to-Book (SLB) limit of 100,000:1 evaluated monthly. This means that for every confirmed booking, customers may perform up to 100,000 "looks" or search combinations. Exceeding this limit will result in additional charges based on the volume of excess "looks." If a customer anticipates consistently exceeding this limit, they must enter into an amendment to include an overage charge cost schedule with Bonotel.

"Looks" are defined as individual search combinations. For example:

Any traffic in excess of the 100,000:1 ratio will be charged at a rate of $0.75 per 100,000 additional "looks," starting from the 100,001st look. For example, if a booking requires 300,000 total "looks," the cost will be $1.50.

Failure to adhere to the SLB Limit over three consecutive months or failure to pay overage charges will be considered a material breach of the agreement and may result in termination of access to the API.

The API has a maximum threshold of 250 requests per second. This threshold is designed to ensure optimal performance and reliability for all customers. Exceeding this threshold more than a few dozen times per hour indicates a significant change in traffic patterns and may result in throttling of requests.

Customers must monitor their traffic patterns and make necessary adjustments to avoid excessive requests. Factors such as changes in hotel mapping, new customer integrations, and public reservation site updates can impact traffic. Customers should revert any changes that do not maintain compliance with designated thresholds.

Bonotel reserves the right to throttle or block requests that exceed the maximum request threshold or negatively impact system performance. Customers will be notified of such actions and are expected to address the underlying issues promptly.

Bonotel assumes no responsibility for booking errors due to incorrect rates provided through the API. In cases where an incorrect rate is identified, Bonotel will work with customers to resolve the issue on a case-by-case basis. Customers should promptly report any discrepancies to ensure timely resolution.

The API does not allow modifications to confirmed bookings. Any changes must be handled as a cancellation and rebooking under the new desired criteria. However, in some cases, modifications may be arranged by contacting the Bonotel call center directly at +1 (702) 796-5454. Modifications arranged through the call center may incur additional fees.

Bonotel has established a timeout value of 60 seconds for all upstream API connections for the purposes of confirming a reservation. Customers are required to implement the same 60-second timeout value for their API requests to Bonotel.

Customers must continue to "listen" for a response from Bonotel for up to 60 seconds after initiating a reservation request. In cases where a customer stops listening before the 60-second period ends, but a reservation is confirmed by a supplier within that timeframe, the customer will still be held liable for that reservation. Customers are highly encouraged to utilize the "reservation report" and "lookup" methods frequently as a means to verify and audit confirmed bookings. If a customer notes unintended confirmed bookings, they should immediately initiate a cancellation request via the API, the website, or the call center.

Static data, including hotel IDs and associated hotel information, is refreshed and published weekly. This data can be retrieved via the API or downloaded as multiple files.

Customers are expected to update their static data mapping on a weekly basis to ensure they have the most current information. Failure to do so may result in requesting hotels that are no longer active and missing out on newly-available hotels.

Using outdated static data can lead to inefficiencies and reduced accuracy in availability requests. Customers should regularly refresh their data to optimize their use of the Bonotel API and ensure they are accessing the latest hotel information.

The "Pre-book" method is designed to bypass any potential availability caching and go straight to the source before attempting to confirm a reservation. This helps prevent mismatches between cached availability data and actual availability, reducing reservation errors.

Customers are expected to use the "Pre-book" method solely for the purpose of confirming availability of a booking before actually confirming it. Using the "Pre-book" method as an availability search tool is considered misuse. If a customer misuses the "Pre-book" method, their access to this feature will be removed.

Customers are expected to regularly monitor their usage and ensure compliance with this policy. Bonotel will also conduct routine audits and provide feedback to customers. Any non-compliance may result in restricted access or termination of API services.

For questions or assistance regarding this policy or API usage, customers should contact their Bonotel representative or reach out to our support team via the helpdesk portal at https://bonotel.atlassian.net/servicedesk/customer/portal/6 or via email at: [email protected].