Orders API collection – Migrating to v3.2

Overview of updates and breaking changes for all Orders endpoints in Demand API v3.2.

Introduction

This page highlights the key updates and breaking changes introduced in Demand API v3.2 in the Orders API collection.

Use it as a starting point before reviewing the endpoint-specific migration guides.

Who is this for

This migration overview is intended for developers and integration partners who consume any of the following Orders endpoints:

Endpoint	Integration
/orders/preview and /orders/create	For Accommodation and now Car rental bookings (in Beta)
/orders/details	For reporting systems, post-booking flows, CRM, billing and analytics for Accommodation, Cars, and now also Attractions (in Beta).
/orders/modify and orders/cancel	For Accommodation.

Summary of key changes

v3.2 introduces structural improvements, multi-travel service support, and new payment capabilities.

Here’s a summary of the most significant changes across the Orders API collection:

Key change	Description
✅ Multi-travel services support	Orders now cover multiple travel services (Accommodation, Car, and Attractions). Only one travel service can be included per request.
✅ Top-level order field	A new `data.order` field replaces `data.accommodation.order` for consistency across travel services.
✅ Payments	Extended functionality including `airplus`, `business_information`,`card`, `wallet`, `authorisation_form`, `3D secure`, `sca_exemption`. Optional `3d_secure` and `sca_exemption` fields are now formalised. `Include_receipt` remains optional. For `airplus`, `number` is required; `dbi` subfields are optional.
✅ Pricing and commission	Flat numeric fields replaced with structured, multi-currency fields (`currencies`, `commissionable_price`, `total_price`).
✅ Attribution and insights	New fields like label (for tracking car bookings) and `stay_probability` (in /orders/details).
✅ Deprecations	Several fields have been removed or replaced (see below).

Deprecated fields

Endpoint	Deprecated field	Replacement / Notes
/orders/create	`cavv` (card authentication in the request)	Removed in v3.2
/orders/details/accommodations	`accommodation.credit_slip` (in response)	Use `credit_slip_number` instead
All	`currency`, `commission.actual_amount`, `price.total`	Use multi-currency fields: `currencies`, `commissionable_price`, `total_price`

Endpoint-specific highlights

Endpoint	Key Updates
/orders/create	Accommodation or Car orders; new `car.driver` object; `order_token` unchanged. Car bookings are available in beta for pilot users.
/orders/preview	Multi-vertical availability; may include Car products.
/orders/details	`data.accommodation.order` removed; top-level `data.order` added; optional `data.car`.
/orders/modify	Accommodation modifications unchanged; Car orders beta for pilot users.

Migration recommendations

Schema inspection - Review v3.2 OpenAPI for all Orders endpoints.
Vertical handling - Implement logic for Accommodation or Car; update request generation.
Response parsing - Update integrations to check data.accommodation or data.car and top-level data.order.
Payment handling - Add support for airplus, business_information, and authorisation_form_url.
Testing & monitoring - Validate flows for both verticals; log request_id for troubleshooting.

Required:

Update your integration to support the new multi-currency fields and to stop relying on deprecated flat fields. Do this as soon as possible to ensure compatibility once v3.2 is enforced.

Summary

v3.2 introduces a unified, multi-vertical Orders structure with support for Accommodation, Car, and future product types such as Attractions. It adds a top-level order identifier, improved payment handling, stricter field validation, and more detailed price and commission structures.

Most existing integrations for accommodation-only flows will continue to work, but you must adapt to handle the new car vertical and response shape to remain fully compatible.

Need help?

If you have questions about your Orders integration migration, contact your Booking.com technical account manager.

By following these guidelines and making the required updates, you can smoothly transition to Demand API v3.2 and continue to provide a seamless booking experience for your travellers.

What's next

Refer to each endpoint migration guide for details:

3.2 Orders/preview migration

Learn how to migrate your Orders Preview integration from v3.1 to v3.2. Understand the new multi-vertical structure and key request and response changes.

3.2 Orders/create migration

Step-by-step guide to migrating from v3.1 to v3.2. Discover how to create both accommodation and car rental bookings (in Beta) using the new schema and validation rules.

3.2 Orders/details migration

Explore how to migrate to v3.2 and retrieve richer booking details for multiple verticals, including accommodation, filghts, cars, and attractions (in Beta).

3.2 Orders/details/accommodations migration

Explore how to migrate to v3.2 and retrieve richer booking details for accommodation.

3.2 Orders/details/cars migration

Explore how to migrate to v3.2 and retrieve richer booking details for cars.

3.2 Orders/modify migration

Learn how to migrate your modification flows to v3.2. Understand what's changed for accommodation modifications and how to prepare for upcoming car rental support.

3.2 Orders/cancel migration

Learn how to migrate your cancellation flows to v3.2. Understand what's changed for accommodation cancellation and how to prepare for upcoming car rental cancellation support.