Quantum Edge Integration Guide
Updated today
Quantum Edge is integrated differently from the others. Inbound, TrackFlo reads a replica of your Quantum Edge database through middleware TrackFlo builds and operates. Outbound, TrackFlo writes through the Quantum Edge REST API.
What TrackFlo reads
Shipments, legs and stops from the replica, including status, appointments and trace history.
What TrackFlo writes
Dispatch of a carrier and driver to a leg.
Check-call notes and stop arrivals and departures, recorded as traces.
What your Quantum Edge admin sets up
Read access to a database replica for TrackFlo, over a private network connection. This is the inbound path; there is no polling API for it.
API keys for the Quantum Edge REST API. Note that the leg-update endpoint uses a separate key from the other endpoints, so TrackFlo needs both.
Things to know
Timestamps are exchanged in local time to the minute, without a timezone marker, so the timezone your operation runs in is agreed at onboarding.
Trace types and status codes are configured per instance. The mapping is built from your data, not assumed.
Not supported today: pushing load status or proof-of-delivery documents into Quantum Edge. Status flows from Quantum Edge to TrackFlo only.