Post Booking Baggage via API

Overview

Post-Booking Baggage is a solution Atlas has developed to eliminate the complexity of purchasing and managing baggage add-ons after a booking is made. With this solution, you can search and order baggage add-ons whether the booking is made through Atlas or other platforms.This solution helps travel sellers:

• Unlock new ancillary sales opportunities even after ticketing.

• Scale with confidence as the solution eliminates the need to juggle multiple airline portals.

• Streamline baggage management in one seamless workflow, making monitoring effortless and revenue optimization simple.

Use Cases

• Internal orders (Atlas-issued tickets)

Seamlessly search and quote baggage fare using existing order number.

• External orders (Non-Atlas-issued tickets)

Two methods are supported:Method 1: Search First

• Use the flight segment information to search for baggage options.

• Once satisfied with the quote, create an Atlas order number using PNR Claim.

• Proceed to place the baggage order.

Method 2: Import First

• Directly import the PNR to generate an Atlas order number.

• Use the order number to search and purchase baggage.

Workflow Summary

1. Atlas Tickets

• Step 1: Retrieve the order number.

• Step 2: Use the Search Ancillary API to view available baggage.

• Step 3: Place the order usingOrder Ancillary API.

• Step 4: Complete payment with the Payment API.

• Step 5: Use Retrieve Booking API to confirm updated booking.

2. Non-Atlas Tickets

Method 1: Search First

• Step 1: Use Segment Info using Search Ancillary API to view available baggage.

• Step 2: If confirmed to proceed, use PNR Claim API to import the booking into Atlas.

• Step 3: Place the order using Order Ancillary API.

• Step 4: Complete payment with the Payment API.

• Step 5: Use Retrieve Booking API to confirm updated booking.

Method 2: Import First

• Step 1: Use PNR Claim API to import the booking into Atlas.

• Step 2: Use the Search Ancillary API to view available baggage.

• Step 3: Place the order using Order Ancillary API.

• Step 4: Complete payment with the Payment API.

• Step 5: Use Retrieve Booking API to confirm updated booking.

Search Options

• By Flight Segment: Use if you need to check baggage quote before creating the order.

• By Order Number: Use when baggage is linked to an existing booking in Atlas.

API Reference

• PNR Claim API – Import external bookings.

• Search Ancillary API – Retrieve available baggage options.

• Order Ancillary API – Add selected baggage to booking.

• Payment API – Process payment.

• Retrieve Booking API – Verify booking status after baggage added.

Sample Requests & Responses

• Show JSON request and response for:

  • PNR Claim

  • Search Ancillary

  • Order Ancillary

  • Payment

  • Retrieve Booking

Error Handling & Notes

• Common errors: invalid PNR, baggage unavailable, duplicate order.

• Best practices:

  • Always confirm availability with Search Ancillary before ordering.

  • Ensure payment is completed before retrieving updated booking.

• Notes: baggage availability depends on airline policies.

FAQ

1. Can I add baggage for multi-segment flights?

Yes. Additional baggage can be added for a multi-segment itinerary. Do note that the product code should be exactly the same.

1. Is baggage refundable after purchase?

Whether the baggage is refundable or not depends on the airline policy regarding the post-booking baggage.

1. What happens if the payment fails?

The ancillary baggage order will be "cancelled", and no additional baggage will be added to the order.

Rules & Restrictions

Note: "Product code" contains various baggage offerings in aspects of baggage pieces and weights for each airline.

1. Single Booking Limit: Check-in baggage and Carry-on baggage can be added to the segment of passenger either in-booking or post-booking phase altogether or separately, but each type of baggage can only be added one time for the given segment throughout the whole flow. This rule aims to simplify the baggage booking flow for customers by sending the query only one time to book multiple baggage.

2. Restrictions for Infants: Baggage ancillary is not allowed to be booked for infant passengers.

3. Post-Booking Baggage Additions: It is not allowed to add the same type of post-booking baggage to a ticketed order the second time unless the first purchase fails during payment.

Please refer to the below scenarios:a. When the post-booking order is in "ticket-in-process" and "ticketed" status, it's not allowed to order another one. If any query is called, the API will respond with an error message.b. When the post-booking order is in "cancelled" status, the customer can create another order.c. When the post-booking order is in "unpaid" status, the customer can create another order. However, if one of the orders completes the payment and moves to "ticketing-in-process" status, the other orders will stop processing the payment.

1. Existing Baggage Policies: In case the air ticket order already contains free baggage, it’s subject to airline’s ancillary policy whether additional baggage is allowed to be purchased either at the booking flow or the post-booking flow.

2. Consistent Product Codes in Connecting Flights: Same “product code” for baggage is mandatory to be added to each segment in connecting flights. If the "product code" is different for each of the segments (in the same direction) or not added for all the sectors, the API will respond with an error message.

3. Round-Trip Baggage Rule: Rule No.6 doesn't work for round trip flights. This means that the outbound and inbound segments can have different product codes. For example, outbound journeys may have a product code of 1PC and 10KG while the inbound journey may have a product code of 20KG. This is allowed.

4. API Request Information: The details of only the passenger for whom the ancillary needs to be added must be sent in the API RQ.