Integrations · Carrier vetting
Carrier vetting integrations for freight brokers
Carrier Vetting uses FMCSA data out of the box. Connect RMIS to check insurance limits and expiry for carriers in your RMIS network. Highway is not connected because it publishes no API.
What connects
| Integration | Who uses it | Status in Tezify |
|---|---|---|
| FMCSA data | Brokers | Built in |
| RMIS | Brokers | Insurance, authority, change checks |
| FMCSA QCMobile | Carriers and brokers | Your own BASIC percentiles in Safety |
| Highway | Brokers | Coming soon: no public API |
Set up vetting
- Ask RMIS for API access and connect RMIS.
- Open Carrier Vetting, enter a carrier's MC or DOT, and press Check RMIS.
- Use Check RMIS changes on the card to see carriers RMIS flagged as changed.
- Add your free FMCSA QCMobile webKey for your own BASIC scores.
Highway is not connected: its API comes with the Connect Core plan and its documentation is not public.
Common questions
Does Tezify check carriers without RMIS?
Yes. Carrier Vetting uses public FMCSA data for authority and safety. RMIS adds insurance limits and expiry dates for carriers in your RMIS network.
Why is Highway not connected?
Highway shares its API only with Connect Core customers and publishes no documentation. If you have the plan, send Highway's API guide to Tezify support.
Ready to do it? This lives at /admin/integrations in Tezify.