Demand API v3.2 migration overview

Understand the main changes introduced in Demand API v3.2 and Beta, identify the changes that affect your integration, and choose the relevant migration guide.

Demand API v3.2 introduces more consistent structures across travel services and expands the API with additional capabilities and integration flows.

Key v3.2 changes include:

• More consistent data structures for pricing, charges, currencies, inventory, and identifiers.
• Updated accommodation flows, including changes to availability, pricing, room identification, inventory, and reporting.
• Expanded Orders capabilities to support multiple travel services and more detailed reporting and reconciliation data.

Demand API Beta introduces additional capabilities, including:

• Expanded car rental capabilities, including search, availability, direct booking, and selected post-booking capabilities.
• Messaging updates including changes to conversations, messages, attachments, and request validation.
• Attractions support for selected integration and reporting flows.

Not all functionality covered by these migration guides has the same release status.

Before migrating, check whether the functionality required by your integration is available in v3.2 or Beta.

Demand API v3.2 introduces changes across accommodation search, availability, details, and booking flows so you can implement all the Integration flows including booking capabilities.

Key changes include:

• Merged availability flows.
• Updated pricing and charges structures.
• Improved room identification.
• A unified inventory model for first-party and third-party rates.
• Additional accommodation information for reporting and reconciliation.
• Support for Cancel for Less.

The Orders API collection includes expanded structures for order management, post-booking tasks, reporting, and financial reconciliation.

Key changes include:

• More detailed pricing, charges, and tax information.
• Updated currency structures.
• Support for reservations from multiple travel services.
• Updated cancellation and partially refundable information.
• Additional fields for reporting and financial reconciliation.

Demand API Beta extends the car rental integration with direct booking and selected post-booking capabilities.

Beta functionality includes:

• Real-time car availability validation.
• Pre-booking terms and conditions.
• Order preview and creation.
• Order cancellation.
• Car reservation details and selected post-booking information.

Demand API Beta introduces changes to the Messaging API data model and request validation.

Key changes include:

• Standardised conversation and participant structures.
• A unified message identifier.
• Updated attachment handling.
• Updated request validation requirements.
• Improved message confirmation tracking.

Demand API Beta introduces Attractions as an additional travel service, with product information for Content only and Search, look and redirect integrations.

Attraction reservations can also be represented in order details alongside other supported travel services.

Some v3.2 and Beta changes require updates to existing integrations.

Review the migration guide for each travel service or API collection used by your integration before updating your implementation.

Demand API v3.2 introduces a unified inventory model across accommodation search, availability, and booking flows.

The third_party_inventory field used in v3.1 is removed. Inventory information is provided through the inventory object.

{
  "inventory": {
    "third_party": true,
    "type": "net"
  }
}

Update integrations that use third_party_inventory to:

• Use inventory.third_party to identify third-party inventory.
• Use inventory.type to identify the pricing model.

This change affects:

• /accommodations/search
• /accommodations/availability
• /orders/preview

Pricing and currency structures have also changed in v3.2.

Depending on the endpoint, you may need to update how your integration handles:

• Price breakdowns.
• Charges.
• Display and total prices.
• Multiple currencies.
• Conditional or online-payable charges.

See the relevant Accommodation or Orders migration guide for endpoint-specific changes.

Orders responses contain additional structures to support multiple travel services, reporting, and financial reconciliation.

If you consume order details, review changes to:

• Reservation structures.
• Pricing and charges.
• Currency.
• Cancellation information.
• Travel service-specific order details.

The Messaging API Beta introduces changes to conversation and message structures.

If you use Messaging API v3.1, review changes to:

• Conversation identifiers.
• Participants and senders.
• Message identifiers.
• Reply handling.
• Attachments.
• Request validation.
• Message confirmation.

Before updating your integration:

1. Identify the travel services and API collections you use — Follow only the migration guides relevant to your integration.
2. Review breaking changes — Check endpoint, field, enum, and schema changes before updating your data models.
3. Update your application flows — Account for endpoints that have been added, replaced, merged, or changed.
4. Update your data models — Map existing v3.1 or XML structures to their v3.2 or Beta equivalents.
5. Review Beta dependencies — Confirm the availability and access requirements of Beta functionality before depending on it.
6. Validate the complete integration flow — Test requests, responses, error handling, and downstream processing before releasing your updated integration.

Choose the travel service or API collection you want to migrate. Each guide provides detailed migration instructions for the relevant endpoints and schemas.