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 200,000+ pieces of capacity, verified carrier dataset - built from live FMCSA data, MOTUS insurance filings and carrier-submitted lane and equipment detail - directly into their existing platform. Disovery is compliance-gated, so you users are never offered a carrier that isn't authorized to operate.
Rest API - Carrier Lookup
A single endpoint returns a fully verified carrier profile
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 lookup inside your TMS
Pull verified carrier profiles and compliance status directly into your carrier-management module. Your users vet carriers by USDOT or MC number without leaving your platform; FreightForge returns authority, insurance and operating status on every call.
Compliance monitoring via webhooks
Subscribe to carrier events. When a carrier is created, updated, changes operating status or has an insurance change, your endpoint receives a signed payload - so your users are alerted to a status change instead of polling for it.
Batch-audit an existing an existing carrier panel
Submit up to 100 USDOT or MC numbers in one call and get a verified profile — or a structured error — for each. Use it to reconcile a carrier database you already have against live FMCSA data.
API Endpoints
Everything you need to build a carrier data integration.
The FreightForge REST API is versioned, JSON-first, and authenticated with HMAC request signing (or a static bearer token on the free tier). All endpoints return consistently named carrier fields.
usdot_number
zone
equipment
per_page
page
identifiers*
id_type
filters
format
fields
filters
format
fields
callback_url
What's in the Data
Up to 143 fields per carrier - sourced, scored, structured, consistently named.
Every profile is built from three authoritative sources: FMCSA federal data (authority, safety, out-of-service history), MOTUS insurance filings, and carrier-submitted lane and equipment preferences. Fields are consistently named. Some profiles are sparse - a typical carrier returns ~90 fields; 19 core fields are on every carrier; the full dictionary spans up to 143.
Carrier Profile Fields
Up to 143 Total
Carrier -submitted
FMCSA auto-populated
FMCSA + MOTUS Insurance
Identity + Authority
company_name
carrier_legal_name
usdot_number
mc_number
operating_authority_status
allowed_to_operate
authority_granted_date
hazmat_indicator
Insurance (FMCSA Legacy + MOTUS)
liability_amount
cargo_amount
insurance_company_name
motus_insurer_name
motus_insurance_coverage_amount
motus_authority_status
Safety + Inspections
safety_rating
oos_status
number_of_oos_events
driver_oos_percentage
vehicle_oos_percentage
accidents_total
Operations + Equipment
number_of_power_units
number_of_drivers
equipment
cargo_carried
carrier_operation
Location + Lanes
city
state_province
company_location_zone
origin_zones
destination_zones
All fields, every request - no field-by-field gating.
Unlike vendors that sell field access separately, every FreightForge API call returns the carrier's full available profile - up to 143 consistently named fields. You build once against one schema and never renegotiate field access as your integration grows.
Partner Types
Three integration paths. Pick the one that fits your platform.
TMS Providers
Embed verified carrier data in your carrier module
Add FMCSA verification and compliance status to your TMS carrier panel without building the data infrastructure. Your users look up and monitor carriers inside your product; FreightForge keeps the data current.
TMS partnership detailsEnterprise 3PLs
Monitor carrier compliance at scale
Reconcile your entire carrier panel through the bulk lookup endpoint and subscribe to webhook events, so status and insurance changes reach you as they happen - without dedicated team polling FMCSA.
3PL integration guideFreight Tech Builders
Build on a verified carrier dataset
Build on a verified carrier dataset: Building a rate engine, load-matching or carrier-relationship tool? Start from a verified, structured carrier dataset instead of building FMCSA ingestion and normalization yourself.
Developer documentationAPI Access Tiers
Scaled to your integration complexity and volume.
Basic
Professional
Enterprise
Integration Questions
What TMS teams ask before committing to an integration.
How long does a typical TMS integration take to build?
Most live in 2–4 weeks. Lookup + monitoring endpoints are straightforward signed REST calls; most build time is UI on your side. Sandbox available.
What happens if FMCSA data is temporarily unavailable?
FreightForge serves every request from its own maintained dataset, so lookups keep working during FMCSA downtime. For compliance-critical flows use webhook subscriptions over polling.
Is there a separate charge for webhook events?
No - included. Subscribe to the event types you want; signed payload on each qualifying event.
What fields will we receive and what happens when some are missing?
Every call returns the carrier's full available profile - up to 143 consistently named fields, with 19 core fields present on every carrier. Profiles are sparse: only populated fields are returned, so treat a missing key as an empty value rather than expecting a null.
Can we look up carriers by MC number as well as USDOT?
Yes. Single lookups are by USDOT; the bulk lookup endpoint accepts up to 100 USDOT or MC identifiers in one call and returns a verified profile - or a structured error - for each, in the order you sent them.
Is there a sandbox we can build against?
Yes. A sandbox environment mirrors the production API and signed-request model so your team can integrate and test before going live. Contact us for sandbox credentials.