Demand API version 3.2 introduces several improvements and breaking changes from version 3.1, including updates to accommodation booking flows, inclusion of Attractions in orders/details for post-booking reporting and other structural enhancements.
- The API follows REST principles and returns data in JSON format.
- You can access endpoints via HTTPS POST requests.
Authentication: Use your Affiliate ID and token credentials to use these endpoints.
Try it out!
Provides generic payment-related identifiers, including supported currency codes, payment cards, and relevant metadata for booking flows.
- Use the returned identifiers when constructing requests across all travel services API collections, including both accommodation and car rental endpoints.
Use this endpoint to calculate the final price, price breakdown, payment schedules, and cancellation policies for accommodation products. * Provide the booker's details and currency to receive personalised pricing. * For accommodations, include checkin/checkout dates, room allocations, and selected products.
Additional information related to the car order. This field is mutually exclusive with accommodation; only one of them can be included in a request.
A three-letter code that uniquely identifies a monetary currency as defined by the ISO 4217 standard. The full list can be obtained by calling common/payments/currencies.
curl -i -X POST \
https://demandapi.booking.com/3.2/orders/preview \
-H 'Authorization: Bearer <YOUR_string_HERE>' \
-H 'Content-Type: application/json' \
-H 'X-Affiliate-Id: 0' \
-d '{
"currency": "EUR",
"accommodation": {
"id": 6745031,
"booker": {
"country": "nl",
"platform": "mobile",
"travel_purpose": "leisure",
"user_groups": [
"authenticated"
]
},
"checkin": "!START_DATE!",
"checkout": "!END_DATE!",
"products": [
{
"id": "674503106_275710478_0_2_0",
"allocation": {
"number_of_adults": 1,
"children": [
8
]
}
},
{
"id": "674503113_275710486_0_1_0",
"allocation": {
"number_of_adults": 1,
"children": []
}
}
]
}
}'{ "request_id": "01fr9ez700exycb98w90w5r9sh", "data": { "accommodation": { … }, "order_token": "..." } }
Additional information related to the accommodation order. This field is mutually exclusive with car; only one of them can be included in a request.
The booker's information.
The booker's address to be used for creating this order. All fields of this object are required if the /accommodations/details endpoint indicates that the booker's address is necessary by returning booker_address_required=true.
A IETF language tag code that uniquely identifies a supported human language or dialect. Note: Demand API only accepts lowercase for the language codes. Examples: "nl" for Dutch/Nederlands or "en-us" for English (US). The full list can be obtained by calling common/languages.
The name of the booker.
Payment related information for the order.
All information related to airplus payment. This is required if airplus is selected as payment method.
All business related information for billing and authorisation form. This must be included for the payments that require authorisation form.
This is used to determine whether to include payment receipt_url in the response or not.
curl -i -X POST \
https://demandapi.booking.com/3.2/orders/create \
-H 'Authorization: Bearer <YOUR_string_HERE>' \
-H 'Content-Type: application/json' \
-H 'X-Affiliate-Id: 0' \
-d '{
"accommodation": {
"label": "Sample label",
"products": [
{
"id": "333",
"bed_configuration": "123456",
"guests": [
{
"email": "test.name@booking.com",
"name": "Test Name"
}
]
}
],
"remarks": {
"estimated_arrival_time": {
"hour": 12
},
"special_requests": "We will need an extra cot."
}
},
"booker": {
"address": {
"address_line": "Road-1, house-2",
"city": "Amsterdam",
"country": "nl",
"post_code": "11111"
},
"company": "Booking B.V",
"email": "test.name@booking.com",
"language": "en-gb",
"name": {
"first_name": "Test",
"last_name": "Name"
},
"telephone": "12345678"
},
"order_token": "sample-token",
"payment": {
"card": {
"cardholder": "Test Name",
"cvc": "111",
"expiry_date": "2030-10",
"number": "23333333333333"
},
"include_receipt": true,
"method": "card",
"timing": "pay_at_the_property"
}
}'{ "request_id": "01fr9ez700exycb98w90w5r9sh", "order": "509430129718799", "data": { "accommodation": { … }, "payment": { … } } }
Use this endpoint to retrieve detailed information about existing orders based on a specific filter or identifier. You can query orders by: - Creation or update date – retrieve orders created or updated within a specified time range (up to 7 days). - Stay or car rental dates – retrieve orders by travel start or end date. - Order or reservation IDs – fetch details for specific orders or reservations. The response includes essential order information such as order ID, status, service type, and price.
The returned information is especially useful for syncing your system with Booking.com order data, monitoring updates, and reporting across services (accommodations, cars, flights, and attractions).
Filtering orders by time range on basis of order "created" or "updated" time. Maximum time range is 7 days (1 week).
ISO 8601 timestamp in UTC, which indicates the timestamp from which you want to filter orders from (inclusive). The value should be within last 1 year.
A three-letter code that uniquely identifies a monetary currency as defined by the ISO 4217 standard. The full list can be obtained by calling common/payments/currencies.
The maximum number of results to return.
Input parameter to request for additional information about this order.
curl -i -X POST \
https://demandapi.booking.com/3.2/orders/details \
-H 'Authorization: Bearer <YOUR_string_HERE>' \
-H 'Content-Type: application/json' \
-H 'X-Affiliate-Id: 0' \
-d '{
"created": {
"from": "2025-08-28T02:00:00+00:00",
"to": "2025-08-31T02:00:00+00:00"
},
"currency": "EUR",
"maximum_results": 20,
"sort": {
"by": "updated",
"direction": "descending"
},
"extras": [
"payment"
]
}'{ "request_id": "01fr9ez700exycb98w90w5r9sh", "data": [ { … } ], "metadata": { "next_page": null, "total_results": 1 } }