Overview

Interactive shipment processing of individual transactions is useful for some use-cases like Freight Quoting with sales orders or for lower volume shippers, but higher-volume customers and use-cases will need asynchronous integration. With asynchronous integration a “service agent” is used to periodically call the GET ConfirmsList resource to identify and process new updates (for ShipmentConfirms, QuoteConfirms, and VoidConfirms). In a typical integration setup, the same service agent that manages new updates can also identify and transmit new Shipments to Pacejet for processing.

1: GET ConfirmsList to identify new updates for processing

With an asynchronous integration configuration, the service agent will periodically issue a GET ConfirmsList for /New/ShipmentConfirms or /New/QuoteConfirms or /New/VoidConfirms. The returned transactionIDList provides a list of Transaction IDs ready for processing.

2a: GET ShipmentConfirms to retrieve data after shipping with a carrier

With an asynchronous integration configuration, the GET ShipmentConfirms resource is accessed for each Transaction ID in the list returned by ConfirmsList. Returned data can then be used to update an ERP or other system with tracking numbers, shipping costs, etc.

2b: PUT ShipmentConfirms to notify Pacejet of successful ERP update

With an asynchronous integration configuration, a PUT ShipmentConfirms call is made after each ShipmentConfirms, QuoteConfirms, or VoidConfirms is processed with the ERP system. The Put ShipmentConfirms action removes the TransactionID passed in the request from the ConfirmsList and changes the visible ERP Status field on the Search Shipments page to Success.