News
Keep yourself updated with our latest news and announcements.
25/02/2025 - Digital Services Act (DSA)
| Demand API v3 and v2 | Compliance | Accommodations new fields | trader_type and trader_verified | new legislation |
The Digital Services Act (DSA), specifically in relation to Article 24 (Trader Traceability) is an EU law on consumer protection that requires digital platforms (including Booking.com) to collect, verify and display certain information from accommodation partners identified as
traders
(professional hosts) in all countries.This information needs to be shown to all EEA users.
Note this is only applicable to accommodations, not to car rentals or any other travelling service.
Trader information and new functionality
In line with our ongoing commitment to ensuring compliance with DSA, we previously introduced a
trader
object returning trader information such as contact, address, phone number, etc. (for further details, see here).We have now introduced a new functionality that automatically excludes non-verified properties from Demand API v3 accommodations/search and availability responses and /hotelAvailability and /blockAvailability responses in v2, based on the booker country.
Technical details
If you want to know more details about which properties are not being displayed due to the filtering, you can check these fields:
host_type | This field helps further distinguish the nature of the accommodation provider, whether is a professional , private or unknown host. |
| This field explicitly indicates whether a property meets the standards set by Booking.com, determining whether it should be excluded for EEA travellers. ✓ true - The property has passed Booking.com's verification process and can be displayed to all users, including EEA travellers. ✗ false - The property has failed the verification and must not be displayed to EEA users. |
These fields have been added to both v2 and v3.
Version | Endpoint | Details | References |
---|---|---|---|
v3 | /accommodations/details | These fields are retrieve when passing "description" as extras. | More details in DSA compliance guide. |
v2 | /hotels | This information is returned when passing hotel_info and trader_info, as extras. | Refer to the v2 Changelog for more details. |
If you are not already familiar with DSA and the impact this has on your business, we advise you to familiarise yourself and update your implementation as required in accordance with the obligations set out in the DSA.
Previous updates
19/12/2024 - New price display in Minnesota, US
| Demand API V3 and V2 | US | Minnesota state | new legislation |
A new price transparency law came into effect in Minnesota, U.S. in January 1st, 2025. It requires prices to be shown in full (including all mandatory fees) for both properties located in Minnesota and for travellers browsing for any property globally from the state of Minnesota.
Our Demand API is designed to allow users to provide prices with no hidden fees and maximum transparency. The right total price and price breakdown provided is based on the input of the correct country or state.
We’ve updated our Demand API so you can now provide the correct inputs for this new legislation.
Similar to the updates introduced for the California price display legislation earlier in 2024, from January 1st, 2025 all properties located in Minnesota were switched to the new price display (for the less strict price display modes).
Refer to November changelog for the technical details.
01/10/2024 Cars API soft launch
| Cars API | Early adopters |
Our new Cars API for Car rentals is now live.
- If you are part of the early adopters pilot, then you can already play around with our brand new Cars API endpoints.
- In case you are not part of the pilot, don't miss the chance to get familiar with it by checking:
- Our Cars API Quick guide
- Some of the endpoint examples
30/8/2024 Demand API V2 end of service
Update - Demand API V2 end of service 30/8/2024 | Demand API V2 | Deprecation |
As advised, we have moved forward with V2 EOS for type 2 partners.
- V2 is no longer available for search (type 2) partners.
- All search partners should now be using Version 3. We also advise using the most up-to-date minor version available.
- If you don't have access yet, please request it via this link here to get started.
- If you already have access to V3, we encourage you to complete the upgrade process as soon as possible.
Refer to our Migration guide for help upgrading to V3.
Changelog - February 2025
Back to documentation