project44 integration: location and predictive ETAs

Some of the carriers on your board already share their location with shippers through a visibility network instead of, or alongside, an ELD connection. project44 is one of those networks, and Roadmark reads the location and predictive ETA it reports for any carrier that's already sharing with you through it, so tracking has a current ETA without that carrier installing anything new for Roadmark specifically.

How a carrier gets into project44's network

project44 runs its own onboarding for carriers. As its carrier FAQ describes, a carrier connects through its ELD or telematics provider, project44's DriveView app on a driver's phone, or an API, and then decides which of its customers can see that data, with the option to stop sharing with any of them at any time. So a carrier's trucks show up for you once that carrier is sharing with you through project44. Roadmark doesn't do that onboarding: it reads from carriers already connected on project44's side.

Connecting Roadmark to project44

project44's Movement platform authenticates API clients with the OAuth 2.0 client credentials grant. An admin with the Movement Customer Admin role registers a client application, assigns it the roles and access groups covering the data Roadmark should read, and Roadmark uses that client's credentials to request an access token from project44's OAuth token endpoint. Nothing about how a carrier connects to project44 changes.

What a predictive ETA adds

project44 describes its ETA as recalculated continuously from a truck's current position along with conditions such as traffic and how that carrier has historically performed on that lane, rather than an ETA that only updates when a status message arrives. Roadmark reads that ETA the same way it reads an ELD's: as one of five sources feeding a load's status, alongside the driver app, a carrier's own app or an EDI 214, other visibility networks, and a check call when nothing else is reporting. The same ETA that shows up on the load board is what a customer sees in their own portal.

A worked example

On Tuesday's board, load 48219 is covered by Northline Freight, an outside carrier, at $1,655.00 in US dollars. Ashgrove Logistics doesn't run that truck, so there's no ELD connection to read from directly. If Northline Freight already shares its location through project44, Roadmark reads that feed instead: tracking gets an ETA for 48219 the same way it would from a connected ELD, and Prairie Foods or whichever customer is waiting on that load sees the same ETA in their own portal, without Ashgrove Logistics calling Northline Freight to ask where the truck is.

Why this matters for brokers

A broker or a group's brokerage arm tenders loads to carriers it doesn't operate, so it can't put its own ELD in someone else's truck. project44 is built for exactly that gap: it tracks the carrier, not the freight's owner, so a broker gets the same current ETA on a purchased-power load that a carrier gets on its own trucks. That's what feeds the same customer portal either way.

For a broker or carrier already working with project44-connected carriers, the change is mostly that the board and the customer portal catch up to what project44 has been reporting the whole time, instead of a dispatcher copying an ETA across from a separate dashboard.