> For the complete documentation index, see [llms.txt](https://resources.atriptech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resources.atriptech.com/api-document/product-guides/booking/optional-ancillaries/baggage.md).

# Baggage

{% hint style="info" %}
💬 **Need help?** If you're stuck, ask Eva in the Help Center for instant diagnostics.

<a href="https://www.atriptech.com/" class="button primary" data-icon="comments">Ask Eva</a>
{% endhint %}

Use this page to build baggage selection into the booking flow.

Start here when you need to:

* show baggage options before booking
* get exact baggage quotes for the current itinerary
* add baggage choice to the booking experience

### FAQ

#### When should I call `getLuggage.do`?

Call `getLuggage.do` as a recommended step before payment.

Baggage display helps reduce hesitation and improve conversion.

Call it after `verify.do`, `getOffers.do`, or `getOfferPrice.do`.

#### Which identifier should I use?

Send `offerId` in `getLuggage.do`.

Use `sessionId` from `verify.do` as `offerId`.

Use `OfferId` from `getOffers.do` or `getOfferPrice.do` directly.

#### What request limit applies to `getLuggage.do`?

`getLuggage.do` shares one `60 QPM` ancillary pool with `seatAvailability.do`.

Over-limit requests return Atlas error code `429`.

Honor the returned `retryAfter` value before retrying.

### Ancillary request limits

Atlas counts `getLuggage.do` and `seatAvailability.do` together in a rolling 60-second window.

The default shared limit is `60 QPM`.

One busy ancillary API can consume the shared pool for the other.

#### How to reduce limit pressure

Avoid repeated baggage checks for the same itinerary in a short window.

Reuse the current verify or offer context while it is still valid.

Honor `retryAfter` when `429` is returned.

### Main API

* `getLuggage.do`

### What should you check first?

Confirm that the airline supports baggage upsell for the current flow.

Confirm that the current verify or offer context is still valid.

Confirm that the returned baggage products still match the itinerary you plan to book.

### What does `getLuggage.do` return?

It returns baggage products for the current itinerary.

Each product has its own `productCode`.

Use that `productCode` in `order.do` when baggage is selected.

### Use this when you need

* Baggage option lookup
* Exact baggage pricing before booking
* Baggage upsell mapping for `order.do`

### Best practice

Choose the itinerary first.

Then query baggage as a recommended conversion step before payment.

Clear baggage pricing helps improve traveler confidence and attachment rate.

Keep baggage mapping consistent across the current booking context before `order.do`.

For connecting flights, keep the baggage selection consistent across connected segments in the same direction.

### Notes

* Availability depends on airline support
* Baggage rules vary by carrier
* Use the current verify or offer context for accurate pricing

### What comes next?

Use [Create Order](/api-document/product-guides/booking/booking-step-guides/create-order.md) to send the selected baggage `productCode` when required.

If seat selection is also needed, use [Seats](/api-document/product-guides/booking/optional-ancillaries/seats-and-baggage.md).

### Related pages

* [Verify](/api-document/product-guides/booking/booking-step-guides/verify.md)
* [Get Offer](/api-document/product-guides/booking/booking-step-guides/get-offer.md)
* [Get Offer Price](/api-document/product-guides/booking/booking-step-guides/get-offer-price.md)
* [Create Order](/api-document/product-guides/booking/booking-step-guides/create-order.md)
* [Post-ticketing Ancillaries](/api-document/product-guides/post-booking/post-ticketing-ancillaries.md)

### Full API reference

See the complete endpoint schemas and samples here:

[Baggage](/api-document/api-reference/booking-apis/baggage.md)