Integrations
TMS integrations, with the status of each one stated plainly
Every integration below is marked live, in development or planned. Two are live in the FreightVero TMS today. We won’t sell the others as working until they are.
Short answer
A TMS integration connects your transportation management system to another tool so data moves without retyping. The FreightVero broker TMS has two live integrations: Load Market for tracking and Google Maps for addresses and time zones. QuickBooks Online is in development. DAT, Truckstop, MacroPoint, project44, RMIS, MyCarrierPackets and EDI are planned.
What a TMS integration should do for a broker
An integration earns its place when it removes a step someone does by hand every day. Tracking data should land on the load without a phone call. An invoice shouldn’t be typed twice. A change in a carrier’s insurance should show up before the next dispatch.
It should also respect the rules in the TMS. In the FreightVero TMS, status changes go through one database function, so neither the app, nor an integration, nor someone typing SQL can skip a checkpoint. See how checkpoints work.
Vendor keys for live integrations are kept server-side and never reach the browser.
FreightVero integrations and their status
Status as of September 10, 2026.
| Integration | What it does for a broker | Status | Where it stands |
|---|---|---|---|
| Load Market | Driver-phone tracking with position, ETA and risk on the load | Live | Live since September 3, 2026 |
| Google Maps | Address autocomplete, a time zone for each stop, city and state for tracking positions | Live | Called server-side |
| QuickBooks Online | Customer invoices and carrier bills in your books | In development | Connection built. Invoice and bill sync not built. QuickBooks Desktop not supported yet |
| DAT | Load board posting and carrier search | Planned | Not built |
| Truckstop | Load board posting and carrier search | Planned | Not built |
| MacroPoint | Tracking from carriers’ ELDs, systems and driver app | Planned | Not built |
| project44 | Multimodal shipment visibility | Planned | Not built |
| RMIS | Carrier onboarding and insurance monitoring | Planned | Not built. Compliance status is set on the carrier record today |
| MyCarrierPackets (MyCarrierPortal) | Carrier onboarding, identity checks and monitoring | Planned | Not built |
| EDI (204, 990, 214, 210) | Load tenders, tender responses, status messages and invoices with shippers | Planned | Not built |
Planned means on the roadmap with no working connection. FreightVero has no partnership with the planned vendors listed here.
Integration details
How we decide what comes next
We order planned integrations by what brokers ask us for and what each vendor’s API allows. Some vendors require an approval or partner agreement before a TMS can connect. We’ll tell you where each one stands on a demo call, and we won’t give a date we can’t keep.
If you’re considering the AI agents alongside a different TMS, the connection to that TMS is scoped separately with each brokerage. Live tracking and ETAs are included on the Growth and Scale plans, listed on pricing.
Request an integration
Tell us which tools your desk runs on. Requests shape the order we build in, and we’ll tell you honestly where each one stands.
Frequently asked questions
Which integrations are live today?
Two. Load Market for driver-phone tracking, live since September 3, 2026, and Google Maps for address autocomplete, stop time zones and tracking locations. Everything else on this page is in development or planned, and none of the planned connections work today.
Is there a public API?
Not yet. A public API is planned. Today, the integrations that exist are built and run by FreightVero, and there's no way for an outside developer to connect their own tool to the TMS.
Can FreightVero build an integration that isn't listed?
Possibly. Tell us through the request form. If it's specific to how your business runs, custom TMS development is quoted after a scoping call, and the Bronco Logistics build is the example of that work.
Do the AI agents need these integrations?
Some do. The Tracking agent builds on the live Load Market connection. The Load Posting and Carrier Response agents depend on the planned DAT and Truckstop integrations. Each agent page states which connections it needs and whether they exist.