Run order reports

Copy

• Copy for LLM

  Copy page as Markdown for LLMs
• View as Markdown

  Open this page as Markdown
• Open in ChatGPT

  Get insights from ChatGPT
• Open in Claude

  Get insights from Claude
• Connect to Cursor

  Install MCP server on Cursor
• Connect to VS Code

  Install MCP server on VS Code

Use the /orders/details endpoint to retrieve detailed information for existing orders across all travel services — including accommodations, cars, flights, attractions and taxis. It provides a single consolidated data source for financial reporting and reconciliation, without needing to query multiple endpoints.

/orders/details/

The orders/details endpoint enables:

• Financial reconciliation and reporting.
• Attribution tracking and analysis.
• Operational monitoring and system synchronisation from a single data source, without needing to combine responses from multiple service-specific endpoints.

It returns consolidated order data across travel services, including:

• Pricing and totals.
• Payment details and transaction status.
• Commissions and attribution data.
• Loyalty rewards (where applicable)
• Service-specific booking details.

Use cases

You can use this endpoint to:

You can retrieve orders by providing order IDs, reservation IDs, or supported date range filters, and receive a unified response structure across services.

How it works

Call the orders/details endpoint using one of the supported filter types.

Supported filters

Required fields

• All requests require:
  • currency — three-letter ISO 4217 code (e.g. EUR, USD)
• Exception - page requests do not require currency.

Optional fields

You can also include:

• extras — Request additional information (Currently supports payment)
• services — Limit results to selected travel services.
• maximum_results — Limit the number of results returned.
• sort.by and sort.direction — Sort results by creation or update date and specify the direction (ascending/descending).

Examples

Retrieve order details by reservation IDs

Scenario: Retrieve details for specific reservations to verify payment and commission.

{
  "currency": "EUR",
  "reservations": [
    "2321873123",
    "4666773123"
  ],
  "sort": {
    "by": "updated",
    "direction": "descending"
  },
  "extras": [
    "payment"
  ]
}

Retrieve all orders created within a date range

Scenario: Get all new orders for cars and accommodations created between 1 and 7 December 2025 to sync with an internal Customer Relationship Management tool (CRM).

{
    "created": {
      "from": "2025-12-01T02:00:00+00:00",
      "to": "2025-12-07T02:00:00+00:00"
    },
    "currency": "EUR",
    "maximum_results": 20,
    "sort": {
      "by": "updated",
      "direction": "descending"
    },
    "services": ["cars", "accommodations"],
    "extras": [
      "payment"
    ]
  }

Syncing order data

To build incremental sync logic for regularly updating systems:

• Use created.from and created.to retrieve newly created orders.
• Use the updated filter with small rolling windows (e.g. every 30–60 minutes) to keep your system in sync with Booking.com changes.

Response structure overview

The API returns matching orders in a standardised response format. Each order object includes:

Payment details

The payment object is returned only when requested via extras=["payment"].

It includes:

• method → airplus, card, wallet.
• timing → pay_at_the_property, pay_online_later, pay_online_now for accommodation.
• paid → completed transactions.
• pending→ upcoming or scheduled transactions.

Accommodation payments may also include:

• authorisation_form
• receipt_url

(See the [Payments section](/demand/docs/payments/overview for details)

Travel service details

Each order may include multiple services if booked together. Each service block (accommodations, cars, flights, attractions, taxis) is returned as:

• An object if present.
• null if the service has not been booked as part of the order.

Supported travel services

Key travel service fields

A reservation ID identifies each travel service that is part of the order.

• Each order may have different reservation IDs if multiple services are booked (for example, accommodation and car rental).
• This field is required for cancellations or customer service enquiries.

Minimal response example

{
  "request_id": "req_123",
  "data": [
    {
      "id": "880045112233",
      "affiliate": 111111,
      "status": "booked",
      "start": "2026-03-10T08:00:00Z",
      "end": "2026-03-12T10:00:00Z",
      "currencies": {
        "booker": "EUR",
        "product": "EUR"
      },
      "price": {
        "total_price": {
          "booker_currency": 420,
          "product_currency": 420
        }
      },
      "accommodations": {
          "reservation": "ABC123"
        }
    }
  ],
  "metadata": {
    "next_page": null,
    "total_results": 1
  }
}

Example – Attraction reservation details (v3.2)

{
  "order_id": "509430129718801",
  "attractions": {
    "reservation": 567890123,
    "name": "Eiffel Tower Guided Tour",
    "location": {"city": "Paris", "country": "fr"}
  },
  "affiliate": 111111,
  "booker": {
    "address": {"city": "Amsterdam", "country": "nl"},
    "email": "janedoe@booking.com",
    "name": {"first_name": "Jane", "last_name": "Doe"},
    "platform": "desktop",
    "telephone": "+100000001",
    "language": "en-gb",
    "travel_purpose": "leisure"
  },
  "commission": {"actual_commission_amount": {"booker_currency": 5.0, "product_currency": 6.0}},
  "currencies": {"booker": "EUR", "product": "EUR"},
  "price": {"commissionable_price": {"booker_currency": 50, "product_currency": 60}, "total_price": {"booker_currency": 55, "product_currency": 66}},
  "status": "booked",
  "start": "2026-07-10T09:00:00+00:00",
  "end": "2026-07-10T12:00:00+00:00",
  "created": "2025-11-28T02:00:00+00:00",
  "updated": "2025-11-28T02:00:00+00:00"
}

Example – Taxi reservation details (v3.2)

Scenario: Retrieve taxi order details including multiple legs.

{
  "request_id": "03fr9fz702lmnop12w34x5y6z",
  "data": [
    {
      "id": "709430129718801",
      "affiliate": 333333,
      "taxis": [
        {
          "reservation": "TX987654321",
          "pickup_location": { "city": "Paris", "country": "fr" },
          "dropoff_location": { "city": "Lyon", "country": "fr" },
          "start": "2026-07-10T09:00:00+00:00",
          "end": "2026-07-10T14:00:00+00:00"
        },
        {
          "reservation": "TX987654322",
          "pickup_location": { "city": "Lyon", "country": "fr" },
          "dropoff_location": { "city": "Marseille", "country": "fr" },
          "start": "2026-07-12T10:00:00+00:00",
          "end": "2026-07-12T15:00:00+00:00"
        }
      ],
      "booker": {
        "name": { "first_name": "Bob", "last_name": "Brown" },
        "email": "bob.brown@example.com",
        "telephone": "+33123456789",
        "language": "fr",
        "platform": "mobile",
        "travel_purpose": "leisure",
        "address": { "city": "Paris", "country": "fr" }
      },
      "commission": {...},
      "currencies": { "booker": "EUR", "product": "EUR" },
      "price": {
        "commissionable_price": { "booker_currency": 375, "product_currency": 400 },
        "total_price": { "booker_currency": 400, "product_currency": 425 }
      },
      "start": "2026-07-10T09:00:00+00:00",
      "end": "2026-07-12T15:00:00+00:00",
      "status": "booked",
      "created": "2026-02-01T08:00:00+00:00",
      "updated": "2026-02-02T10:00:00+00:00"
    }
  ],
  "metadata": {...}
}

Error handling

While the /orders/details endpoint follows general API error conventions, there are several endpoint-specific conditions to be aware of:

Post-booking - Specific travel service details

Use each orders/details/*service endpoint for granulard details on a specific travel service so you can perform post-booking tasks such as:

• Managing cancellations or modifications.
• Reporting commissions to affiliates.
• Allocating loyalty points or rewards.

Travel service details guides