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 for details.
Authentication: The V3 call uses a valid bearer token 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. |
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.
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 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.
In V2 there were multiple endpoints to change reservations (example: canChangeHotelReservation) - In V3 you can use the orders/modify endpoint 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 – Overview of the full accommodations integration.
- Searching for accommodation - Details on searching for available properties (including use cases)
- Look at accommodation details – How to retrieve accommodation details.
- Pricing and discounts
- Orders and Payments management.
Support resources:
- Common errors - Troubleshooting and handling errors.
- Rate limiting - Best practices for dealing with rate limits.
- Filtering and pagination – How to filter and paginate responses.