# Migrating from V2 to V3 Endpoints **To migrate individual V2 endpoints, replace all calls to V2 endpoints in your application with their corresponding V3 equivalents. Follow the instructions below to ensure a smooth migration.** ## Verify key changes for each endpoint For each endpoint you migrate, ensure the following: * **HTTP Method & URL:** The V3 call uses the POST method and the correct endpoint URL. Refer to the [Endpoint structure](/demand/docs/migration-guide/v3/changes-in-v3) for details. * **Authentication**: The V3 call uses a valid [bearer token](/demand/docs/development-guide/authentication) for the appropriate API user. Ensure your token is up-to-date. * **Query parameters & response fields:** | | ✅ If a V2 parameter or field has a direct equivalent in V3, update your code to map it correctly. | | ✅ If a V2 parameter or field is not available in V3, modify your code to handle the absence of that data appropriately. | | ✅ Ensure that any other required V3 endpoints are called to fetch IDs or codes needed for requests or responses. | Important consideration Do not assume that mapped parameters or fields function identically between V2 and V3. The V3 API represents a significant redesign, and some behaviors may differ. Thoroughly consult the documentation, API references, and test your implementation to ensure correct migration. For more information see [V2 endpoints and their V3 equivalents](#v2-endpoints-and-their-v3-equivalents). * **Redirection URLs**: If your V2 endpoint provides a URL to redirect users (e.g., to Booking.com), ensure that the V3 response includes the correct affiliate ID for tracking and attribution. See Affiliate ID Tracking. * **Error handling**: Implement robust [error handling](//demand/docs/support/error-handling/about-errors) for every potential error the V3 endpoint may return. ## V2 endpoints and their V3 equivalents The table below outlines the V2 endpoints and their corresponding V3 equivalents, including links to: * The relevant API reference topic. * Migration guides for each endpoint, when available. Use these links to examine exactly how each V2 endpoint maps to its V3 equivalent. | V2 endpoint | V3 endpoint | | --- | --- | | **AVAILABILITY:** | | | [blockAvailability](https://developers.booking.com/api/technical.html?version=2.10#!/Availability/blockAvailability) | [/accommodations/availability](/demand/docs/open-api/demand-api/accommodations/accommodations/availability) | | [hotelAvailability](https://developers.booking.com/api/technical.html?version=2.10#!/Availability/hotelAvailability)See also: [V3 migration guide](/demand/docs/migration-guide/v3/hotelavailability-v3-migration-guide) | [/accommodations/search](/demand/docs/open-api/demand-api/accommodations/accommodations/search) | | **BOOKING:** | | | [bookingDetails](https://developers.booking.com/api/technical.html?version=2.10#!/Booking/bookingDetails) See also: [V3 migration guide](/demand/docs/migration-guide/v3/bookingdetails-v3-migration-guide) | [/orders/details](/demand/docs/open-api/demand-api/orders/orders/details)[/orders/details/accommodations](/demand/docs/open-api/demand-api/orders/orders/details/accommodations) | | [processBooking](https://developers.booking.com/api/technical.html?version=2.10#!/Booking/processBooking) | [/orders/preview](/demand/docs/open-api/demand-api/orders/orders/preview)[/orders/create](/demand/docs/open-api/demand-api/orders/orders/create) | | **REVIEWS:** | | | [reviews](https://developers.booking.com/api/technical.html?version=2.10#!/Reviews/reviews) | [/accommodations/reviews](/demand/docs/open-api/demand-api/accommodations/accommodations/reviews) | | [reviewScores](https://developers.booking.com/api/technical.html?version=2.10#!/Reviews/reviewScores) | [/accommodations/reviews/scores](/demand/docs/open-api/demand-api/accommodations/accommodations/reviews/scores) | | **STATIC:** | | | [autocomplete](https://developers.booking.com/api/technical.html?version=2.10#!/Static/autocomplete) | **Not available in V3** | | [chainTypes](https://developers.booking.com/api/technical.html?version=2.10#!/Static/chainTypes) | [/accommodations/chains](/demand/docs/open-api/demand-api/accommodations/accommodations/chains) | | [changedHotels](https://developers.booking.com/api/technical.html?version=2.10#!/Static/changedHotels) | [/accommodations/details/changes](/demand/docs/open-api/demand-api/accommodations/accommodations/details/changes) | | [cities](https://developers.booking.com/api/technical.html?version=2.10#!/Static/cities) | [/common/locations/cities](/demand/docs/open-api/demand-api/commonlocations/common/locations/cities) | | [countries](https://developers.booking.com/api/technical.html?version=2.10#!/Static/countries) | [/common/locations/countries](/demand/docs/open-api/demand-api/commonlocations/common/locations/countries) | | [districts](https://developers.booking.com/api/technical.html?version=2.10#!/Static/districts) | [/common/locations/districts](/demand/docs/open-api/demand-api/commonlocations/common/locations/districts) | | [facilityTypes](https://developers.booking.com/api/technical.html?version=2.10#!/Static/facilityTypes)[hotelFacilityTypes](https://developers.booking.com/api/technical.html?version=2.10#!/Static/hotelFacilityTypes)[hotelThemeTypes](https://developers.booking.com/api/technical.html?version=2.10#!/Static/hotelThemeTypes)[hotelTypes](https://developers.booking.com/api/technical.html?version=2.10#!/Static/hotelTypes)[paymentTypes](https://developers.booking.com/api/technical.html?version=2.10#!/Static/paymentTypes)[roomFacilityTypes](https://developers.booking.com/api/technical.html?version=2.10#!/Static/roomFacilityTypes)[roomTypes](https://developers.booking.com/api/technical.html?version=2.10#!/Static/roomTypes) | [/accommodations/constants](/demand/docs/open-api/demand-api/accommodations/accommodations/constants) | | [hotels](https://developers.booking.com/api/technical.html?version=2.10#!/Static/hotels)See also: [V3 migration guide](/demand/docs/migration-guide/v3/hotel-v3-migration-guide) | ​[/accommodations​/details](/demand/docs/open-api/demand-api/accommodations/accommodations/details) | | [regions](https://developers.booking.com/api/technical.html?version=2.10#!/Static/regions) | [/common/locations/regions](/demand/docs/open-api/demand-api/commonlocations/common/locations/regions) | Modifications in orders In V2 there were multiple endpoints to change reservations (example: canChangeHotelReservation) - In V3 you can use the [orders/modify endpoint](/demand/docs/open-api/demand-api/orders/orders/modify) to make these changes. ## Additional resources To help you navigate the V3 API and streamline your migration process, we recommend reviewing the following guidelines: * [Quick guide](/demand/docs/getting-started/try-out-the-api) – Overview of the full accommodations integration. * [Searching for accommodation](/demand/docs/accommodations/search-for-available-properties) - Details on searching for available properties (including use cases) * [Look at accommodation details](/demand/docs/accommodations/look-accommodation-details) – How to retrieve accommodation details. * [Pricing ](/demand/docs/accommodations/prices-accommodations)and [discounts](/demand/docs/accommodations/discounts) * [Orders](/demand/docs/orders-api/overview) and [Payments](/demand/docs/payments/overview) management. Support resources: * [Common errors](/demand/docs/support/error-handling/about-errors) - Troubleshooting and handling errors. * [Rate limiting](/demand/docs/development-guide/rate-limiting) - Best practices for dealing with rate limits. * [Filtering and sorting](/demand/docs/accommodations/filter-sorting) – How to filter and paginate responses.