Use these guides to migrate your integration to a stable Demand API version or to a capability available in the generic Beta version.
The Demand API evolves through new travel services, endpoints, data structures, and integration capabilities.
Demand API v3.3 is the latest stable version and introduces new capabilities and breaking changes compared with v3.2.
The generic Beta version contains capabilities that are still under active development and may change before they become part of a stable version.
Some capabilities that were previously available in 3.2 Beta may now be included in both v3.2 stable and v3.3 stable, or just in v3.3. See the Versioning strategy for details.
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 your current integration | Identify the API version, travel services, endpoints, and integration flows currently used by your application. |
| 2 | Select your target version | Choose whether to migrate to v3.3, continue using v3.2, or integrate a capability available in the generic Beta version. |
| 3 | Review the version changes | Read the migration overview for your target version and 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.
Demand API v3.3 is the latest stable version. It introduces new capabilities and breaking changes across multiple travel services and API collections.
For a summary of the release, see the Demand API v3.3 migration overview.
If you are migrating from the 3.2 Beta version, use the v3.3 migration guides to review any changes required for the stable implementation.
Capabilities promoted from 3.2 Beta are now available in the stable API and should be implemented through v3.2 or v3.3 stable, rather than through the generic Beta version.
Attractions capabilities previously available in 3.2 Beta are now available in the stable versions of v3.2 and v3.3. Existing integrations can move to either stable version.
See the Demand API v3.3 migration overview for details.
Choose the travel service or API collection you want to migrate.
Demand API v3.3 migration overview
Review the main changes, breaking changes, and capability availability introduced in Demand API v3.3.
Accommodation integration — v3.3
Migrate your accommodation integration to v3.3, including changes to endpoints, structures, and integration flows.
Car rental integration — v3.3
Migrate your car rental integration to v3.3, including changes to search, booking, post-booking, invoicing, and response structures.
Orders integration — v3.3
Migrate your Orders integration to v3.3, including changes to endpoints, request and response structures, and integration flows.
Demand API v3.2 remains available as a stable version.
Use the Demand API v3.2 migration overview to review the main changes, breaking changes, and capabilities available in v3.2 stable.
The v3.2 migration overview reflects the current availability of capabilities after the v3.3 launch.
Capabilities previously available in 3.2 Beta that have been promoted to stable are now documented as part of v3.2 Stable.
The generic Beta version contains capabilities that are still under active development. Beta functionality may change before becoming available in a stable API version, including changes to schemas, fields, endpoints, and supported integration flows.
Review the generic Beta API reference and confirm that your account has access before implementing a Beta capability.
For guidance on earlier Demand API migrations, see the v3 migration guides.