What is it?
The Baggage Check In - Manual API is used to issue manual baggage tags for single or multiple passengers.
Why use it?
The Baggage Check-In - Manual API is used to check in passenger bags for a single segment or for multiple segments.
When bags are not permitted to be tagged into a city, or if the baggage route has multiple segments and one of the segments is not set up for thru tag bags, Baggage Check-In - Manual will short tag the bag.
This API also supports issuing special baggage; up to six (6) special baggage/baggage types can be associated with a single bag (heavy, priority, limited release, etc).
How it works
This API issues a manual bag tag for
OA carriers, associates a bag with an existing
AE, and adds both weight and reason codes during issuing.
HOSTrefers to host airlines, a.k.a. multi-hosts, that use Sabre as their CRS. Each airline has their own area of data storage, referred to as a partition. A hosted airline may retrieve PNRs created in their partition only.
OArefers to any airline that is not in the current partition or a reference to another airline than itself.
AErefers to an Air Extra, a wide variety of ancillary services.
How to use
To make a successful call to this API, include the following information in the request:
- Itinerary details
- One of the following to identify the passenger:
- Passenger ID
- PNR location, with a
- Seat number
- Sequence number
Some carriers may opt for a 10 digit Bag Tag feature on configuration, which means that in order to make a call, all baggage references need to be at least ten (10) digits.
Note: Carriers are expected to have the Individual Bag Weight setting turned
ON. For total weight carriers, bag weights are saved as the total bag weight, even through this API accepts individual bag weights.