# Bulk VIN Decoder + NHTSA Recalls & Complaints (official API) (`mediapro-tools/bulk-vin-decoder-recalls`) Actor

Decode thousands of VINs with the official NHTSA vPIC API. No login. Export JSON/CSV/Excel. Pay only per result.

- **URL**: https://apify.com/mediapro-tools/bulk-vin-decoder-recalls.md
- **Developed by:** [Jeremy Yarbrough](https://apify.com/mediapro-tools) (community)
- **Categories:** Automation, Lead generation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

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

## Bulk VIN Decoder + NHTSA Recalls & Complaints (official API)

**Decode thousands of VINs with the official NHTSA vPIC API, with no login, no browser and no code. Export to JSON, CSV or Excel, or use the API.**

Decode thousands of VINs with the official NHTSA vPIC API: year, make, model, trim, body, drive, engine, fuel/EV level, plant and manufacturer, plus a local check-digit test. Adds NHTSA recall campaigns (with park-it warnings) and complaint counts for each make/model/year. Monitor mode alerts on new recalls for your fleet or inventory.

### Use cases

- Enrich dealer or auction inventory with full specs
- Flag vehicles with open-recall risk before purchase or listing
- Weekly recall monitoring for a fleet

### Input

| Field | Type | Notes |
|---|---|---|
| `vins` | array | 17-character VINs. |
| `includeRecalls` | boolean | NHTSA recalls for the decoded make/model/year. |
| `includeComplaintCount` | boolean |  |
| `monitorMode` | boolean | Remember recall campaigns per VIN; later runs flag new ones. |
| `onlyNewRecalls` | boolean | Monitor mode only. |
| `stateStoreName` | string |  |

### Example input

```json
{
 "vins": [
  "1HGCM82633A004352",
  "5YJ3E1EA7KF317000",
  "1FTFW1ET5DFC10312",
  "12345678901234567"
 ],
 "monitorMode": true
}
```

### Output

One dataset item per result. Main columns: `vin`, `modelYear`, `make`, `model`, `trim`, `bodyClass`, `driveType`, `engineCylinders`, `displacementL`, `fuelType`, `checkDigitValid`, `recallCount`, `parkItWarning`, `complaintCount`, `newRecallCampaigns`, `error`. A `RUN_SUMMARY` record is saved to the default key-value store. See the sample output in the Output tab.

### Example output

```json
{
  "vin": "1HGCM82633A004352",
  "checkDigitValid": true,
  "modelYear": 2003,
  "make": "HONDA",
  "model": "Accord",
  "trim": "EX-V6",
  "series": null,
  "bodyClass": "Coupe",
  "vehicleType": "PASSENGER CAR",
  "doors": 2,
  "driveType": null,
  "transmission": "Automatic",
  "engineCylinders": 6,
  "displacementL": 3,
  "engineHp": 240,
  "fuelType": "Gasoline",
  "electrificationLevel": null,
  "gvwr": "Class 1C: 4,001 - 5,000 lb (1,814 - 2,268 kg)"
}
```

### Pricing

Pay per result, with no monthly rental or subscription:

- **VIN decoded (with recalls)**: $0.002
- **New recall for a VIN (monitor)**: $0.01

Example: 1,000 results cost about $2.00 in fees. Apify's free plan includes $5 of monthly credit, which is enough to test this Actor.

### FAQ

**Do I need an account, cookies or a login for the source site?** No. Bulk VIN Decoder + NHTSA Recalls & Complaints uses public data sources only, so there is nothing to connect and no account to risk.

**How much will a run cost?** You pay only for results delivered (see Pricing above), plus Apify platform usage, which the free plan's monthly credit easily covers for test runs. Start with a small limit to see the exact cost per run.

**Can I export to CSV, Excel or Google Sheets?** Yes. Every run's dataset can be downloaded as JSON, CSV, Excel, XML or HTML, or pushed to Google Sheets, Make, Zapier, n8n, Slack or a webhook through Apify integrations.

**Can I run it on a schedule or from my own code?** Yes. Add an Apify Schedule (hourly, daily, weekly) or call it through the Apify API / Python & JavaScript clients. It also works with AI agents through the Apify MCP server.

**What happens if an input is invalid or a source is down?** The run keeps going. The bad input gets a row with an `error` field so you can see what failed, and you are not charged for results that were not delivered.

**Is this legal to use?** It collects publicly available data. You are responsible for using the output in line with the source's terms and privacy laws such as GDPR/CCPA; don't use it for spam.

**Something missing or broken?** Open an issue on the Issues tab. Feature requests are usually added within a few days.

### Scheduling / monitoring

Create a Schedule (daily/weekly) and connect a webhook or Slack/email integration.

### Fair use

Official public APIs only, no login. Do not use output for spam or harassment. Respect the data sources' rate limits and terms.

### Related tools

- [US Address Geocoder + Census Tract, County & FIPS](https://apify.com/mediapro-tools/us-address-geocoder-census)
- [Bulk Barcode Lookup: UPC/EAN to Product (Open Food Facts)](https://apify.com/mediapro-tools/barcode-upc-ean-product-lookup)
- [FDA Recalls Monitor: Food, Drug & Medical Device (openFDA API)](https://apify.com/mediapro-tools/fda-recalls-monitor)
- [Product Price Monitor for Any Store (schema.org) + Alerts](https://apify.com/mediapro-tools/product-price-monitor-any-store)

# Actor input Schema

## `vins` (type: `array`):

17-character VINs.

## `includeRecalls` (type: `boolean`):

NHTSA recalls for the decoded make/model/year.

## `includeComplaintCount` (type: `boolean`):

No description

## `monitorMode` (type: `boolean`):

Remember recall campaigns per VIN; later runs flag new ones.

## `onlyNewRecalls` (type: `boolean`):

Monitor mode only.

## `stateStoreName` (type: `string`):

No description

## Actor input object example

```json
{
  "vins": [
    "1HGCM82633A004352",
    "5YJ3E1EA7KF317000"
  ],
  "includeRecalls": true,
  "includeComplaintCount": true,
  "monitorMode": false,
  "onlyNewRecalls": false,
  "stateStoreName": "vin-recall-monitor"
}
```

# Actor output Schema

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

All result records in the default dataset (table view: overview).

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

Counts and stats for this run (JSON).

# 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 = {
    "vins": [
        "1HGCM82633A004352",
        "5YJ3E1EA7KF317000"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("mediapro-tools/bulk-vin-decoder-recalls").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 = { "vins": [
        "1HGCM82633A004352",
        "5YJ3E1EA7KF317000",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("mediapro-tools/bulk-vin-decoder-recalls").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 '{
  "vins": [
    "1HGCM82633A004352",
    "5YJ3E1EA7KF317000"
  ]
}' |
apify call mediapro-tools/bulk-vin-decoder-recalls --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,mediapro-tools/bulk-vin-decoder-recalls"
        }
    }
}
```

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/eJugB5bQuqs3NIeeN/builds/ccyMkYG3hG9qh9dqR/openapi.json