McLeod PowerBroker Integration Guide
Updated today
TrackFlo connects to your McLeod PowerBroker instance through its web services API, the same one your instance documents at https://<your-mcleod-host>/ws/docs/. Movements are read on a schedule; if you use RapidAlerts, McLeod can also push changes to TrackFlo as they happen.
What TrackFlo reads
Active movements and their orders, stops, carrier, driver and equipment.
Call-in history, so check calls made in McLeod appear on the TrackFlo timeline.
Movement and brokerage statuses, mapped to TrackFlo's shared status vocabulary.
What TrackFlo writes
Call-ins with status, city and state, remarks and an ETA.
Stop arrivals and departures.
Driver, truck and trailer on the movement.
Proof of delivery as an imaged document.
What your McLeod admin sets up
An API user. McLeod supports HTTP Basic and its own Token scheme. Which one your instance accepts varies by version and configuration, so we confirm it against your instance during onboarding rather than assume. A token can be created under Sys Admin → Smartphone Mobile Service, or minted from a Basic login.
Network access to your instance's web services port from TrackFlo, if it sits behind a firewall.
RapidAlerts (optional). Point the alert at your tenant's TrackFlo webhook hostname with the bearer token we issue. Without RapidAlerts, TrackFlo still stays current through polling.
Things to know
Status codes are yours. Brokerage status codes are configured per McLeod instance, so the mapping to TrackFlo statuses is built with you, not copied from another customer.
"Not found" is a 204. McLeod answers a lookup for a missing record with an empty success response rather than a 404. TrackFlo handles it; it is worth knowing if you ever read the API yourself.
Availability. McLeod-hosted instances have maintenance windows and occasional outages. TrackFlo retries and resumes; a gap in updates during a McLeod outage closes on the next successful poll.