# Flight order details

**Use /orders/details/flights to retrieve detailed information about flight bookings and support post-booking workflows such as managing cancellations, reporting commissions, and generating travelling communications**.

## Retrieve flight order details

→ Use /orders/details/flights to retrieve detailed information for one or more flight orders.

The request supports the following fields:

| Parameter | Description |
|  --- | --- |
| `orders` | Required when reservations is not provided. List of flight order IDs to retrieve. Supports up to 100 IDs. |
| `reservations` | Required when orders is not provided. List of flight reservation IDs to retrieve. Supports up to 100 IDs. |
| `currency` | Optional. Returns monetary amounts in the requested currency where applicable. |


Specify either orders or reservations, but not both.

### Example request

```json
{
    "currency": "EUR",
    "orders": [
      "1234567890123456",
      "9876543210987654"
    ]
}
```

## Response

The response returns a data array containing one object for each requested order.

Common fields include:

| Parameter | Description |
|  --- | --- |
| `id` | The order identifier. |
| `reservation` | Reservation identifier associated with the flight booking. |
| `currency` | Booker and order currency. |
| `itineraries` | Flight itinerary segments, including departure and arrival airports and timestamps. |
| `label` | Identifier associated with the order for attribution or reporting purposes. |
| `price` | Total price in both the booker and order currencies. See the [Pricing guide](/demand/docs/accommodations/prices-accommodations) for details. |
| `status` | Current status of the flight order. |


### Itinerary information

The itineraries array contains the departure and arrival details for each journey segment, including:

* Departure airport (IATA code).
* Departure date and time.
* Arrival airport (IATA code).
* Arrival date and time.


Use the [/common/locations/airports](/demand/docs/open-api/3.2/demand-api/commonlocations/common/locations/airports) endpoint to check accepted airport codes.

### Pricing

The price object returns the total booking amount in:

* `booker_currency` – The traveller's currency.
* `order_currency` – The currency in which the order was created.


If the currency request parameter is specified, returned monetary values are converted where applicable.

### Example response

```json
{
  "request_id": "01jeayp0a7v6abn2fsjhm3jdkt",
  "data": [
    {
      "id": "ORDER_ID",
      "reservation": "RESERVATION_ID",
      "currency": {
        "booker_currency": "EUR",
        "order_currency": "USD"
      },
      "itineraries": [
        {
          "departure": {
            "airport": "CAI",
            "date_time": "2024-03-01T07:00:00+00:00"
          },
          "arrival": {
            "airport": "LXR",
            "date_time": "2024-03-01T08:10:00+00:00"
          }
        }
      ],
      "label": "SAMPLE_LABEL",
      "price": {
        "booker_currency": 197.87,
        "order_currency": 212.86
      },
      "status": "booked"
    }
  ]
}
```

## Order status

| Order status | Description |
|  --- | --- |
| `booked` | The flight booking has been successfully confirmed. |
| `cancelled` | The booking has been cancelled. |
| `unknown` | The current status is unknown or not available. |


## Next steps

Related guides:

- Understand [cancellation policies](/demand/docs/orders-api/cancellation-policies).
- Learn how to [cancel orders](/demand/docs/orders-api/cancel-order).
- Use [labels and attribution](/demand/docs/orders-api/labels-attributions) for reporting and reconciliation.