Stay up to date with the latest enhancements to the Demand API.

This release includes updates to Demand API v3.2 and Beta across accommodations, attractions, and orders.

| v3.2 | New field | requires_request_to_book |

The requires_request_to_book field indicates whether an accommodation requires a booking request before it can be booked.

Available in:

• /accommodations/details

Example:

{
  "id": 10004,
  "requires_request_to_book": true
}

| Beta | Behaviour change | Omit booker.address for eligible cardless car orders|

For eligible pay-at-pickup car offers, you can omit booker.address from /orders/create when:

• credit_card_required is false.
• The accepted price has no online payment amounts.
• The payment object is also omitted.

Include booker.address for all other car orders.

Available in:

• /orders/create

| Beta | Behaviour change | Increase the date range |

The maximum /attractions/search date range (end_date − start_date) increases from 30 to 90 days, in line with the maximum accommodation length of stay of 90 days.

The end date of the availability period uses ISO 8601 date format (YYYY-MM-DD).

• It can be the same as start_date for single-day searches.
• It must be no more than 90 days after start_date and no more than 180 days in the future.

Available in:

• /attractions/search

v3.2 API reference

Check the 3.2 version specifications and give them a try in the console to return the new fields.

Check now

Beta API reference

Check the Beta API collections. You need specific credentials to test them out - Contact your Booking Account Manager if interested.

Check now