Dependency: No preceding function needs to be carried out. The order should be ticketed and the departure date should be in the future.
Please note the below "Rules & Restrictions" while initiating a post-ticketing transaction.
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 baggages.
Product Code: "Product code" contains various baggage offerings in aspects of baggage pieces and weights for each airline.
Restrictions for Infants: Baggage ancillary is not allowed to be booked for infant passenger.
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 in 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, 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.
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 purchase either at the booking flow or the post-booking flow.
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 segment (in the same direction) or not added for all the sectors, the API will respond with an error message.
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 journey may have a product code of 1PC and 10KG while the inbound journey may have a product code of 20KG. This is allowed.
API Request Information: The details of only the passenger for whom the ancillary needs to be added must be sent in the API RQ.
Ancillary Category. Different categories of ancillaries need to be separately requested. Currently we only supportBAGGAGE.
paymentMethodinteger | nullableOptional
The payment method you prefer to use. If you specify a payment method (provided that the fare supports it), then you can only use that method for payment.
Responses
200Success
application/json
post
/postBookingAncillarySearch.do
200Success
Order Ancillary
post
Dependency: The postBookingAncillarySearch.do function should be called prior to this one.
Procedure:
Copy the Session ID into the request body.
Type the passenger information and "product code" selected from the response in "postBookingAncillarySearch.do".
POST /postBookingAncillarySearch.do HTTP/1.1
Host:
Accept: text
Content-Type: application/json
Accept-Encoding: text
x-atlas-client-id: text
x-atlas-client-secret: text
Content-Length: 72
{
"ticketOrderNo": "TESTA20240618162411631",
"ancillaryCategory": "BAGGAGE"
}
