Switch to version 2 of the Demand API:
version 1 will be switched off by the end of the day on the 15.02.2019!
It has been more than one year since we have communicated the Launch of V2 of the Demand API (sent on Oct 3, 2017, Subject; Important Announcement Booking.com Demand API v2), and we are very excited to see the improved performance of partners that are already fully on Version 2.
Majority of our partners have adopted the new version, however, we still see that you are making use of Version 1 and missing all the newly added features that are rolled out during the past year. That is why we are reaching out to you again.
By the end of the day on the15th of February 2019, we will switch off V1 endpoints. We recommend you to switch to V2 by then, and going for the latest version (2.3) so you benefit from all new features that were launched in the minor versions. Here below all the new features are also outlined.
Why switch to V2?
Major bug fixes and support have stopped for V1 since July 2018. Bugs are no longer fixed, and users who request support for v1 are directed to upgrade to v2 in order to obtain support.
V2 is faster, more stable, and much simpler to use.
All endpoint names and parameters have been standardized across the entire API.
The static content endpoints have been totally reworked so that getting content is easier, faster, and more intuitive.
The way in which changed content is monitored and delivered has been greatly improved.
Versioning the API enables us to roll out many improvements at the same time while allowing our partners to test the new functionality before migrating.
IMPORTANT: When using processBooking; blockAvailability and processBooking need to be on the same version.
What new features are available in the new Version?
All new features of the new (minor) versions are uploaded in our Change Log in our documentation. For technical details such as sample output for each feature, view the technical documentation. Below in this email you can also find per minor version which features are available.
(The latest version will always have all features included).
Questions and support
API versions in the documentation at developers.booking.com.
We have created a migration guide for users that are moving from v1 to v2.
If you have questions or need support see the contact information at the developer portal.
The Booking.com Demand API team
Endpoints that will be switched off:
All New Features available in Version 2.3:
Availability can be queried up to 500 days into the future.
Add license_number as a separate field (extras=important_information).
Output lunch_included and dinner_included has been added (extras=mealplans).
Output hotel_url has been added.
Output mealplan_description is now provided (extras=mealplans).
Output cheapest_breakfast_rate has been added (extras=add_cheapest_breakfast_rate).
It is now possible to filter for properties that can be booked without a credit card by using option=no_cc_filter.
Add license_number as a separate (extras=hotel_desctiption).
Add auto_tags to hotel_photos object and room_photos object (extras=hotel_photos,room_photos).
Output field bed_configurations has been added (extras=room_info).
Output key collection information has b
een added (extras=key_collection_info).
Hotel themes can now be provided in the output (extras=hotel_info).
Add price_local output field that represents the total reservation cost in local property's currency
Added to output:
Returns a list of rooms booked for each reservation.
Returns a breakdown of reservation charges.
New parameter guest_emails: accepts a comma-separated list of emails, similar to guest_names.
It is now possible to pull reviews in all available languages by passing all to the language parameter.
2-character inputs are now supported.
Ruids are now provided with all json responses, in order to be consistent with xml output.
Category IT & Programming
Subcategory Web development
What is the scope of the project? Medium-sized change
Is this a project or a position? Project
I currently have I have specifications
Required availability As needed
API Integrations Other (Other APIs)
Roles needed Developer
Deadline: July 12, 2020