Mastery (MasterMind) Integration Guide
Updated today
TrackFlo consumes Mastery's event stream for orders, routes, stops and rep assignments, and reads the Mastery REST API to fill in detail and to write back. Authentication is OAuth client credentials issued from your Mastery identity provider.
What TrackFlo reads
Orders and their routes, stops and appointments, as events arrive.
Carrier and driver assignments and the reps on each order.
Reference numbers at the order, route and stop level.
What TrackFlo writes
Status and check-call notes on the route.
Stop arrivals and departures.
Driver and tracking details, including a tracking link.
Proof of delivery as a document on the order.
What your Mastery admin sets up
A client id and secret for TrackFlo in your identity provider, with the roles your Mastery team uses for API access. Non-production and production are separate realms with separate credentials.
Event stream access for TrackFlo's consumer, scoped to the topics above.
Things to know
Rep changes can take time to appear in TrackFlo unless the order itself is touched, because rep data arrives on the order event.
Reference number placement differs by qualifier. Tell us which reference your team searches by most, and we confirm where Mastery carries it for your setup.