Overview
The operations in Bag Data Submit Service version 1.0 will typically be asynchronously processed. This means that all data that follows the syntax will be accepted, but it might not be used by downstream systems.
The figure below visualizes the defined operations.
Service error response
ErrorResponse is typically used with HTTP Response Code: 400 Bad Request
|
Operations
Submits data related to a batch of bags, typically meant for an ULD (Unit Load Device). Parameters Returns Submits bag event data from a baggage handling system (BHS) ( BhsEventData ). This is data related to one bag, with BagTagNumber as the key. The BHS should call this operation for all significant bag events. See BagEventCode for a list of relevant events. Only BagTagNumber and the BagEvent are required. Other elements should be sent when the BHS knows them. If the bag is part of a batch, BhsBatchId links the bag to that batch. The batch information itself is submitted with SubmitBatchData. Parameters Returns Submits information about a lost bag (LostBagData). This is data related to one bag, reported by an airline or handler from their baggage tracing system (e.g. WorldTracer). Since BagTagNumber isn't unique across airports and dates additional information (BagLostAirportIATA, BagLostDate) is needed to uniquely identify the bag. Parameters ReturnsSubmitBatchData( BatchEventDataIn )
SubmitBhsEventData( BhsEventDataIn )
SubmitLostBagData( LostBagDataIn )

