Create your orders

Learn to create an order using the /orders/preview and /orders/create endpoints

To create an order, you must use the following endpoints in sequence:

Order creation process

Once a traveller selects their desired products, you can follow these steps to create the booking.

Step 1 - Call the /orders/preview

Use the /orders/preview endpoint to validate the order details before proceeding.

The request should be built using product and accommodation data returned in the previous step of your integration flow.

Define the request

Your /orders/preview request must include:

• booker, currency, accommodation.checkin and accommodation.checkout - Use the values from the previous response.

• accommodation.id and products - Use the values from the preceding response for the products selected by the traveller.

Guest allocation

If the booking includes multiple rooms, specify how guests are distributed using products.allocation.

Example: Booking two identical rooms, with one adult allocated to each:

{
  "products": [
    {
      "id": "1050736002_377311511_0_2_0",
      "number_of_adults": 1,
      "room": 1050736002
    },
    {
      "id": "1050736002_377311511_0_2_0",
      "number_of_adults": 1,
      "room": 1050736002
    }
  ]
}

Allocation data depends on your integration type:

Search and book

The products returned in the /accommodations/search endpoint response already include guest allocation.

Search, look and book flow

recommendation.products in the /accommodations/availability response includes guest allocation.

For example:

{
  "recommendation": {
    "products": [
      {
        "id": "1050736003_377312697_1_2_0",
        "number_of_adults": 1,
        "room": 1050736002
      },
      {
        "id": "1050736003_377312697_1_2_0",
        "number_of_adults": 1,
        "room": 1050736002
      }
    ]
  }
}

• For non-recommended products, check products.maximum_occupancy and assign guests manually.

Orders/preview response

A successful response from the /orders/preview endpoint includes:

• Accommodation-specific details:

  • Final price.

  • Supported payment timings and methods.

• Product-specific details:

  • Final product price (See Accommodation pricing guide for details and examples)

  • policies including cancellation fees and schedules, and meal plans.

• Order token.

  • Encapsulated order details needed for /orders/create request.

Note on payment object

Different products may support different payment timelines and methods.

The payment object in the preview includes only the methods and timings supported by all selected products.

Step 2 - Display the order preview page

Display the order details in the preview page so traveller can:

• Review the booking.

• Choose a payment method and timing.

• Provide guest and arrival information.

Example:

Step 3 - Call the /orders/create endpoint

Once the traveller confirms the booking, call /orders/create, with the order_token from the orders/preview response, and all required inputs.

Required fields

The /orders/create request requires the following fields:

Considerations about booker

Some fields under booker are conditionally required:

booker.address

• If /accommodations/details indicates booker_address_required=true, this field is mandatory. Otherwise, it is optional.
• All address subfields (address_line, city, country, and post_code) must be provided if used.

And other optional:

• booker.company: Use for B2B or invoicing.

Optional fields

These are not required to create the order but may help with additional use cases:

Receipt generation

Best practices for optional fields

Only provide optional fields if:

• They are relevant to your integration.

• They are required by your internal business logic.

• The endpoint or booking context explicitly requires them.

This helps minimise complexity and keeps your request payload lightweight and easier to manage.

Example - order/ create request

In this request, we have included the optional fields: products bed_configuration, remarks and receipt generation:

{
  "accommodation": {
    "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"
  }
}

Example - orders/create response

A successful response from /orders/create returns the following information about the order:

Example response

{
  "request_id": "01j69mtd91x3pdcmqyj0spebt9",
  "data": {
    "payment": {
      "receipt_url": "https://secure.booking.com/payment_receipt.html?product_type=BookingBudget&aid=2373042&auth_key=8riKJJ0XuxDhk4ds&lang=en",
      "authorisation_form_url": null
    },
    "accommodation": {
      "order": "5006302528200239",
      "pincode": "884512",
      "reservation": 55303962
    }
  }
}

Step 4 - Confirm the booking with the traveller.

Use the /orders/create data to:

• Display your order confirmation page.
• Notify the traveller that their booking has been confirmed.