Data Syndication - for TMS and 3PL Platforms

Add verified carrier data to your platform. Without building it yourself.

FreightForge gives TMS providers and enterprise 3PLs a REST API to embed a 30,000+ verified carrier dataset complete with fraud scores, FMCSA cross-validation, lane data, and real-time compliance monitoring, directly into their existing platform infrastructure.

Talk to a partner
REST API + webhooks
64 fields per carrier
Real-time FMCSA-verified
White-label onboarding
SLA included

Rest API - Carrier Lookup

A single endpoint returns a fully verified carrier profile

Request
GET /v1/carriers/USDOT-4006166
Authorization: Bearer {api_key}
Response - 200 OK
"usdot_number": "USDOT-4006166",
"legal_name": "Arizona Express Inc.",
"authority_status": "Active",
"insurance_current": true,
"risk_score": "low",
"equipment_types": ["flatbed"],
"lanes": [{...}], // 10 lanes
"verified_at": "2026-06-25T14:22:00Z"
JSON
OAuth 2.0
Rate limited
Versioned

Integration Use Cases

Three ways TMS platforms and 3PLs use FreightForge data.

The API is purpose-built for platforms that need verified carrier data inside their existing product, not as a separate tool their users have to leave the platform to access.

Carrier panel management inside your TMS

Pull carrier profiles, risk scores, and compliance status directly into your TMS carrier management module. Your users vet and onboard carriers without leaving your platform. FreightForge runs verification in the background via API.

Real-time compliance monitoring

Subscribe to webhook events for any carrier in your system. When a carrier's authority lapses, insurance expires, or risk score changes, your platform receives an immediate payload, so your users are alerted before they tender a load to a non-compliant carrier.

White-label carrier onboarding

Embed FreightForge's FMCSA auto-populate onboarding flow inside your platform under your own brand. Carriers see your UI. FreightForge runs the FMCSA lookup, fraud screening and data structuring behind it. Your product gets the feature - you don't build it.

API Endpoints

Everything you need to build a carrier data integration.

The FreightForge REST API is versioned, JSON-first, and authenticated via OAuth 2.0 bearer tokens. All endpoints return standardized carrier profile objects with consistent field naming across calls.

GET
/v1/carriers/{usdot_number}
Retrieve a single verified carrier profile by MC number. Returns all 64 data fields including authority status, insurance, safety rating, risk score, equipment types, and lane data.

usdot_number*

fields

include_lanes

GET
/v1/carriers
Paginated carrier list with filtering by lane zone, equipment type, risk score tier, and authority status. Returns summary profiles by default; pass full=true for complete 64-field records.

zone

equipment

risk_score

authority_status

per_page

page

GET
/v1/carriers/lookup
Bulk carrier lookup - submit up to 100 USDOT numbers in a single request. Returns a verified profile or a structured error for each input. Use for batch-auditing an existing carrier database.

identifiers*

id_type

fields

GET
/v1/carriers/{usdot_number}/risk
Returns only the risk scoring fields for a carrier - FMCSA match status, IP geolocation result, GPS distance score, composite risk tier, and last verification timestamp. Lightweight endpoint for compliance dashboards.

usdot_number*

POST
/v1/export
Trigger an async bulk export of filtered carrier data as JSON or CSV. Returns a job ID; poll /v1/export/{job_id} for status, then download the completed file from the provided URL. Scheduled exports available on Partner plan.

filters

format

fields

callback_url

Webhook events
carrier.authority_lapsed
Authority revoked
carrier.insurance_expired
Coverage gap detected
carrier.risk_score_changed
Score tier updated
carrier.profile_updated
Any field change
carrier.fraud_flagged
New fraud signal
Rate Limits + SLA
Read API: 1,000 req/min standard. Bulk lookup: 100 carriers/request. Webhooks: delivered within 30 seconds of event. Enterprise / Partner plan includes dedicated rate limit tiers and a 99.9% uptime SLA with direct technical support.
Authentication
OAuth 2.0 client credentials flow. API keys scoped by environment (sandbox / production). Sandbox environment available with 1,000 test carrier profiles - build and test integrations before going live.
Data Freshness
FMCSA authority and insurance fields refresh on a daily cycle. Risk scores recalculate on any FMCSA data change. Webhook delivery is event-driven. You're notified within seconds of a change, not on a polling schedule.

What's in the Data

64 fields per carrier. Sourced, scored, and structured for platform integration.

Every carrier profile is built from three authoritative sources: FMCSA federal data pulled in real time, FreightForge's 3-layer verification system and carrier-submitted lane and equipment preferences. All fields are consistently named and typed across API responses.

Carrier Profile Fields

64 Total

FMCSA auto-populated

System-generated

Carrier-submitted

Identity + Authority

legal_name

usdot_number

authority_status

authority_granted_date

entity_type

dba_name

Insurance + Compliance

liability_amount

insurance_company_name

insurance_policy_number

cargo_amount

safety_rating

out_of_service_percentage

Operations

power_units

number_of_drivers

states_covered

street_address

equipment_type

provinces_covered

Lane Data

origin_city

destination_city

origin_location_zone

destination_location_zone

lane_Coverage

Risk + Verification

risk_score

ip_geolocation_result

gps_distance_score

usdot_status

allowed_to_operate

operating_authority_status

operation_classification

All fields, every request - no field-by-field gating.

Unlike fragmented carrier data vendors that sell field access separately, FreightForge API access at the Partner tier returns the complete 64-field profile on every call. You build once against a consistent schema; you don’t renegotiate field access as your integration grows.

Consistent field names and types across all endpoints
Null-safe - missing FMCSA fields return null, not missing keys
Versioned schema - breaking changes announced 90 days ahead

Unlike fragmented carrier data vendors that sell field access separately, FreightForge API access at the Partner tier returns the complete 64-field profile on every call. You build once against a consistent schema; you don’t renegotiate field access as your integration grows.

Consistent field names and types across all endpoints
Null-safe - missing FMCSA fields return null, not missing keys
Versioned schema - breaking changes announced 90 days ahead

Partner Types

Three integration paths. Pick the one that fits your platform.

TMS Providers

Embed verified carrier data in your carrier management module

Add FMCSA verification, risk scoring, and compliance monitoring to your TMS carrier panel without building the data infrastructure. White-label onboarding flow available — carriers register inside your TMS, FreightForge runs verification behind the scenes.

TMS partnership details

Enterprise 3PLs

Automate carrier compliance monitoring at scale

Pull your entire carrier panel through the bulk lookup endpoint, establish webhook subscriptions for compliance events, and receive real-time alerts when any carrier's status changes without a dedicated compliance team to monitor it manually.

3PL integration guide

Freight Tech Builders

Add carrier intelligence to a new freight product

Building a freight rate engine, load matching platform, or carrier relationship tool? FreightForge's carrier data layer gives you the verified, fraud-scored carrier dataset to build on, so you don't spend your roadmap building what we've already built.

Developer documentation

API Access Tiers

Scaled to your integration complexity and volume.

Read API

3PL access

3PL operations teams
Single carrier MC/DOT lookup
Bulk lookup — up to 100/request
64-field carrier profiles
Risk score + fraud flags
Webhook subscriptions — read
White-label onboarding
Custom field mapping
Scheduled bulk exports
Dedicated SLA + support
Talk to us
Full API

TMS partner

TMS platform integrations
Everything in 3PL access
Read + write API
Scheduled bulk exports
Webhook — all event types
White-label onboarding flow
Custom field mapping
Dedicated API key + sandbox
99.9% uptime SLA
Technical onboarding support
Talk to a partner
Enterprise

Custom build

Enterprise freight platforms
Everything in TMS partner
Custom rate limits
Custom schema mapping
Private cloud deployment option
Joint go-to-market support
Co-branded integration docs
Dedicated integration engineer
Custom SLA + enterprise contract
Revenue-share partnership model
Contact us

Integration Questions

What TMS teams ask before committing to an integration.

How long does a typical TMS integration take to build?

Most integrations are live within 2–4 weeks. The carrier lookup and compliance monitoring endpoints are straightforward REST calls. The bulk of the build time is UI work on your side, not API complexity. We provide a sandbox environment with test profiles so you can build and test before touching production data.

Can FreightForge's onboarding flow run under our brand?

Yes - white-label onboarding is available on the TMS Partner plan. Carriers complete registration inside your TMS under your brand. FreightForge handles the FMCSA lookup, fraud screening, and profile creation in the background. Your customers never see "powered by FreightForge" unless you want them to.

What happens if FMCSA data is temporarily unavailable?

FreightForge maintains a cached dataset that serves API requests even during FMCSA API downtime. Cache age is returned in the response header so you know the freshness of each field. For compliance-critical operations, we recommend webhook subscriptions rather than polling. You're alerted on changes rather than depending on real-time lookups.

Is there a separate charge for webhook events?

No - webhook delivery is included in both the 3PL Access and TMS Partner tiers. You subscribe to the event types you want. We deliver the payload to your endpoint on every qualifying event.

Ready to talk about adding verified carrier data to your platform?

We start with a technical scoping call — your integration engineer and ours, 45 minutes, to understand your platform architecture and map the right integration approach. No commitment required.
What the partner call covers
Your platform stack
Architecture review
Integration approach
API vs white-label
Data volume estimate
Sizing + rate limits
Timeline
Typical: 2–4 weeks
Commercial model
License or rev-share