This section outlines rules that must be followed when using the Booking.com Demand API. API users and partners who do not adhere to these rules or who otherwise abuse Booking.com servers may have their API privileges revoked, losing access to both our availability and static content endpoints. Partners using the **/processBooking** endpoint will also lose the ability to make reservations with the API. Booking.com does not accept any liability for any loss of revenue caused by the disabling of API access for misuse.
## Maximum API Connections
If a user causes an excessive number of connections within one minute, an automated process will disable API access. The limit will never be approached under normal API use and cannot be manually reset or increased.
## Price Comparison
In this context, "price comparison" refers to the comparison of accommodation prices made available from two or more online booking platforms. When an affiliate wishes to use Booking.com properties for the purposes of price comparison, they are not permitted to use any of the content provided by Booking.com or made available through the Booking.com website. This includes, but is not limited to, property descriptions, photos, details of facilities, and policies. As such, the affiliate will be required to use its own content to appropriately describe each property.
## No Data Forwarding
Data forwarding or forward distribution is strictly forbidden. When an affiliate sends data from the Booking.com API to another company that is not affiliated with or part of the company contracted to in the affiliate agreement with Booking.com, this is considered data forwarding or forward distribution. This includes both selling content and giving it away for free.
## Caching of Availability Content and Heavy Caching of Static Content
Some caching is always needed for static content, but these types of content (for example, hotel data) will not change frequently. For these cases, see the recommended update frequency [page](https://developers.booking.com/api/commercial/index.html?version=2.5&page_url=usage-information).
Partners are not allowed to cache availability or prices. This is to ensure the presented information is always as accurate as possible. With the large number of properties on Booking.com, availability and pricing changes very rapidly, so any cache of this data will quickly be rendered inaccurate.
## No Altering the Property Description
The content provided for the property description has been carefully curated by Booking.com to ensure it accurately represents the property and its features. Changing any of this text is strictly forbidden.
## No Changing Prices
The price returned in the availability endpoints is the actual price the property has entered into our system and the price that bookers will pay. Changing this price for any reason is strictly forbidden.
## No Altering or Downloading Property Photos
Property photos come directly from the property, allowing bookers to see exactly what they are getting for their money. Trust in these images is paramount for conversion and cancellation. If these images are tampered with or changed in any way, it could mislead the user. This is therefore strictly forbidden.
Partners must store the URL to hotel images for use in HTML IMG tags. Downloading the image files themselves is not permitted.
## Responsibility to Show Current Data
API users who are caching content are responsible for keeping the data current. This is to ensure content is updated or removed in cases where Booking.com may no longer have permission to use it, or when content is no longer valid. Failure to keep data current may result in complaints being brought against partners. Booking.com cannot take any responsibility for complaints and third-party claims regarding outdated content.
## Closed Properties
If a property has been flagged as closed, partners must remove all related data from their websites, apps, and/or databases.