Find here a comprehensive history of all updates, improvements, and bug fixes across versions.

Each entry provides a detailed log of changes made to Demand API, including new features, enhancements, and any resolved issues, divided by endpoints and/ or travel services.

This archive serves as a valuable resource for understanding the evolution of the product over time and tracking its progress.

This release focuses on Demand API version 3.2 and 3.2 Beta, with updates across attractions, accommodations and orders:

| 3.2 Beta | New endpoint: /attractions/constants |

A new endpoint is available to retrieve static metadata used in attractions search flows. It is designed to be cached client-side for performance optimisation.

Purpose – Supports richer discovery experiences by:

• Providing category and subcategory identifiers.
• Supporting category-based filtering in /attractions/search.

Available in:

• /attractions/constants

| 3.2 Beta | New field: booker.country |

The booker.country field is now required in Car rental post-booking endpoints (Beta): orders/cancel and orders/details/cars/live

Purpose – Improves accuracy of:

• Pricing calculations.
• Policy enforcement.
• Supplier-specific rules.

| 3.2 Beta | Sandbox behaviour: 403 error for unsupported endpoints |

Car rental order creation and cancellation are not available in the sandbox environment.

Behaviour:

When using the sandbox environment, the following endpoints for car rentals return now a 403 error:

• /orders/create
• /orders/cancel

Purpose – Prevents unsupported car rental order operations in sandbox and ensures correct usage of the production environment for end-to-end testing.

Error response:

{
  "request_id": "01kjan7r7yvff5yg95gxy1cjhy",
  "errors": [
    {
      "id": "sandbox_blocked",
      "message": "The /orders/create endpoint for cars is not available in the sandbox. Use the production environment instead."
    }
  ]
}

| v3.2 | cancellation schedule completeness |

The cancellation schedule now includes the no-show stage (post check-in) fees in accommodations/search, /accommodations/availability, and /orders/preview responses.

Purpose – Ensures the full cancellation cost timeline is available earlier in the booking flow, without requiring a call to /orders/details.

The schedule now includes:

• Free cancellation period.
• Partial penalty period(s).
• No-show stage (from check-in date, typically 100% charge).

Example:

"policies": {
  "cancellation": {
    "free_cancellation_until": "2026-01-28T22:59:59+00:00",
    "schedule": [
      {
        "from": "now",
        "price": 0.0
      },
      {
        "from": "2026-01-28T23:00:00+00:00",
        "price": 4.05
      },
      {
        "from": "checkin date",
        "price": 8.10
      }
    ],
    "type": "free_cancellation"
  }
}

This release focuses on Demand API version 3.2 and 3.2 Beta, with significant updates across car rentals and orders:

| v3.2 3.2 Beta | New field: insurance |

The new insurance object under each product in the cars response provides information about any optional insurance traveller can book for the rental.

• Only present when configured for the partner.
• null if not available.

Available in:

• /cars/search
• /cars/availability
• /orders/preview

Example in search response:

"insurance": {
  "name": "Full Protection",
  "id": "999",
  "price": {
    "amount": 144.70,
    "currency": "EUR"
  }
}

| v3.2 3.2 Beta | New field: cars.payment.timing in orders/details |

Payment timing information is now available in the orders/details response under cars.payment.timing.

Purpose – It indicates when the traveller is expected to pay for the car rental order, enabling better post-booking experiences and financial workflows.

Possible payment timing for cars:

• pay_online_now – Paid at booking time.
• pay_at_pickup – Paid locally at pickup.
• unknown – Timing could not be determined.

Example response:

{
  "cars": {
    "payment": {
      "timing": "pay_at_pickup"
    }
  }
}

| v3.2 3.2 Beta | Behaviour change |

The default number of car search results returned by the /cars/search endpoint has been increased.

Purpose – Provides more comprehensive search results without requiring clients to set a custom limit.

• Default results increased from 100 to 500.
• Supports richer search experiences for travellers and applications.
• May affect response size and pagination behaviour.

| 3.2 Beta | New filter: categories in attractions/search |

The categories filter allows you to refine search results by one or more attraction category IDs.

Purpose – Enables more relevant and targeted search experiences by returning only attractions that match at least one of the selected categories.

Supported categories include:

• Tours
• Services and rentals.
• Workshops and classes.
• Museums, arts and culture.
• Nature and outdoor.
• Entertainment and tickets.
• Food and drink.

Available in:

• /attractions/search

| v3.2 3.2 Beta | Car order cancellations supported |

Apart from accommodation, orders/cancel endpoint supports now car rental cancellations.

Example request:

{
  "car": {
    "reservation": "1234567890",
    "reason": "My travel plans have changed and I no longer need this car rental.",
    "booker": {
      "country": "nl"
    }
  }
}

| 3.2 Beta | New endpoint: /orders/modify/preview |

A new endpoint is available to preview order modifications before applying them.

Purpose – It allows you to validate whether a modification can be applied and understand its impact before confirming the change.

• Helps prevent failed modification attempts by checking eligibility upfront.
• Enables displaying updated pricing to travellers before confirming changes.
• Supports safer UX flows for post-booking modifications.

Behaviour:

• Returns modifiable: true if the change can be applied.
• Returns modifiable: false with a reason when the modification is not allowed.

For accommodation date changes, returns a price object with:

• current – price before modification.
• new – price after modification.

Example request:

{
  "order": "6520081014",
  "modification": {
    "accommodation": {
      "reservation": "6187285715",
      "type": "dates",
      "change": {
        "checkin": "2026-04-19",
        "checkout": "2026-04-21"
      }
    }
  }
}

Example response:

{
  "data": {
    "modifiable": true,
    "price": {
      "currency": "EUR",
      "current": {
        "amount": 120.00
      },
      "new": {
        "amount": 150.00
      }
    }
  }
}

| v3.2 v3.1 | New field: occupancy_mismatch |

The new occupancy_mismatch warning object is included in the orders/preview endpoint response.

Purpose - It Indicates when the requested guest allocation exceeds the product’s maximum occupancy.

• It helps partners display a clear warning to the traveller or decide whether to allow the booking to proceed.

Behaviour – If the allocation fits the product capacity, occupancy_mismatch is null. Otherwise, it provides a breakdown of:

• allocated – guests that can be accommodated in the room.
• unallocated – guests that cannot be accommodated.

Example request:

{
  "occupancy_mismatch": {
    "allocated": {
      "number_of_adults": 1,
      "children": null
    },
    "unallocated": {
      "number_of_adults": 1,
      "children": null
    }
  }
}

This release focuses on Demand API version 3.2 and 3.2 Beta, with significant updates across car rentals and orders:

| v3.2 3.2 Beta | New field: credit_card_required |

The new credit_card_required boolean under the price response, indicates whether a credit card is required as a guarantee for pay_at_pickup vehicles.

• true - Credit card required and passed to supplier.
• false- Credit card explicitly not required.
• null - Information not available or not applicable.

Available in:

• /cars/search
• /cars/availability

| v3.2 3.2 Beta | New field: special_offer |

Returns any promotional or free upgrade features provided by the supplier for a vehicle, including: gps, priority pick up, wifi device, upgrade, one additional driver, etc.

Available in:

• /cars/search
• /cars/availability
• /cars/constants

Example in constants response:

"special_offers": [
    {
    "id": "one_additional_driver",
    "name": {
    "de": "1 zusätzlicher Fahrer inbegriffen",
    "en-gb": "1 additional driver included"
    }
    },
    {
    "id": "two_additional_drivers",
    "name": {
    "de": "2 zusätzliche Fahrer inbegriffen",
    "en-gb": "2 additional drivers included"
    }
]

| v3.2 3.2 Beta | New field: customer_services |

/cars/constants returns now customer service email addresses per requested language.

Example request:

{
"constants": ["customer_services"],
"languages": [
    "en-gb",
    "fr"

  ]
}

Example response:

{
  "request_id": "01kja15bmhz3s8xfe1knejce3x",
  "data": {
    "customer_services": [
      {
        "id": "email",
        "name": {
          "fr": "customer.service-fr@cars.booking.com",
          "en-gb": "customer.service@cars.booking.com"
        }
      }
    ]
  }
}

| 3.2 Beta | New field: voucher filter |

Use the voucher boolean filter in orders/details/cars/terms-and-conditions to receive only the subset of terms required for the booking voucher.

• true - Only the terms needed to recreate the booking voucher content shown on Booking.com are returned.
• false (or not provided) - Full set of agreed terms and conditions is returned.

Example of request:

{
  "booker": {
    "country": "gb"
  },
  "language": "en-gb",
  "orders": [
    "765255700"
  ],
  "filters": {
    "voucher": true
  }
}

| v3.2 | New field: authentication_response |

The new authentication_response is an optional field included in the orders/create endpoint, under payment.card.authentication.3d_secure object. It represents the 3D Secure transaction status (transStatus) returned by the 3DS provider.

• Purpose - It maps to the transStatus codes to confirm the status of the authentication transaction (Y: authentication successful, N: Authentication failed, etc.)
• Requirement - It is optional. Partners should only include it if their provider returns it or if a 3DS challenge flow occurred. It is not required if no challenge occurred.

Example request:

"payment": {
  "card": {
    "authentication": {
      "3d_secure": {
        "authentication_value": "AAABBBCCC123=",
        "eci": "05",
        "transaction": "abc123xyz",
        "authentication_response": "Y"
      }
    }
  }
}

| v3.2 3.2 Beta | New field: subtype |

The subtype field is included in the orders/create endpoint under payment.card

• This is used to identify cards that belong to supported special or co-branded programmes (currently only unionpay_cobrand)
• It ensures that the payment is routed correctly when the card network cannot be reliably determined by the card number (PAN) alone.

Example request:

  "payment": {
    "card": {
      "cardholder": "Test Name",
      "cvc": "111",
      "expiry_date": "2030-10",
      "number": "23333333333333",
      "subtype": "unionpay_cobrand"
    },

This release brings mainly updates to Demand API version 3.2 Beta being car rentals the main focus:

| 3.1 | New | Bundles and value added services |

• Bundles and value added services are automatically available across accommodation and orders endpoints.
• However for version 3.1 you must include extras.include_bundle_variants in the availability request.
• This ensures the response includes all bookable products with bundles, instead of returning only non-bundled products.

| 3.2 Beta | Replace “Prepayment” field in cars/availability |

The prepayment field under price has been replaced by the new price structure that includes the unit_amount, display and pay.
This aligns the response with the cars/search data model.

Before:

{
  "price": {
    "amount": 33.98,
    "prepayment": false
  }
}

After:

{
  "price": {
    "unit_amount": {
      "display": {
        "value": 33.98,
        "currency": "GBP"
      },
      "pay": {
        "value": 33.98,
        "currency": "GBP",
        "timing": "pay_at_pickup"
      }
    }
  }
}

| 3.2 Beta | Bug fix – depot IDs in cars/availability |

The depot IDs returned in the /3.2/cars/search response and depotID returned in the /3.2/cars/availability endpoint were different values.

• /cars/availability was returning the Location ID of the depot incorrectly. To fix this inconsistency, both endpoints now return the route object, that includes the same depot IDs as in /cars/search.

Before:

{
  "depot": 38566
}

After:

    "route": {
      "dropoff": {
        "depot": 14443,
        "depot_location_type": "shuttle_bus"
      },
      "pickup": {
        "depot": 14443,
        "depot_location_type": "shuttle_bus"
      }
    }

| 3.1 | v3.2 | "Label" supported for Third-Party Inventory (TPI) products |

• The existing label field is now also populated for properties with third-party inventory (TPI) rates in Demand API order responses.
• Endpoints impacted:
  • /orders/details
  • /orders/details/accommodation
  • /orders/create

What this means

• Partners can apply a single label taxonomy across both Booking.com-sourced and third-party inventory.
• Labels can be used to attribute bookings to specific TPI providers, programmes, or commercial constructs.

This improves post-booking reporting and reconciliation for mixed inventory portfolios that combine Booking.com and TPI rates.

Example orders/details response:

{
  "request_id": "01k9exampletpi0000000000000",
  "data": [
    {
      "id": "509430129718799",
      "accommodation": 123456,
      "third_party_inventory": true,
      "inventory": {
        "third_party": true,
        "type": "sell"
      },
      "label": "tpi-partner-x"
    }
  ]
}

| v3.2 | "Taxis" available in orders/details |

The /orders/details endpoint now supports taxi orders. You can retrieve detailed information about taxi bookings alongside other travel services such as accommodations, cars, flights, and attractions.

What’s included per taxi leg:

• Pickup and dropoff locations (address, city, country)
• Start and end date-time.
• Leg identifier.
• Reservation identifier (shared across legs in the same taxi order).
• Leg-level status.
• Currencies.
• Leg-level commission.
• Leg-level price (total and commissionable)
• Created and updated timestamps.

Example orders/details response (minimal):

{
  "request_id": "01htaxi9ez700example",
  "data": [
    {
      "id": "880045112233",
      "affiliate": 111111,
      "taxis": [
        {
          "leg": "607244787653565",
          "reservation": "916957580",
          "status": "booked",
          "start": "2026-03-10T08:00:00Z",
          "end": "2026-03-10T09:00:00Z",
          "pickup_location": { "city": "Amsterdam", "country": "nl" },
          "dropoff_location": { "city": "Utrecht", "country": "nl" },
          "price": {
            "total": { "booker_currency": 50.0, "product_currency": 50.0 }
          }
        }
      ],
      "start": "2026-03-10T08:00:00Z",
      "end": "2026-03-10T09:00:00Z",
      "status": "booked",
      "currencies": { "booker": "EUR", "product": "EUR" }
    }
  ],
  "metadata": { "next_page": null, "total_results": 1 }
}

| 3.2 Beta | New | New endpoint: orders/details/cars/live |

• The orders/details/cars/live endpoint provides enriched, live car order details, including driver information, supplier, pricing breakdown, payment timing, and operational pick-up/drop-off instructions.
• Currently, requests are limited to a single reservation ID.

Example response:

{
  "request_id": "123456789",
  "data": {
    "reservation_id": "ABC123",
    "driver": { "name": "John Doe", "age": 35 },
    "supplier": { "id": 3486, "name": "Premium Cars" },
    "price": {
      "unit_amount": { "display": { "value": 150, "currency": "EUR" }, "pay": { "value": 150, "currency": "EUR", "timing": "pay_online_now" } },
      "total_amount": { "display": { "value": 180, "currency": "EUR" }, "pay": { "value": 180, "currency": "EUR", "timing": "pay_online_now" } }
    },
    "route": {
      "pickup": { "depot": 243816, "depot_location_type": "meet_greet" },
      "dropoff": { "depot": 243816, "depot_location_type": "meet_greet" }
    }
  }
}

| 3.2 Beta | Removal of “Prepayment” field in orders/preview |

The prepayment field under the price object is no longer needed, as payment timing is already included in price.

Before:

     "products": [
          {
            "id": "10000000006012",
            "type": "baby_seat",
            "selected_quantity": 1,
            "mode": "per_rental",
            "price": {
              "unit_amount": {
                "display": {
                  "value": 25,
                  "currency": "EUR"
                },
                "pay": {
                  "value": 25,
                  "currency": "EUR",
                  "timing": "pay_online_now"
                }
              },
              "total_amount": {
                "display": {
                  "value": 25,
                  "currency": "EUR"
                },
                "pay": {
                  "value": 25,
                  "currency": "EUR",
                  "timing": "pay_online_now"
                }
              },
              "prepayment": true
            }
          },

After:

 "products": [
          {
            "id": "10000000006012",
            "type": "baby_seat",
            "selected_quantity": 1,
            "mode": "per_rental",
            "price": {
              "unit_amount": {
                "display": {
                  "value": 25,
                  "currency": "EUR"
                },
                "pay": {
                  "value": 25,
                  "currency": "EUR",
                  "timing": "pay_online_now"
                }
              },
              "total_amount": {
                "display": {
                  "value": 25,
                  "currency": "EUR"
                },
                "pay": {
                  "value": 25,
                  "currency": "EUR",
                  "timing": "pay_online_now"
                }
              },