> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dev.gojinko.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Booking

> Retrieve a booking using the Jinko booking reference and the traveler's last name

Anonymous retrieval for a booking the user already made. Use it when the traveler has their Jinko booking reference and last name, for example to look up the itinerary days later without signing in. Returns the full booking envelope: status, travelers, and itinerary items with confirmation numbers (PNR for flights, confirmation number for hotels).

<Accordion title="Tool description (what the LLM sees)" defaultOpen={false}>
  ```text theme={null}
  Retrieve a booking using the Jinko booking reference and the traveler's last name. No login required.

  USAGE:
    get_booking({ booking_ref: "JNK-A7B3X9", last_name: "Doe" })

  Returns booking details: status, travelers, itinerary items with confirmation numbers (PNR for flights, confirmation number for hotels).

  The booking reference is found in the confirmation email sent after booking. Format: JNK-XXXXXX (6 uppercase alphanumeric characters).
  ```
</Accordion>

## Parameters

| Name          | Type     | Required | Description                                                                         |
| ------------- | -------- | -------- | ----------------------------------------------------------------------------------- |
| `booking_ref` | `string` | Yes      | Jinko booking reference (e.g. JNK-A7B3X9). Found in the booking confirmation email. |
| `last_name`   | `string` | Yes      | Last name of the primary traveler on the booking.                                   |

## Examples

**Guest lookup by Jinko reference + last name:**

```json theme={null}
{
  "name": "get_booking",
  "arguments": {
    "booking_ref": "JNK-ABC123",
    "last_name": "Doe"
  }
}
```

Returns the booking envelope (itineraries, travelers, status). No auth required, this endpoint is guest-accessible so end users can check their own reservations without signing into a Jinko account.

**Error handling:**

The endpoint deliberately returns the same generic 404 for both "booking does not exist" and "last\_name doesn't match this booking\_ref", existence non-leak is intentional. If you get a 404, don't retry with variations; either the user typoed the ref or the booking was never made under this last\_name.