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

# Get Trip

> Fetch the full lifecycle state of a trip, items, travelers, quote, fulfillment, and any booking references

Inspect the current state of a trip without modifying it. Reach for it when you need to confirm what items are on the trip, verify the travelers attached to a booking, or check whether a checkout has finalized after the user paid. The response covers items, traveler details, quote status, and any booking references that have been issued.

<Accordion title="Tool description (what the LLM sees)" defaultOpen={false}>
  ```text theme={null}
  Fetch the full lifecycle state of a trip, cart contents, travelers, quote status, fulfillment status, and any booking references already produced.

  USAGE:
    get_trip({ trip_id })

  This is a read-only call. Use it to inspect a trip after trip(add_item), trip(upsert_travelers), or checkout, for example to confirm what items / travelers are currently on the cart, or to check whether a booking has been finalized post-checkout.
  ```
</Accordion>

## Parameters

| Name          | Type     | Required | Description                                                                                                                                                                                                                                                                                                                                                                                                                                    |
| ------------- | -------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `trip_id`     | `string` | Yes      | Trip ID returned from a previous trip(add\_item) or checkout call.                                                                                                                                                                                                                                                                                                                                                                             |
| `user_intent` | `string` | No       | The end user's current request in their own words, e.g. "find a cheap flight to Tokyo in mid-June". Pass it as-is when short; otherwise condense the goal and constraints into 1-2 sentences. Strip personal identifiers (names, emails, phone numbers, addresses, payment details), replace them with placeholders like "\[name]". Optional and never changes the result of the call; Jinko uses it to understand demand and improve results. |

## Examples

**Inspect a trip's lifecycle state:**

```json theme={null}
{
  "name": "get_trip",
  "arguments": { "trip_id": "42" }
}
```

**Abbreviated response:**

```json theme={null}
{
  "trip_id": "42",
  "status": "fulfilling",
  "items": [
    { "item_id": 7, "kind": "flight", "trip_item_token": "...", "price": { "total": 842.30 } }
  ],
  "travelers": [{ "first_name": "Jane", "last_name": "Doe", "passenger_type": "ADULT" }],
  "quote": {
    "status": "succeeded",
    "totals": { "subtotal": 842.30, "fees": 0, "total": 842.30, "currency": "USD" }
  },
  "fulfillment": {
    "status": "fulfilling",
    "scheduled_at": "2026-04-21T15:00:00Z"
  },
  "bookings": []
}
```

Once `fulfillment.status` is `completed`, `bookings[]` populates with `booking_ref` (Jinko reference) and `pnr` (airline reference). These are what you surface in confirmation emails or share with the customer.