> 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/readme/booking-overview/baggage.md).

# Baggage

{% hint style="info" %}
💬 **Need help?** If you're stuck, ask Eva on ATRIP 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` or `getOffers.do`.

#### Which identifier should I use?

Send `offerId` in `getLuggage.do`.

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

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

### 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/readme/booking-overview/create-order.md) to send the selected baggage `productCode` when required.

If seat selection is also needed, use [Seats](/api-document/readme/booking-overview/seats-and-baggage.md).

### Related pages

* [Verify](/api-document/readme/booking-overview/verify.md)
* [Get Offer](/api-document/readme/booking-overview/get-offer.md)
* [Create Order](/api-document/readme/booking-overview/create-order.md)
* [Post-ticketing Ancillaries](/api-document/readme/post-booking-overview/post-booking-operations/post-ticketing-ancillaries.md)

### Full API reference

See the complete endpoint schemas and samples here:

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


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://resources.atriptech.com/api-document/readme/booking-overview/baggage.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.