Migration guides

These guides are designed to help you migrate smoothly from older versions of the API to the latest stable or beta releases.

Introduction

Version 3.0 of the Demand API introduced a comprehensive redesign, improving both developer experience and application performance, while version 3.1 included new travel services (car rental and orders/details/flights) and new endpoints.

With Demand API version 3.2, the API continues to evolve, offering multi-vertical integrations, richer data structures, and more accurate reporting, as well as new features and endpoints.

Plan your migration

Before updating your integration, review the key version changes and prepare your systems for new structures and endpoints.

The following steps will help you understand what changed, explore updated documentation, and ensure a smooth transition.

Preparation steps for a smooth migration:

Step	Action	Description
1	Understand the Demand API	Review the Getting Started guide to familiarise yourself with the API’s architecture, verticals, and endpoint collections.
2	Explore endpoints	Use the API Sandbox collection to experiment with requests and responses. Review the detailed guides for accommodation, car rental, Messaging API and Attractions.
3	Review key changes in v3.1 & v3.2	Understand the overall major design updates in v3.2 including multi-currency support, structured pricing, and messaging enhancements.
4	Plan your migration	Map old fields to new structured fields, update data models, and prepare UI/reporting changes. Checking new verticals and endpoints (Messaging, Orders, Attractions) to reflect the expanded coverage. Ensure temporary backward compatibility for deprecated fields while planning their phase-out.
5	Validate & test	Perform end-to-end testing in Sandbox environments if possible. Verify multi-vertical scenarios (accommodation, cars, attractions) and confirm correct handling of fields like `commission`, `label` and `offer` for cars.

Migration recommendations

When upgrading from v3.1 → v3.2, review your integration for schema changes, deprecated fields, and new response structures.

Update your data models to adopt new structured fields and drop legacy flat numeric fields such as actual_amount, estimated_amount, multi currency, commissionable, total, as well as chargeable_online.
Support new verticals and endpoints — including Messaging and Orders — which introduce additional fields and nested objects for car rental bookings.
Ensure backward compatibility temporarily if needed, but plan to phase out deprecated fields and response shapes in future versions.
Test with realistic data using the test properties and sandbox environment if possible to confirm expected behaviour in accommodation and orders.

Choose your migration guide

Choose the guide relevant to your integration type.

After reviewing the overall changes, follow the travel service-specific endpoint guides to migrate each service individually.

3.2 Overall migration

Upgrade your integration from v3.1 to v3.2. Learn about structural updates across Messaging, Orders, and other new verticals.

3.2 Accommodation integration

Learn how to migrate accommodation endpoints from version 3.1 to version 3.2, with step-by-step guidance on updating your application flows.

3.2 Car rental integration

Migrate from Demand API car rental collection v3.1 to v3.2 – Explore the redesigned structure, new endpoints and integration flows.

3.2 Orders integration

Migrate from Demand API orders collection v3.1 to v3.2 – Explore the redesigned structure, endpoints and integration flows.

3.2 Beta Messaging

Migrate from Messaging API v3.1 to v3.2 – Note this endpoint is still under development and accessible only to restricted group of partners.

Previous versions