TrackFlo Integration API Overview

Updated today

TrackFlo tracks freight for brokerage teams. This API is how your TMS keeps it current: five endpoints, each an upsert, each identified by an id you already have. A first load takes one request.

Where to start

Getting started: base URL, the order to post objects in, a first request and what comes back.
Authentication and tenants: one key per tenant, sent as X-API-Key. What a 401 and a 403 each mean.
Data model: how loads, legs, stops, updates and carriers fit together, and which timestamps travel in pairs.
Rate limits and errors: every status code and what to do about it.

The five endpoints

The API reference lists every field on each endpoint, with its importance at the start of the description, a redacted real example body and a Try it console.

Post in this order	Endpoint	One row per	Reference
1	`POST /api/v1/carriers/upsert`	carrier	Carriers
2	`POST /api/v1/loads/upsert`	order / BOL	Loads
3	`POST /api/v1/loadlegs/upsert`	route / movement	Load legs
4	`POST /api/v1/stops/upsert`	pickup or delivery	Stops
5	`POST /api/v1/loadupdates/upsert`	check call, GPS ping or status remark	Load updates

Every response is the same shape:

{ "status": "processed", "message": "Load processed", "permalink": "1089520-acme" }

Also here

TMS guides: what TrackFlo reads and writes in Turvo, McLeod, Mastery, Tai, Revenova and Quantum Edge.
Front: show the assigned rep and latest update inside Front.
API changelog: every change to the API, dated.
Download the OpenAPI spec for Postman, Insomnia or codegen.

Was this helpful?