# 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](/demand/docs/getting-started/overview) to familiarise yourself with the API’s architecture, verticals, and endpoint collections. |
| 2 | Explore endpoints | Use the [API Sandbox collection](/demand/docs/getting-started/try-out-the-api/) to experiment with requests and responses.* Review the detailed guides for [accommodation](/demand/docs/accommodations/about-accommodation), [car rental](/demand/docs/cars/overview), [Messaging API](/demand/docs/messaging/about-messaging) and [Attractions](/demand/docs/attractions/about-attractions).

 |
| 3 | Review key changes in v3.1 & v3.2 | Understand the overall [major design updates in v3.2](/demand/docs/migration-guide/v3.2/changes) 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.

## Previous versions

If you are interested in Demand API previous versions migration, see the [v3.1 Migration section](/demand/docs/migration-guide/v3/changes-in-v3).