FMCSA New Carrier Feed — Trucking Authority Leads, Phone avatar

FMCSA New Carrier Feed — Trucking Authority Leads, Phone

Pricing

from $5.00 / 1,000 carrier leads

Go to Apify Store
FMCSA New Carrier Feed — Trucking Authority Leads, Phone

FMCSA New Carrier Feed — Trucking Authority Leads, Phone

Newly-registered US motor carriers with company name, phone, email and address. Dedup means scheduled runs only return brand-new carriers. For trucking-insurance agents, factoring, ELD and compliance sellers. Now also syncs free to Notion, HubSpot, Airtable or Supabase.

Pricing

from $5.00 / 1,000 carrier leads

Rating

0.0

(0)

Developer

K O

K O

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

0

Monthly active users

2 days ago

Last modified

Share

FMCSA New Trucking Carrier Leads – Phone & Email

Reach a trucking company in the narrow window right after it registers — before it has an insurance policy, a factoring relationship, or an ELD vendor.

Built from the FMCSA Motor Carrier Census: every newly-registered US motor carrier, sorted newest-first, with phone, email, physical address, fleet size, and operation type normalized into one clean lead record.


Pain points

  • A new trucking company legally cannot haul freight without insurance in place — but a generic "trucking leads" list gives you the same static roster every agent already called, with no way to tell who just registered.
  • FMCSA's own SAFER/census lookup is a one-carrier-at-a-time web tool. There's no bulk export and no "show me who's new since I last checked."
  • The raw census table is not usable as-is: dates are stored as strings like 14-MAY-26, the DOT-number column is text (so a naive sort puts "999999" above "5000000"), and operation-type is a bare A/B/C code with no legend.

What we solve

  • The registration date is the product. A carrier must secure insurance, DOT authority, and permitting before it can legally operate — the days right after its USDOT number is issued are the highest-intent window that exists for anyone selling into trucking.
  • Correctly sorted newest-first, by DOT number parsed and sorted as a real number — not a text sort that puts recent 7-digit numbers behind old 6-digit ones.
  • Near-100% phone fill on recent registrations, pulled straight from the carrier's own MCS-150 filing.
  • Dedup across scheduled runs. With onlyNewSinceLastRun on (the default), a recurring schedule only returns — and only charges for — carriers that registered since your last run.
  • Filter before you spend. states, forHireOnly, and minPowerUnits narrow the feed at the source; the per-run query charge is flat regardless of how many filters you apply.

Who uses it

Commercial trucking-insurance agents (a new carrier must carry insurance before operating — the highest-intent lead there is), freight factoring companies, ELD/telematics vendors, compliance and permitting services, and anyone selling to brand-new trucking businesses.


Input

FieldWhat it does
statesTwo-letter state codes to include (physical address), e.g. CA, TX, FL. Leave empty for all states.
forHireOnlyKeep only carriers authorized for hire (excludes private fleets).
minPowerUnitsKeep only carriers with at least this many power units (trucks). Leave blank for all sizes.
pageSizeRows fetched per API page (max 1000).
maxPagesToScanPages of newest carriers to scan per run.
maxItemsStop after this many normalized records. Leave blank for no limit.
onlyNewSinceLastRunRecommended for schedules. Uses persisted state to skip carriers already returned earlier, so a recurring schedule only charges for genuinely new registrations.
syncEnabledOptional, off by default. Also send each new record to a connected app — see Sync below.
syncDestination, syncWriteTool, syncFieldMap, syncExtraArgsOnly used when syncEnabled is on.

Output

One record per new carrier, newest-first. This is a real record from the current dataset — not a placeholder:

{
"dotNumber": "9999984",
"legalName": "GREENLINE CUSTOM FARMS LLC",
"dbaName": null,
"phone": "(608) 485-2334",
"email": "trinityfarmscody@gmail.com",
"phyStreet": "1100 E TAFT ST",
"phyCity": "BLAIR",
"phyState": "WI",
"phyZip": "54616-9368",
"mailingCity": "BLAIR",
"mailingState": "WI",
"carrierOperation": "Intrastate (Non-Hazmat)",
"authorizedForHire": true,
"hazmat": false,
"powerUnits": 6,
"drivers": 9,
"registeredDate": "2026-05-19",
"mcs150Date": null,
"saferUrl": "https://safer.fmcsa.dot.gov/query.asp?searchtype=ANY&query_type=queryCarrierSnapshot&query_param=USDOT&query_string=9999984",
"source": "FMCSA"
}
FieldDescription
dotNumberUSDOT number — the carrier's stable identifier.
legalNameCarrier's legal business name.
dbaName"Doing business as" name, when on file.
phoneBusiness phone from the carrier's MCS-150 filing.
emailBusiness email from the MCS-150 filing, lowercased.
phyStreet, phyCity, phyState, phyZipPhysical (garage/terminal) address on file.
mailingCity, mailingStateMailing address city/state, when it differs from physical.
carrierOperationDecoded operation type — Interstate, Intrastate (Hazmat), or Intrastate (Non-Hazmat).
authorizedForHiretrue/false — hauls for other companies vs. a private fleet. null if not on file.
hazmattrue/false hazmat flag on file. null if not on file.
powerUnitsNumber of power units (trucks) reported.
driversNumber of drivers reported.
registeredDateDate the carrier's census entry was added (ISO).
mcs150DateDate of the carrier's most recent MCS-150 filing (ISO). Often null on very fresh registrations that haven't filed one yet.
saferUrlDirect link to the carrier's FMCSA SAFER snapshot page.
sourceConstant "FMCSA".

Sync to your CRM, Notion, HubSpot, Airtable or Supabase (optional)

Turn on syncEnabled to also send each new carrier straight to a connected app — free, with no extra charge. Connect the app under Integrations in Apify Console, pick it as syncDestination, and set syncWriteTool to the name of the tool that creates one record there (run the dataset-sync-connector Actor in list-tools mode against the same connector if you don't know the name). A sync failure is logged as a warning and never blocks the dataset — your leads always land here first regardless of what the destination does.

Pricing (Pay-Per-Event)

  • query — charged once per run for the census poll.
  • carrier-record — charged per normalized carrier pushed. This is the primary event.
  • apify-actor-start (Apify-managed) — covers baseline compute per run.
  • Sync to a connected app (optional) — free. No event is charged for records sent to a destination; it's an added convenience on top of the dataset you already paid for.

A daily run filtered to your state returns just that day's new carriers for pennies; a first backfill pull is a larger one-time run you control with maxPagesToScan and maxItems.

Run frequency

Schedule it daily. With onlyNewSinceLastRun on, each run returns only the carriers that registered since the previous run, so a daily schedule keeps your lead list current without re-billing carriers you've already seen.

FAQ

How am I charged?

Pay-per-event. query is charged once per run for polling the census. carrier-record is charged once per normalized carrier pushed to the dataset — that's the primary event. Sync to a connected app (if enabled) is free and never adds a charge.

Where does the data come from?

The public FMCSA Motor Carrier Census, served via data.transportation.gov (Socrata) — the same MCS-150 registration data FMCSA itself publishes. No API key or proxy required.

How fresh is it?

Carriers are returned newest-first by USDOT number, which FMCSA assigns sequentially at registration. The census refreshes on FMCSA's own schedule (typically within weeks of a new registration). Run on a schedule with onlyNewSinceLastRun on to pick up each new batch as it lands rather than re-pulling the whole census.

Is phone always present?

On recent registrations phone fill is near-100%; email is present on roughly half. Both come straight from the carrier's MCS-150 filing.

Which actor do I want if I need something adjacent?

This is currently our only trucking-carrier product — there's no separate actor yet for established/existing carriers (vs. brand-new registrations) or for a hazmat-only feed. Narrow this one with states, forHireOnly, and minPowerUnits instead.


SEO keywords: FMCSA leads, new trucking company leads, motor carrier leads, USDOT new registrations, trucking insurance leads, freight factoring leads, ELD leads, carrier phone list, MCS-150 data