Commercial insurance, freight-factoring and carrier-sales teams rarely need a dump of the entire FMCSA census. They need yesterday's grants: the motor carriers, brokers and freight forwarders that just received operating authority.
Since FMCSA moved registration to Motus, those grants live in the Motus AuthHist dataset, not the retired pre-Motus files. The official Socrata API is keyless, but joining each grant to the Company Census File and skipping IDs you have already seen is tedious to run by hand every morning.
This walkthrough uses the FMCSA New Authority & MC Number Leads Actor (quarrylane-data/fmcsa-new-authority-leads) to pull that list and send it to n8n, Make or Clay. There is no FMCSA login and no DOT API key. You only need an Apify account and an API token from Console → Settings → API & Integrations. Store the token in a secret or credential vault — never in a public workflow, gist or blog comment.
Why this list matters
A newly granted MC or USDOT number is a buying signal: the company has just cleared a regulatory step and usually still needs insurance, surety, factoring, load-board access or equipment. Insurance agencies, factoring and load-board sales teams, and CRM workflows in Clay, n8n or Make are the typical buyers.
Run it once from curl or Python
run-sync-get-dataset-items starts a run, waits for it to finish, and returns the dataset items in one response. The call times out at 300 seconds, which is enough for a normal filtered pull (the Actor's default timeout is 10 minutes). Use a tilde (~) between the username and the Actor name. Prefer an Authorization: Bearer header over putting the token in the URL.
Input fields come from the Actor's schema:
-
mode—new-authorities(default) orcensusfor USDOT numbers added to the census in the same date window -
daysBack(default 14), orstartDate/endDateasYYYY-MM-DD -
authorityTypes— optional:carrier,broker,freight-forwarder -
states— census physical-address states, applied after the join -
minPowerUnits/maxPowerUnits— numeric census power units (fleetSizeClassis the official letter class and is returned separately) -
onlyNew+monitorKey— monitor mode (see below) -
maxItems— default 25, maximum 25,000; free Apify plans are capped at 15 results per run
activeCensusOnly (default true) applies only in census mode.
export APIFY_TOKEN="YOUR_APIFY_TOKEN" curl -sS -X POST \ "https://api.apify.com/v2/acts/quarrylane-data~fmcsa-new-authority-leads/run-sync-get-dataset-items" \ -H "Authorization: Bearer $APIFY_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "mode": "new-authorities", "daysBack": 14, "authorityTypes": ["carrier"], "maxItems": 15 }' The same body works in Python:
import json, os, urllib.request TOKEN = os.environ["APIFY_TOKEN"] url = ( "https://api.apify.com/v2/acts/" "quarrylane-data~fmcsa-new-authority-leads/" "run-sync-get-dataset-items" ) body = { "mode": "new-authorities", "daysBack": 14, "authorityTypes": ["carrier"], "maxItems": 15, } req = urllib.request.Request( url, data=json.dumps(body).encode(), headers={ "Authorization": f"Bearer {TOKEN}", "Content-Type": "application/json", }, method="POST", ) with urllib.request.urlopen(req, timeout=300) as resp: items = json.loads(resp.read()) print(len(items), "carriers") print(json.dumps(items[:2], indent=2)) Sample output
The two records below are motor-carrier rows from a succeeded run on 13 Nov 2026 (2:39pm Australia/Brisbane). That run used mode: new-authorities, daysBack: 14 and maxItems: 15. Adding authorityTypes: ["carrier"], as in the snippets above, keeps the list to trucking companies and drops brokers and freight forwarders. Census officer-name fields are omitted here so the example stays on business data; the live dataset still includes officer1 and officer2 when the census publishes them. A few null fields are also omitted for brevity.
[ { "recordId": "MC63547101|Motor Carrier of Property (Except Household Goods)|20261112", "mode": "new-authorities", "usdotNumber": "5983326", "docketNumber": "MC63547101", "authorityType": "Motor Carrier of Property (Except Household Goods)", "authorityGroup": "carrier", "authorityStatus": "Active", "grantDate": "2026-11-12", "grantReason": "Granted", "legalName": "PR LOGISTICS INC", "address": "1481 N PEACH AVE APT 150", "city": "FRESNO", "state": "CA", "zip": "93727", "postalCode": "93727-2084", "country": "US", "phone": "5599442424", "email": "prlogisticsinc@yahoo.com", "powerUnits": 1, "drivers": 1, "fleetSizeClass": "A", "censusStatus": "A", "censusAddDate": "2026-10-22", "saferUrl": "https://safer.fmcsa.dot.gov/query.asp?searchtype=ANY&query_type=queryCarrierSnapshot&query_param=USDOT&query_string=5983326", "source": "FMCSA", "sourceDataset": "auth-hist", "scrapedAt": "2026-11-13T04:39:44.912Z", "mailingAddress": "1481 N PEACH AVE APT 150", "mailingCity": "FRESNO", "mailingState": "CA", "mailingZip": "93727", "cdlDrivers": 1, "operationClass": "AUTHORIZED FOR HIRE" }, { "recordId": "MC65596173|Motor Carrier of Property (Except Household Goods)|20261112", "mode": "new-authorities", "usdotNumber": "4718153", "docketNumber": "MC65596173", "authorityType": "Motor Carrier of Property (Except Household Goods)", "authorityGroup": "carrier", "authorityStatus": "Active", "grantDate": "2026-11-12", "grantReason": "Granted", "legalName": "PURPLE FOX TRANSPORT INC", "address": "7075 WESTWOOD DR", "city": "CARPENTERSVILLE", "state": "IL", "zip": "60110", "postalCode": "60110-3255", "country": "US", "phone": "3314422635", "email": "purplefoxtransportinc@gmail.com", "powerUnits": 2, "drivers": 1, "fleetSizeClass": "B", "censusStatus": "A", "censusAddDate": "2026-10-21", "saferUrl": "https://safer.fmcsa.dot.gov/query.asp?searchtype=ANY&query_type=queryCarrierSnapshot&query_param=USDOT&query_string=4718153", "source": "FMCSA", "sourceDataset": "auth-hist", "scrapedAt": "2026-11-13T04:39:44.912Z", "mailingAddress": "7075 WESTWOOD DR", "mailingCity": "CARPENTERSVILLE", "mailingState": "IL", "mailingZip": "60110", "cdlDrivers": 1, "operationClass": "AUTHORIZED FOR HIRE" } ] Useful columns to map onward: legalName, docketNumber (the MC number), usdotNumber, grantDate, phone, email, powerUnits, city, state and saferUrl.
n8n: schedule a daily pull
- Add a Schedule Trigger (for example, every day at 07:00 in your timezone).
- Either use the official Apify community node or a plain HTTP Request node.
Apify node (@apify/n8n-nodes-apify, on n8n Cloud or self-hosted): add an Apify credential (API token, or OAuth2 on n8n Cloud). Set the resource to Actors and the operation to Run Actor and get dataset items (this waits for the run and returns the rows). Select quarrylane-data/fmcsa-new-authority-leads and paste the JSON input from above into the custom input field.
HTTP Request node (no community package required): Method POST, URL https://api.apify.com/v2/acts/quarrylane-data~fmcsa-new-authority-leads/run-sync-get-dataset-items, header Authorization = Bearer {{$credentials...}} or an n8n environment variable, header Content-Type = application/json, body the same JSON. Raise the node's timeout to at least 300 seconds.
- The response is a JSON array. Use Split Out (or Item Lists) so each carrier is one item, then write to Google Sheets, a CRM, Slack or email.
Make.com: Apify module or one HTTP module
Connect the official Apify app in Make with OAuth or an API token.
For a small daily pull: add Run an Actor, choose quarrylane-data/fmcsa-new-authority-leads, paste the input, and set "Run synchronously" to Yes. Then add Get Dataset Items and map the default dataset ID from the previous module.
Make imposes a hard sync timeout that varies by plan. If a run might exceed it (for example a first monitor run that has to seed a wide unfiltered window), start the Actor asynchronously and use the Watch Actor Runs trigger plus Get Dataset Items. You can also replace both steps with a single HTTP module that calls run-sync-get-dataset-items, the same URL as in the curl example.
Trigger the scenario on a schedule once the path is working.
Clay: HTTP API or the Apify integration
Clay can either import a list or enrich existing rows.
As a list (better for a daily feed): use HTTP API as source. Method POST, the same run-sync-get-dataset-items URL, headers Authorization: Bearer YOUR_APIFY_TOKEN and Content-Type: application/json, body the JSON input above. After the import, map legalName, docketNumber, usdotNumber, grantDate, phone, email and saferUrl into columns.
As an enrichment: Add enrichment → search Apify → Run Apify Actor, connect your token, select this Actor, and paste the input JSON. Or use an HTTP API enrichment column with the same POST details. Clay's HTTP API docs use /ColumnName inside a quoted string to reference another column. Keep maxItems small if the column runs per row — a new Actor run on every row will multiply cost.
Monitor mode: later runs return only new grants
Set "onlyNew": true and a stable "monitorKey" (for example "daily-carriers-us"). Use a different key for each filter set or client.
The first run bills up to maxItems as standard carrier-record events and remembers every other current match in the date window without charging. Later scheduled runs return only IDs not seen before and bill the new-authority event instead. Census mode is always billed as carrier-record.
A first monitor run over a wide unfiltered 14-day window may page AuthHist to seed a couple of thousand grant IDs, but it only joins the census for rows it delivers. If that seed might exceed the 300-second HTTP limit, run it once from Apify Console or an async start, then use the sync endpoint for daily follow-ups.
What it costs
Pay per result, with no monthly rental of the Actor:
| Event | When it is charged | Price |
|---|---|---|
carrier-record | Each row in a standard run, the first monitor run (up to maxItems), and every census-mode row | $0.005 ($5 per 1,000) |
new-authority | Each newly granted authority on a later onlyNew run | $0.025 ($25 per 1,000) |
You also pay Apify's platform usage (compute and storage), which for this Actor is usually a fraction of a cent. Set Max cost per run in the run options as a hard budget.
Worked example: a first monitor run with maxItems 25 costs $0.125 in events and seeds the rest of the window. A typical 14-day national window has around 2,000 grants, so a later unfiltered daily run of roughly 140 new grants would cost about $3.50 in events. Adding authorityTypes and states cuts that down. On the free Apify plan each run returns at most 15 rows, which is enough to test the output.
Try the Actor
The Actor is on the Apify Store: quarrylane-data/fmcsa-new-authority-leads. Run the curl snippet once, then put the same input on a daily schedule with onlyNew and a stable monitorKey.
Built by Quarrylane Data. Not affiliated with FMCSA or the U.S. Department of Transportation. Data comes from the public datasets at data.transportation.gov.
