Highway is Carrier Identity. Focused on solving the digital identity problem in the trucking industry. They Remove risk and friction between brokers and carriers by being the only onboarding provider with a Carrier Identity Engine. They manage carrier identity and solve the problem of fraud and double brokering while providing brokers with the richest data on carrier equipment to supercharge their capacity sourcing and vetting efforts. Highway accelerates connections and drives engagement, making the industry more integrated, digital, and secure.


The Highway team needs to provide an API key; our support/onboarding team must create an integration source and add a source setting called ApiKey and add it as the value.

Onboarding Packet

After the set-up, the Onboarding Packet job runs every 5 minutes and will handle the initial sync to build up all the carrier data in the TMS.

Imported carrier details include:

  • Payment terms
  • Payment method
  • Factoring organizations
  • Preferred regions
  • Shipment types
  • Equipment types
  • Tax ID
  • Remit to address
  • Contacts

Carrier Full Update and Bulk Upload

These jobs run every Saturday to catch up on potential changes on either Highway or Tai. With the Carrier full update, we attempt to get complete carrier data from Highway, and with the Bulk upload, we send complete carrier data from the TMS to Highway.

Single Carrier Sync

The sync is triggered on carrier creation to ensure it is updated in real-time.

We will send the following information on the sync:

  • Broker carrier ID
  • DOT #
  • MC #
  • Request to update the status in Highway to "Needs to Onboard"

Disabling or Blocking a Carrier

If you decide to update the status of a carrier to disabled or blocked in the TMS, that will trigger a request to update the carrier's status in Highway to "Do Not Dispatch." If you decide to use the carrier later, you can enable them in the TMS, but you will need to manually update the carrier's status in Highway.

Carrier Alerts

This job runs every 5 minutes, checking if a significant event might affect a broker's willingness to work with a carrier, for example, a change in insurance or anything that might impact a broker's rules for carriers. Highway will generate a Carrier Alert; the TMS will consume the carrier details and ensure all carrier data is current.

Rules Assessment

The system will check for the rules assessment status: PassPartial PassFail, or Incomplete.

If it fails or is incomplete, the system will switch the carrier status in the TMS to "Blocked."

The system will check for the Rules assessment status any time it attempts to update the carriers' information which includes the following jobs: 

  • Carrier Full Update (Saturday job)
  • Onboarding Packet
  • Carrier Alerts

Overwrite Setting

By default, the system will overwrite attachments (packets), contacts, and insurance information if the information is updated in Highway.

If you need the system not to overwrite the information, add a source setting in the integration called Overwrite and make the value equal to false.

When false, the system will add new attachments (packets) if the file name and attachment type differ. Insurance will consider the file name, attachment type, and effective and expiration date. If any of these details differ, the system will add a new attachment leaving the original data in the carrier profile for you to review.

Broker and Master Carrier Creation

When an inbound sync occurs (onboarding packet or carrier alert) and the system does not find a broker carrier or the carrier is not part of our master carrier list, the system will create the carrier profile and set it to "Needs to Onboard." The system will attempt to match by DOT or MC number.

Carrier Re Onboarding

If a broker wants to force carriers to sign a new contract, that can be managed in the Highway system. For multiple carrier onboarding, the broker would provide a .csv file of carriers to re-onboard (or Highway can set all carriers to re-onboard).