# NHTSA Recall Manufacturer Leads (`infocomp/nhtsa-recall-manufacturer-leads`) Actor

One row per vehicle, tire or equipment manufacturer with NHTSA safety recalls in your date range: recall count, campaign numbers, top components, most recent recall date. Firm-level, no personal data. $3/1,000. Not an official NHTSA product.

- **URL**: https://apify.com/infocomp/nhtsa-recall-manufacturer-leads.md
- **Developed by:** [InfoComp Data](https://apify.com/infocomp) (community)
- **Categories:** Lead generation, Business, Automation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$3.00 / 1,000 manufacturer leads

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## NHTSA Recall Manufacturer Leads

See **which vehicle, tire and equipment manufacturers have safety recalls in the date range you choose**. Each row is
**one manufacturer** with its **recall count, NHTSA campaign numbers, the most-recalled components, brands, units
potentially affected and the date of its most recent recall**.

Built for people who sell to manufacturers under recall pressure: recall-management and notification services,
parts and supplier sales, quality and compliance software, field-service and repair networks, legal and insurance
analysts, and trade press tracking who is recalling right now.

> **Not an official NHTSA product.** Not affiliated with or endorsed by the National Highway Traffic Safety
> Administration (NHTSA), the U.S. Department of Transportation or any manufacturer. Data comes from NHTSA's public
> recall flat file. **NHTSA last updated the file on Nov 14, 2026** (newest recall report in it: Nov 12, 2026; NHTSA
> refreshes it daily). Recall details can change, so verify at [nhtsa.gov/recalls](https://www.nhtsa.gov/recalls) before you rely on them.

### What you get

- **One row per manufacturer** with at least one recall report received by NHTSA in your date range (the **default
  prefilled range, Aug 15 to today, returns 94 manufacturers**, you get the top 25 by default).
- `recall_count`: distinct NHTSA campaigns (a recall that covers many models counts once).
- `campaign_numbers` (newest first, up to 100) and `most_recent_recall_date`, `earliest_recall_date_in_range`.
- `top_components`: the most-recalled components with counts, plus `distinct_components`.
- `recall_types` (Vehicle, Tire, Equipment, Child seat), `top_brands` and `potential_units_affected` (NHTSA's
  per-campaign unit count, summed once per campaign).
- Sorted by recall count, highest first. Manufacturer spellings are merged (for example "General Motors, LLC" and
  "GENERAL MOTORS LLC"); other spellings are listed in `name_variants`.

#### Company-level data only (privacy)

This is a **company** list. No person-level data is read or output: no recall narratives, no owner or consumer
information, no VINs, no phones or emails. Names are the manufacturers NHTSA lists on the Part 573 recall report.

### Input

| Field | Default | What it does |
|---|---|---|
| Recalls received from | `2026-08-15` (prefilled; empty = 90 days before the end date) | First day of the range, YYYY-MM-DD. Uses the date NHTSA received the manufacturer's report. |
| Recalls received to | today | Last day of the range. |
| Recall types | all | Vehicle, Tire, Equipment, Child seat. |
| Manufacturer name contains | none | For example "ford", "trailer", "tire". |
| Minimum recalls | 1 | Keep manufacturers with at least this many campaigns in the range. |
| Max results | 25 | Stops after this many manufacturers, most recalls first. |

The default input returns 25 manufacturers in about 3 seconds.

Example: tire makers with recalls in 2026: `{"recallsFrom": "2026-01-01", "recallTypes": ["Tire"], "maxResults": 1000}`.
Example: every manufacturer with 3 or more recalls since 2025: `{"recallsFrom": "2025-01-01", "minRecalls": 3, "maxResults": 1000}`.

### Output sample

This row is real and untrimmed except that `top_components` is cut to 4 of 8 entries. It comes from a local default
run on Nov 14, 2026.

```json
{
  "manufacturer_name": "Daimler Trucks North America, LLC",
  "name_variants": [],
  "recall_count": 9,
  "most_recent_recall_date": "2026-11-06",
  "earliest_recall_date_in_range": "2026-08-24",
  "recall_types": [
    "Vehicle"
  ],
  "potential_units_affected": 22481,
  "top_components": [
    {
      "component": "Structure: Body",
      "recalls": 3
    },
    {
      "component": "Electronic Stability Control (Esc)",
      "recalls": 1
    },
    {
      "component": "Engine",
      "recalls": 1
    },
    {
      "component": "Equipment: Other: Labels",
      "recalls": 1
    }
  ],
  "distinct_components": 9,
  "top_brands": [
    "Freightliner",
    "Thomas Built Buses",
    "Fccc",
    "Western Star"
  ],
  "campaign_numbers": [
    "26V737000",
    "26V736000",
    "26V702000",
    "26V697000",
    "26V660000",
    "26V635000",
    "26V632000",
    "26V583000",
    "26V546000"
  ],
  "campaign_numbers_truncated": false,
  "source": "U.S. DOT / NHTSA Office of Defects Investigation recall flat file (static.nhtsa.gov/odi/ffdd/rcl/FLAT_RCL_POST_2010.zip, keyless public data).",
  "disclaimer": "Not an official NHTSA or U.S. DOT product. Not affiliated with or endorsed by NHTSA, the U.S. Department of Transportation or any manufacturer. Provided as-is from public NHTSA recall data; verify at nhtsa.gov/recalls.",
  "nhtsa_data_updated": "2026-11-14T08:04:52+00:00",
  "retrieved_at": "2026-11-14T17:01:35Z"
}
```

The dataset has an "Overview" table view and an "All fields" view. `RUN_SUMMARY` in the key-value store lists the filters, counts and data dates.

### Pricing

Pay per event: **`manufacturer-lead` at $0.003 per manufacturer row = $3.00 per 1,000 rows**. There is no start fee and no run fee.

- One row per manufacturer, however many recalls it has.
- Empty runs, failed runs and manufacturers filtered out are **free**, and those rows are not saved.
- The Actor respects the maximum cost you set for a run. It stops cleanly when it reaches the limit.

### How it works

The Actor downloads NHTSA's official recall flat file (about 15 MB zip, recalls since 2010), groups the lines by
manufacturer for your date range and returns the summary rows. It needs no key, login or proxy.
In local tests the default run took about 2.5 seconds, and the whole file (all 1,369 manufacturers since 2010) about 5 seconds.

### How this differs from our NHTSA VIN decoder

[NHTSA Bulk VIN Decoder: Specs, Recalls & MPG](https://apify.com/infocomp/bulk-vin-decoder-recalls-mpg) takes **VINs you
already have** and returns specs, open recalls and fuel cost per vehicle. This Actor takes **no VINs**: it lists the
**manufacturers** behind recalls in a date range, one row per firm. Use the decoder for vehicles, this one for companies.

### Data source and terms

- Source: NHTSA Office of Defects Investigation, recall flat file `FLAT_RCL_POST_2010.zip` (layout in `RCL.txt`), listed at nhtsa.gov/nhtsa-datasets-and-apis and on data.gov.
- NHTSA's Terms of Use say information on its site "is considered public information and may be distributed or copied". It is a U.S. government work, free to use, including commercially. We credit NHTSA anyway.
- NHTSA makes no warranty about accuracy or completeness; we pass the data on as-is.
- NHTSA credit and the not-an-official-NHTSA-product notice are on every row (`source`, `disclaimer`).

### More tools from InfoComp

- [NY DMV Auto Dealer & Repair Shop Leads](https://apify.com/infocomp/ny-dmv-dealer-repair-leads): New York car dealers, repair and body shops with license dates.
- [HUD Multifamily Owner/Manager Leads](https://apify.com/infocomp/hud-multifamily-leads): HUD-assisted apartment properties with the management company and contract expiry.
- [NHTSA Bulk VIN Decoder: Specs, Recalls & MPG](https://apify.com/infocomp/bulk-vin-decoder-recalls-mpg): decode fleets of VINs with open recalls and fuel cost.

### Limits

- Covers recalls NHTSA received since Jan 1, 2010. NHTSA updates the file daily, so the newest few days may be missing.
- The date is when NHTSA **received** the manufacturer's report, not when owners were notified or the recall was announced.
- "Manufacturer" is the name NHTSA lists for the recalled product. Some brands file under a parent or importer, and a few firms appear under more than one spelling beyond what we merge.
- A campaign that names several manufacturers is counted for each of them.
- Component names are NHTSA's categories, lightly re-cased (for example "Esc" for ESC).

# Actor input Schema

## `recallsFrom` (type: `string`):

First day of the date range, YYYY-MM-DD. Uses the date the manufacturer's recall report was received by NHTSA. Empty = 90 days before 'Recalls received to'.

## `recallsTo` (type: `string`):

Last day of the date range, YYYY-MM-DD. Empty = today.

## `recallTypes` (type: `array`):

Optional. Empty = all types.

## `nameContains` (type: `string`):

Optional. For example 'ford', 'trailer' or 'tire'.

## `minRecalls` (type: `integer`):

Keep manufacturers with at least this many recall campaigns in the range.

## `maxResults` (type: `integer`):

Stops after this many manufacturers (most recalls first). You pay $0.003 per manufacturer.

## Actor input object example

```json
{
  "recallsFrom": "2026-08-15",
  "recallTypes": [],
  "minRecalls": 1,
  "maxResults": 25
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `summary` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "recallsFrom": "2026-08-15",
    "maxResults": 25
};

// Run the Actor and wait for it to finish
const run = await client.actor("infocomp/nhtsa-recall-manufacturer-leads").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "recallsFrom": "2026-08-15",
    "maxResults": 25,
}

# Run the Actor and wait for it to finish
run = client.actor("infocomp/nhtsa-recall-manufacturer-leads").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "recallsFrom": "2026-08-15",
  "maxResults": 25
}' |
apify call infocomp/nhtsa-recall-manufacturer-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,infocomp/nhtsa-recall-manufacturer-leads"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/Qtaoo3TFyhGO0jpZh/builds/XPLMtTc6rx98aaQPg/openapi.json
