Integrations · Carrier vetting
Highway integration: status and carrier vetting options
Highway is not connected. Its API comes with the Connect Core plan and its documentation is shared only with customers. Vet carriers with FMCSA and RMIS in Tezify.
What Highway does in Tezify
Highway checks carrier identity, authority and insurance. Tezify has no Highway connection, because Highway publishes no API documentation to build against.
An adapter built on guessed fields would vet carriers against nothing, so the card shows Coming soon and takes no keys.
Who needs it
Freight brokers. The Highway card shows on the brokerage company's Integrations page only, because it is about outside carriers or broker pricing.
What you need from Highway
- Highway's Connect Core plan, which is where its API access comes from.
- The API guide and webhook samples Highway gives Connect Core customers.
What to do instead
- Vet carriers in Tezify with FMCSA data (built in) and RMIS if you use it.
- If you are on Highway Connect Core, ask Highway for the API guide and webhook payload samples.
- Send them to Tezify support so the connection can be built.
Test the connection
There is nothing to test. The card does not take keys.
What syncs and how often
- Nothing syncs from Highway.
Limits
- No Highway checks in Tezify until a documented API is shared.
Ready to do it? This lives at /admin/integrations?open=highway in Tezify.