Skip to content

Trucker Path for Fleets + Alvys

Alvys Holds the Load, the API Sends the Route

No connector exists between Alvys and Trucker Path, which matters less here than on most TMS platforms: the fleet API is documented publicly, your system posts the trip and reads the miles back, and a dispatcher can work by hand in the meantime. If someone on your team can call an endpoint, this is a short job.

Start Free Trial
AlvysTrucker Path
Illustration: a trip sent through the fleet API from a dispatch computer to navigation on the driver’s phone.

Via the fleet API · No prebuilt connector

No connector
Nothing prebuilt between Alvys and Trucker Path today
Two ways
The fleet API, or dispatch from Trucker Path
No middleware
Your system posts the trip and reads the miles back on the same API

Your situation

Built for Teams That Already Work in an API

Alvys is a cloud TMS, so if there is someone on your side who can call an endpoint, the API is the shortest path here: your system posts the trip, the driver gets the route, and the miles come back the same way. No middleware in between.

Through the fleet API

Your system posts a trip with the stop coordinates and a driver ID, and the route opens in that driver's Trucker Path app. Planned, actual and out-of-route miles read back the same way.

Or dispatch by hand first

Plan the stop in Trucker Path and send it to a driver. Nothing has to be connected, so you can see exactly what a driver gets before committing developer time.

Your system resolves the address, not ours

The API takes stop coordinates, not street addresses, and does no geocoding. A TMS holding addresses resolves them its own way first — worth knowing on day one rather than on the afternoon the first trip fails to post.

Nothing to subscribe to, so you poll

There are no webhooks or callbacks. Anything you want to know about a trip you ask for, which keeps the integration simple but means your side decides how often to check rather than waiting to be told.

Other TMS platforms

The answer is the same shape whichever TMS holds the load: the fleet API, or dispatching from Trucker Path while the TMS stays the system of record.

Reported 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

Is there an Alvys integration with Trucker Path?

Not a prebuilt one. Alvys is not among the TMS platforms Trucker Path has announced a connection with. The Trucker Path for Fleets API is the route in, and it is documented publicly.

What does the API actually do?

Your system posts a trip with the stop coordinates and a driver ID, and the route opens in that driver's Trucker Path app. Reading back, you get planned miles, actual miles, out-of-route miles, and arrival, departure and dwell time per stop.

What authentication does it use?

A Client Identifier plus a JWT bearer token on every request, not a static API key. The documented rate guideline is 25 requests per second per client.

Can we try it before wiring anything up?

Yes. Plan a stop in Trucker Path and dispatch it to one of your drivers by hand. Nothing needs to be connected for that, and it shows exactly what the driver will see.

Still have questions?navpro@truckerpath.com

The fleet API is documented publicly, and a trial account lets you dispatch by hand while the integration is still a plan. Nothing to connect, seven days, no charge.

Start Free Trial