> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://bcdtravel.ferndocs.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://bcdtravel.ferndocs.com/_mcp/server.

# Get reservation details

## Overview

The `get_reservation_details` endpoint retrieves the full reservation summary and current status for a specific booking. This is the primary endpoint for tracking reservation state after booking.

## Use case

This endpoint can be used to provide users with flight and reservation information most relevant to their upcoming reservation. It must also be used by your application to check the status of a reservation until it is fully completed (e.g. reservation status not `in-progress`), or your application receives an error. The response contains the most relevant summary information of a reservation, including basic flight/fare information, optional and included services, and traveler and payment information.

## What's next?

This is the last step of the booking application workflow.

## Key parameters

| Parameter     | Type   | Required | Description                                                     |
| ------------- | ------ | -------- | --------------------------------------------------------------- |
| `booking_uid` | string | yes      | The unique booking identifier returned from the `book` endpoint |

## Response structure

The response includes:

* `status` — reservation status (`in-progress`, `active`, `cancelled`, `error`)
* `flight_details` — flight information (carrier, route, times, fare class)
* `travelers` — traveler name, contact, and document info
* `payment` — payment method with masked credit card
* `optional_services` — booked add-ons (bags, seats, etc.)
* `included_services` — services included with the fare
* `fare_details` — price breakdown and fare rules
* `cancellation_policy` — refund eligibility and deadlines

## Status polling

After booking, your application must poll this endpoint to track the reservation status:

#### Initial call after booking

Immediately call `get_reservation_details` with the `booking_uid` from the `book` response.

#### Check status

If status is `in-progress`, wait and retry. If status is `active`, the booking is confirmed. If an error is returned, handle accordingly.

#### Display confirmation

Once status is `active`, display the reservation confirmation to the user with flight details and booking reference.

> **Info**
>
> Reservation processing can take varying amounts of time depending on the airline and GDS. Implement appropriate retry logic with exponential backoff rather than rapid polling.