Highway

Highway supports carrier onboarding, compliance monitoring, alerts, and carrier document sync when connected for your organization.

Setup checklist

1. Confirm your Highway account access.
2. Open Settings, then Integrations.
3. Select Highway.
4. Enter the Highway API key and environment.
5. Turn on Enable Highway onboarding.
6. Save settings.
7. Configure the onboarding packet and carrier alert webhooks in Highway when webhook sync is used.
8. Contact support for initial bulk import from monitored carriers if needed.

Webhook setup

Highway settings show the webhook URLs and generated bearer token. In Highway, create production webhooks for onboarding packet and carrier alert events, then set the authorization header to Bearer <webhook token>.

The settings page shows whether each webhook is configured.

Test workflow

1. Preview or search for one carrier by Highway ID, DOT, or MC number.
2. Sync carrier profile and monitoring details.
3. Review alerts, compliance information, documents, contacts, and packet details.
4. Compare the synced profile with Highway.
5. Approve, reject, block, or keep inactive according to your policy.

Normal usage

Use provider data as part of your review process, then make the final carrier approval decision inside your team’s operating policy.

Review Highway alerts before assigning a carrier to a load. If a carrier’s risk or monitoring status changes, update the carrier status according to your policy.

Manual sync is for carriers already connected in Highway. If the carrier is not connected there yet, invite the carrier first. When an invite finds an existing Highway connection, ARK TMS syncs the latest provider record instead of sending a duplicate invitation.

Manual sync can recover completed Highway onboarding packets that were not previously imported by webhook. When matching packet documents are found, ARK TMS imports them into the carrier files area with standard document types and may show packet sync counts or warnings.

New Highway carriers can stay inactive while an invite or packet is still pending. Existing active carriers may show an onboarding-incomplete warning when Highway paperwork is not complete; normal dispatch checks still determine eligibility.

If a Highway invite or provider action succeeds but ARK TMS cannot fully update the local carrier record, the action may return a warning. Review the carrier profile, lifecycle status, and synced evidence before retrying or approving the carrier.

Highway may sync profile metadata even when a document file cannot be downloaded. Compare the carrier profile with Highway before deciding whether a missing file blocks approval.

Only one carrier onboarding provider can be active at a time. Turning on Highway onboarding disables RMIS and MyCarrierPortal onboarding actions.

Troubleshooting

• Carrier not found: confirm the legal name, MC number, DOT number, or Highway profile.
• Identifier rejected: use a real DOT, Highway ID, or MC docket value; all-zero or malformed values cannot be sent to the provider.
• Sync asks for an invite: the carrier is not connected in Highway yet.
• Duplicate carrier conflict: resolve or archive non-deleted local carrier records that share the same DOT or MC/MX/FF identity before retrying sync.
• Pending invite or paperwork warning: review the Highway packet before making the carrier active; normal dispatch checks still determine eligibility.
• Sync or invite action missing: confirm Highway onboarding is enabled and no other carrier onboarding provider is active.
• Alerts do not match: compare the carrier profile directly in Highway.
• Documents missing: confirm the documents are available in Highway and sync again. If the documents belong to a completed onboarding packet, use manual sync on the connected carrier.
• Webhook updates missing: confirm both Highway webhooks are configured with the bearer token from Settings.
• Sync completed with warning: review the carrier profile and lifecycle status, then sync again if local evidence still looks stale.
• Status looks outdated: refresh the carrier profile before making an approval decision.
• Monitored carriers need initial import: contact support.