Customer has a server which can combine information from all their systems to create the necessary info for the Kargo API request (e.g., Order Items, Order #, Scheduled Departure).
Customer decides on a trigger to send to the Kargo system, which could be a batch of new orders, or even item by item as they’re picked.
Customer makes an HTTP POST call using a Bearer Token to the GraphQL API to set up a scheduled shipment and attach an order to it.
Kargo persists the information in its database so it can display it on the dashboard and use it for validation and more.
Kargo gathers all necessary information from its devices and once it has aggregated it all, creates a trigger to push to the customer. This can be on the pallet or shipment level.
Kargo issues an HTTP POST call to an endpoint exposed by the customer as detailed in the documentation. This contains information about the labels for each pallet scanned.
Finally, the customer parses the JSON received from the Kargo Push API and writes it back into their system.
