The #1 App for North American Truckers — Trusted by 1M+ drivers for parking, stops, fuel & weigh stations.
Learn More
Trucker Path for Fleets API
Keep Dispatch in the System You Already Run
Keep loads, customers and billing in your TMS. Send trips to drivers in Trucker Path, then read back actual miles and stop times.
Routes open in the driver app. The API does not return routes to your software.
Your TMS
Loads, customers and billing stay here
Send stop coordinates + driver ID
Trucker Path for Fleets
Build the route on your truck profile
Deliver the trip to the driver
Trucker Path driver app
Truck-safe navigation on the phone
Read back into your TMS
MilesArrival & departureDwell time
Your system polls for results
API workflow illustration
- 36
- Documented endpoints, REST over HTTPS
- Client ID + JWT
- Bearer auth, tokens you generate yourself
- No middleware
- Your system talks to ours directly
How a trip reaches a driver
From Your TMS to the Driver and Back
- 01Onboard
Invite your driver
Invite the driver to your account. They accept in the Trucker Path app before you send the first trip.
- 02Post
Send the trip
Send stop coordinates and the driver ID. Geocode addresses first; use an Idempotency-Key to prevent duplicate trips.
- 03Drive
Navigate in the app
The route uses the truck profile and opens in Trucker Path, alongside parking, fuel prices and weigh station status.
- 04Read back
Read back results
Poll for miles, trip performance and stop times. Your system controls the interval; there are no webhooks.
What flows back
Bring Trip Data Back to Your TMS
Read the data your team needs for reporting, billing and daily operations.
Driver mileage
Compare planned, actual and out-of-route miles, plus planned and actual time, by driver and period.
Arrival and dwell time
Read scheduled arrival, actual arrival and departure, and dwell time for each stop to support detention records.
On-time performance
Report completed, on-time and delayed trips by driver and period, directly from your own system.
App or ELD location
Use app locations by default or request ELD positions after the driver logs in and completes ELD binding.
Your facility IDs
Keep your external facility IDs and query points of interest in bulk, using the identifiers already in your TMS.
Linked documents
Attach BOLs, PODs, rate confirmations, scale tickets, fuel receipts and settlements to customers, loads, drivers or vehicles.
Before you scope it
What It Does, and What It Does Not
Read this before estimating the work. Everything below comes from the published specification, and the things it cannot do are listed as plainly as the things it can.
Capability
Trucker Path for Fleets API
Create a trip and send it to a driver
IncludedStop coordinates + driver ID. Idempotency-Key: 24-hour deduplication.
Read back planned, actual and out-of-route miles
IncludedBy driver and period, including planned and actual time.
Stop-level arrival, departure and dwell time
IncludedOn every stop of a trip.
Use your ELD as the position source
IncludedChoose ELD after the driver completes binding.
Return a route to your software
—Not includedRoutes go to the driver app; no route geometry is returned.
Resolve a street address
—Not includedStops are coordinates. Geocode on your side first.
Push updates to you
—Not includedPolling only; no webhooks, callbacks or subscriptions.
Track the whole fleet in one call
—Not includedOne driver ID per request.
Write truck dimensions
Read onlyList profiles via API; set dimensions in the portal.
Hours of service
—Not includedHours stay with your ELD; no HOS endpoint.
An official SDK
—Not includedUse REST directly; generated snippets are not an SDK.
Choose your setup
Three Ways to Connect Your Fleet
Start with no-code fleet dispatch or ELD integration. Use the TMS API when you need a custom connection.
01 · Fleet dispatch
Fleet Dispatch — No Code
Plan a stop in Trucker Path and send it to a driver. Try the navigation experience before building an integration.
See small fleet dispatch
02 · ELD integration
ELD Integration — No Code
Connect your ELD to sync drivers and status. After driver binding, your system can read ELD positions through the API.
See the ELD integrations
03 · TMS API
TMS API — Custom Integration
Send trips from your TMS and read back miles via API. McLeod also offers an announced navigation connection through Driver Sidekick.
See the TMS optionsReported by fleets running Trucker Path
$84,000-some down to $40,000-someThomas E., Founder of Keller Trucking, on one month of toll bills.
Drivers up to speed quicklyChandler Klein, Sr. Business Analyst at Christenson Transportation.
2,800+ fleets, 45,000+ vehiclesRunning Trucker Path for Fleets on their own trucks today.
FAQ
What Developers Ask First
Does the API return a route to my software?
No, and this is the most common misunderstanding. Trucker Path for Fleets is a fleet operations API rather than a routing engine. Your system posts a trip with stop coordinates and a driver ID; the route is built on that truck's profile and opens in that driver's Trucker Path app. What comes back to your software is the trip identifier and, afterwards, the miles and times that were actually run. If you are looking for a service that returns waypoints to draw on your own map, this is not it.
What does my system have to send?
A trip with stop coordinates and a driver ID. Coordinates, not addresses: there is no geocoding in the API, so a system that holds only street addresses resolves them first. The driver must already be on your Trucker Path account, which means inviting them and having them accept before the first trip can be sent to them.
What comes back into my system?
Per driver and per period: out-of-route miles, scheduled miles, actual miles, scheduled time, actual time, trips completed, on-time trips and delayed trips. Per trip: each stop's scheduled arrival, actual arrival, actual departure and dwell time. That last set is what a fleet uses to argue detention, because it is a timestamped record of when the truck actually got there and when it actually left.
How does authentication work?
A Client Identifier plus a JWT bearer token on every request, not a static API key. You generate tokens yourself from the API settings page after logging in to Trucker Path for Fleets. The documented guidance is 25 requests per second per client, and the spec describes exceeding it as a cause of degraded response times rather than a hard cap.
Are there webhooks?
No. There are no webhook, callback or subscription endpoints, so anything you want to know about is polled. Tracking is also per driver rather than fleet-wide: the driver ID is required on the request, so a hundred drivers is a hundred calls. Plan the polling interval against the 25 requests per second guidance.
What stops a retry from creating the trip twice?
Send an Idempotency-Key header on trip creation. It is a UUID you generate, and for 24 hours the same key returns the original response instead of creating a second trip. Use it: network retries are the usual way duplicate trips reach a driver's phone.
Can I set truck dimensions over the API?
No. The routing profile is read-only over the API — there is a list endpoint and nothing that writes. Height, weight, length, axle count and hazmat class are set once per truck in the web portal, and every trip for that truck routes against the profile, including trips your own software creates.
Where do the GPS points come from?
Either the Trucker Path app or your ELD. The driver dispatch tracking request takes a data source that defaults to the app and can be set to ELD instead. The spec notes that the driver must log in and complete ELD binding before GPS points begin syncing. This is why the ELD connection is worth doing even if hours of service is not what you came for: it becomes a second, compliance-grade position source for your own systems.
Is there an official SDK?
No. The documentation page shows code snippets in several languages, but those are generated by the documentation tool rather than maintained client libraries, and there is no published Trucker Path SDK. You call the REST endpoints directly.
Scoping an integration?integrations@truckerpath.com
Send One Trip Before You Scope the Work
Start the trial, plan a stop by hand and dispatch it to a driver. It takes minutes, it needs no code, and it settles what the integration is actually buying you.
Start Free Trial