Run order reports

Use the /orders/details endpoint to retrieve reporting and reconciliation data for existing orders across supported travel services from a single endpoint. It provides a consolidated view of order, pricing, payment, commission, attribution, and service-specific booking data without requiring separate requests to each travel vertical.

The /orders/details endpoint is designed for reporting, synchronisation, and operational workflows across multiple travel services.

Typical use cases include:

• Financial reconciliation and reporting.
• Attribution tracking and performance analysis.
• Synchronising Booking.com order data with internal systems.
• Validating booking, payment, and commission information.
• Retrieving consolidated order information across supported travel services.

Use /orders/details when you need to:

Call orders/details endpoint using one supported filter type.

All requests require:

• currency - three-letter ISO 4217 code.

The only exception is requests using page, where the pagination token already preserves the original query context.

You can also include:

• extras — Request additional information (Currently supports payment)
• services — Restrict results to one or more 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).

The services parameter acts as an inclusion filter. Use the optional services field to limit results to specific travel services, for example:

"services": ["accommodations", "cars"]

Default behaviour when services is omitted:

The default behaviour depends on the filter type:

• Identifier-based requests (orders or reservations): if services is omitted, only accommodation orders are returned.
• Date-based requests (created, updated, start, or end): if services is omitted, all travel services available to your account are returned.

To ensure predictable behaviour, explicitly specify services whenever you want to control which travel services are included.

• Do not assume ID-based requests return all verticals.
• Use date-based filters when building:
  • dashboards.
  • reconciliation pipelines.
  • CRM synchronisation.
• Always explicitly set services when you need a reduced dataset in reporting flows.
• Expect different payload shapes depending on the specific travel service returned (e.g., accommodations vs cars).

Scenario: Retrieve payment, pricing, or commission details for known reservations.

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

Scenario: Synchronise newly created accommodation and car bookings for a certain period.

{
    "created": {
      "from": "2025-12-01T02:00:00+00:00",
      "to": "2025-12-07T02:00:00+00:00"
    },
    "currency": "EUR",
    "services": ["cars", "accommodations"],
    "extras": [
      "payment"
    ]
  }

Scenario: Get all the orders across all travel services (available to the partner) that ended from 05 June 2026 to sync with an internal Customer Relationship Management tool (CRM).

{
    "end": {
      "from": "2026-06-05T02:00:00+00:00",
      "to": "2026-06-08T02:00:00+00:00"
    },
    "currency": "EUR",
    "sort": {
      "by": "updated",
      "direction": "descending"
    },
    "extras": [
      "payment"
    ]
  }

To build incremental sync logic for regularly updating systems:

• Use created.from and created.to to retrieve newly created orders.
• Use updated with small rolling windows (for example, every 30–60 minutes) to detect changes to existing orders.
• Use pagination (metadata.next_page) when processing large result sets.

Each returned order contains common reporting fields regardless of travel service.

When extras includes payment, the response may contain:

• method
• timing
• paid → completed transactions.
• pending→ upcoming or scheduled transactions.

Accommodation payments may also include:

• authorisation_form
• receipt_url

Each order may contain one or more travel service objects depending on what was booked.

Possible service objects include:

• accommodations
• cars
• flights
• attractions (v3.2)
• taxis (v3.2)

Services that are not part of the order are returned as null (or omitted according to the response schema).

Taxi orders may contain multiple legs.

• The order-level price, start, end, and status are aggregated across all legs.
• All legs belonging to the same taxi order share the same reservation identifier.
• Each leg has its own leg identifier and lifecycle.
• If different legs have different statuses, the order-level status may be unknown.

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

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

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

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

Use /orders/details for reporting, reconciliation, and synchronisation.

Use /orders/details/{service} endpoints instead, when you need travel-service-specific functionality, including:

• Managing cancellations.
• Processing modifications.
• Retrieving detailed booking information.
• Supporting customer service workflows.
• Performing service-specific post-booking operations.

These endpoints provide additional information specific to each travel vertical and are recommended for operational booking management.