> ## 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.

# Bags

> Check included baggage, select extra bags, and follow booking outcomes with Jinko.

Help travelers check their included baggage before choosing extra bags and paying for their trip.

Bags follow the same flow as every ancillary: see [Ancillaries](/concepts/ancillaries#booking-flow).

## Check included baggage

Start with what the traveler already gets with the fare.

Included baggage belongs to the fare. The fare's `checked_bag_included` indicates whether its price includes at least one checked bag; the same search filter keeps only fares with an included checked bag. Check the fare's allowance for the number of pieces and weight limits before offering extra bags.

**Example questions**

1. "Does this fare include a checked bag?"
2. "How many bags can I take, and what is the weight limit?"
3. "Show me fares that include a checked bag."

## Find extra bags

Show the traveler the bags available for the selected flight.

Read `items[].available_ancillaries` from `GET /v1/trip/{trip_id}/ancillaries` and look for `type: "bag"`. Show the `display_label`, `price_per_unit_money`, and `max_quantity`. See [Ancillaries](/concepts/ancillaries#discover-available-extras) for availability and pricing responses.

`per_pax: true` means the bag is priced per traveler; otherwise it is priced once per booking.

**Example questions**

1. "What does an extra checked bag cost?"
2. "Is that price per traveler or for the whole booking?"
3. "How many extra bags can I add?"

## Select bags

Add the quantity the traveler needs without losing other selected extras.

### Traveler and quantity

Select a bag through `POST /v1/select_ancillaries` using its `offer_id` and `quantity`, with `traveler_ref` for a per-traveler offer. When `max_quantity` is returned, keep the quantity within that limit. Copy `traveler_ref` from the trip response. See the [selection API reference](/api/select-ancillaries) for the request fields.

### Keep existing extras

Selected bags appear in `selected_ancillaries`. Each call replaces the item's previous selection, so send every bag, seat, and other ancillary that should remain selected.

**Example questions**

1. "Add one extra checked bag for me."
2. "Keep our seats and add a bag for my partner."

## Check out

Review the bags and total with the traveler before payment.

After choosing or changing bags, create checkout with the current selections and use the latest checkout link or agent payment parameters. See [Trips and checkout](/guides/trips-and-checkout) for the payment flow.

**Example questions**

1. "What is the total with the extra bags?"
2. "Does this payment include the bag I just added?"

## Manage after booking

Check each bag's outcome before telling the traveler it is confirmed.

After booking, bags appear alongside seats in `booked_ancillaries`. Read each bag's `status` (`confirmed`, `pending`, or `failed`) and any `failure_reason`; a confirmed flight does not by itself confirm the bag.

**Example questions**

1. "Is my extra checked bag confirmed?"
2. "My flight is confirmed. Why is my bag still pending?"
3. "Why could my extra bag not be booked?"

## Related guides

1. [Flight booking](/guides/flight-booking)
2. [Seats](/concepts/ancillaries/seats)
3. [Ancillaries](/concepts/ancillaries)
4. [Trips and checkout](/guides/trips-and-checkout)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.