Baggage

Atlas API baggage flow for luggage lookup, baggage quotes, and conversion-focused booking decisions.

💬 Need help? If you're stuck, ask Eva in the Help Center for instant diagnostics.

Ask Eva

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 to send the selected baggage productCode when required.

If seat selection is also needed, use Seats.

Related pages

• Verify

• Get Offer

• Get Offer Price

• Create Order

• Post-ticketing Ancillaries

Full API reference

See the complete endpoint schemas and samples here:

Baggage