FMCSA Carrier Safety Search - DOT KYB & Crash API avatar

FMCSA Carrier Safety Search - DOT KYB & Crash API

Pricing

from $1.60 / 1,000 results

Go to Apify Store
FMCSA Carrier Safety Search - DOT KYB & Crash API

FMCSA Carrier Safety Search - DOT KYB & Crash API

Search official FMCSA carrier, inspection, violation, and crash records by company or USDOT for trucking KYB and insurance. Returns DOT/MC status, fleet, safety rating, OOS violations, and crashes. No key. Related: Business Entity Search, OSHA, OFAC.

Pricing

from $1.60 / 1,000 results

Rating

0.0

(0)

Developer

Ava Torres

Ava Torres

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

9 days ago

Last modified

Features

Limited permissions

Share

FMCSA Carrier Safety Scraper — DOT, Inspections & Crashes API

Search official FMCSA carrier, inspection, violation, and crash records by trucking-company name or exact USDOT number. The Actor uses public U.S. Department of Transportation datasets, requires no API key, and returns source-linked evidence for carrier onboarding, commercial-auto insurance, compliance review, and trucking lead workflows.

What it returns

Carrier identity and operating evidence

  • USDOT number, legal name, and DBA name
  • Active, inactive, or pending registration status
  • MC/MX/FF operating-authority docket numbers and status codes
  • FMCSA safety rating and review dates when available
  • Power units, trucks, buses, drivers, CDL drivers, mileage, and fleet size
  • Phone, cell phone, fax, email, physical address, and mailing address when reported
  • Hazardous-material indicator and reported cargo classifications

Latest inspection and violation evidence

  • Inspection ID, report number/state, date/time, location, level, and facility code
  • Total, driver, vehicle, and hazmat violation counts
  • Driver, vehicle, hazmat, and total out-of-service counts
  • Linked violation codes, descriptions, units, citation numbers, and out-of-service indicators
  • Official record URLs for the inspection and source dataset

Latest crash-involvement evidence

  • Crash report ID, number/state, date/time, location, city, and reporting agency
  • Injury, fatality, tow-away, hazmat, and federal/state-recordable indicators
  • Vehicle/configuration/road/weather/light source codes and reported event sequence
  • Official crash-record URL

Quick test

The strongest first-run workflow is an exact USDOT lookup:

{
"dotNumber": "54283",
"fetchSafetyHistory": true,
"maxInspections": 10,
"maxCrashes": 10
}

Search by carrier name:

{
"carrierName": "Swift Transportation",
"statusCode": "A",
"fetchSafetyHistory": true,
"maxResults": 10
}

Carrier-only lead search without secondary safety-history requests:

{
"carrierName": "Transport",
"state": "TX",
"statusCode": "A",
"fetchSafetyHistory": false,
"maxResults": 25
}

Input

FieldRequiredDescription
carrierNameOne of name/DOTSearches legal and DBA names.
dotNumberOne of name/DOTExact USDOT lookup; takes precedence over name.
stateNoTwo-letter physical-address state filter.
statusCodeNoA active, I inactive, or P pending for name searches. Exact USDOT lookups ignore this filter.
fetchSafetyHistoryNoAttach latest inspection, violation, and crash records. Defaults to true.
maxInspectionsNoLatest inspections per carrier, 1–25. Defaults to 10.
maxCrashesNoLatest crash reports per carrier, 1–25. Defaults to 10.
maxResultsNoTotal carrier response cap, 1–100.

If no carrier name or DOT number is supplied, the Actor uses deterministic Swift Transportation USDOT 54283, so first runs and Store quality tests return current carrier and safety evidence quickly.

Common workflows

  • Carrier onboarding and USDOT/MC verification
  • Commercial-auto insurance and transportation risk review
  • Inspection and out-of-service violation research
  • Reported crash-involvement screening
  • Freight-broker and shipper carrier due diligence
  • Trucking-company lead generation and fleet-size segmentation
  • CRM/vendor-record enrichment and monitoring

Evidence limits and responsible use

FMCSA records are screening evidence, not a complete or real-time safety determination.

  • Crash involvement does not establish fault or preventability. A crash record shows reported involvement. It is not proof that the carrier or driver caused the crash.
  • Inspection violations and citations can be corrected, challenged, settled, or adjudicated later.
  • State and FMCSA reports can be delayed, duplicated, amended, or removed as corrections arrive.
  • Driver data are excluded from the public inspection and crash files because of privacy restrictions.
  • Safety ratings, operating authority, registration, inspections, violations, and crashes have different meanings and update schedules; do not collapse them into a single pass/fail conclusion.
  • Output is bounded by maxInspections and maxCrashes and is not represented as complete history.

Review the linked official records and current FMCSA systems before making a safety, insurance, employment, or contracting decision.

Official sources

How to use

  1. Open FMCSA Carrier Safety Search - DOT KYB & Crash API in Apify Console and click Start (or Try for free).
  2. Fill in the input form - start with Registration Status, Fetch Inspections, Violations & Crashes, Latest Inspections per Carrier. Every field is optional unless marked required, and the form is prefilled with a working example.
  3. Set Maximum results to cap your cost, then run the Actor.
  4. Download the results as JSON, CSV, Excel, XML or HTML, or pull them with the Apify API.

Example input

{
"statusCode": "A",
"fetchSafetyHistory": true,
"maxInspections": 10,
"maxCrashes": 10,
"maxResults": 5
}

Output example

One record from a real run (long values shortened, contact details partly masked):

{
"message": "The official FMCSA/DOT Company Census source is temporarily unavailable after retries. Try again later.",
"setupStatus": "source_unavailable",
"sourceUrl": "https://data.transportation.gov/Trucking-and-Motorcoaches/Company-Census-File/az4n-8mr2"
}

Pricing

Pay per event: $0.002 per result plus $0.0001 per run start. No subscription to this Actor is needed. Apify Store discounts apply, so the price per result is lower on Silver, Gold and higher Apify plans. Use Maximum results to cap the cost of each run.

FAQ

How much does FMCSA Carrier Safety Search - DOT KYB & Crash API cost?

$0.002 per result plus $0.0001 per run. For example, 1,000 results cost about $2.00. Higher Apify plans get a Store discount.

Do I need an API key or login?

No. Just configure the input and run it.

Can I run it on a schedule or from code?

Yes. Use Apify Schedules for recurring runs, or call it from the Apify API, the JavaScript or Python client, Make, Zapier, n8n, or any MCP-compatible AI agent.

Why did my run return no results?

Your filters are probably too narrow. Remove a filter or broaden the search, then run again. You only pay the result price for records that are actually saved.

Is the data accurate and up to date?

Each run fetches live data from the source described above, so results are as current as that source. Verify critical records with the original source before acting on them.