Use these guides to migrate your integration from an earlier Demand API version to the latest stable or Beta version.
The Demand API evolves through new travel services, endpoints, data structures, and integration capabilities.
- Demand API v3.1 introduced a major redesign of the API, while later versions expanded its travel services and integration capabilities.
- Demand API v3.2 and Beta introduce further changes to API structures, endpoints, reporting data, and supported integration flows.
Use these migration guides to identify the changes that affect your integration and understand the updates required when moving to a newer version.
Before updating your integration, review the changes for your target version and identify how they affect your existing application flows, data models, and dependencies.
Use the following steps to plan your migration.
| Step | Action | Description |
|---|---|---|
| 1 | Review the Demand API | Read the Getting Started guide to understand the API architecture, available travel services, integration flows, and endpoint collections. |
| 2 | Review your current integration | Identify the API version, travel services, endpoints, and integration flows currently used by your application. |
| 3 | Review the version changes | Select your target API version and review its migration overview. Identify changes to endpoints, schemas, fields, and integration flows that affect your application. |
| 4 | Follow the relevant migration guides | Review the migration guides for each travel service or API collection used by your integration and map existing fields and structures to their replacements. |
| 5 | Validate and test | Test the updated integration end to end. Where a sandbox environment is available, use it to validate requests, responses, error handling, and the scenarios supported by your application. |
When migrating to a newer API version:
✓ Review schema changes — Identify fields and objects that were added, changed, moved, or deprecated, and update your data models accordingly.
✓ Review endpoint changes — Check whether your existing endpoints have changed or whether new endpoints or integration flows replace existing functionality.
✓ Check deprecated functionality — If you temporarily support both old and new structures, plan to remove dependencies on deprecated fields and response formats.
✓ Review travel service-specific changes — Migration requirements can differ between travel services and API collections. Follow the relevant migration guide for each part of your integration.
✓ Test your integration end to end — Validate the scenarios supported by your application and confirm that requests, responses, errors, and downstream processing behave as expected.
A dedicated sandbox environment is currently not available for car rental integrations.
Demand API v3.2 introduces changes to API structures, endpoints, and integration flows across multiple travel services.
Review the Demand API v3.2 migration overview to understand the main changes, breaking changes, and functionality available in v3.2 and Beta.
If you already know which part of your integration you need to update, choose the relevant migration guide below.
Choose the travel service or API collection you want to migrate. Each guide explains the relevant changes and links to more detailed migration instructions where applicable.
Accommodation integration — v3.2
Migrate your accommodation integration from Demand API v3.1 to v3.2, with guidance on endpoint and response changes.
Car rental integration — v3.2 and Beta
Migrate your car rental integration from Demand API v3.1 or XML to v3.2, including updated endpoints, structures, and integration flows.
Orders integration — v3.2
Migrate your orders integration from Demand API v3.1 to v3.2, including changes to endpoints, request and response structures, and integration flows.
Messaging integration — Beta
Migrate your Messaging API integration from v3.1 to the v3.2 Beta. Access is currently restricted to eligible partners.
For guidance on earlier Demand API migrations, see the v3 migration guides.