# Dutch License Plate Lookup (RDW) (`memorable_alphabet/rdw-vehicle-lookup`) Actor

Look up Dutch vehicles by license plate (kenteken) or search the national register by make, model and dates. Official RDW open data joined into one record: specs, APK expiry, odometer verdict, fuels and emissions, open recalls. No proxy or login.

- **URL**: https://apify.com/memorable_alphabet/rdw-vehicle-lookup.md
- **Developed by:** [Mathieu](https://apify.com/memorable_alphabet) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 results

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

## Dutch License Plate Lookup (RDW)

Look up Dutch vehicles by license plate (kenteken), or search the national vehicle register by make,
model, color and dates. The data is the RDW's official open data, joined into one record per vehicle:
specifications, APK (MOT) expiry, the full APK inspection history with every defect found,
odometer verdict, registration flags, fuels with emissions, and recalls. No proxy, no login, no scraping.

### Use cases

- **Used-car checks:** APK validity and the inspection history (what failed, when), odometer verdict (`Logisch` / `Onlogisch`), open recalls, export
  and taxi history, whether the car is insured (WAM) and can be registered.
- **Dealers, importers and fleets:** enrich a list of plates in bulk, or find vehicles by make, model and
  first-admission year.
- **Garages and marketing apps:** find vehicles whose APK expires in a date range.
- **Apps and insurers:** structured specs and emissions for a plate, ready for JSON, CSV or Excel.

### Input

| Field | Description |
|---|---|
| `licensePlates` | Plates in any format (`GX-Z86-T`, `gxz86t`). If set, the search filters are ignored. |
| `make` / `model` | Make (exact, case-insensitive) and model (matched anywhere in the name). |
| `vehicleType` | Passenger car, commercial vehicle, motorcycle, moped, bus, trailer, ... |
| `color` | Main color in the register's Dutch wording (`ZWART`, `WIT`, `GRIJS`, ...). |
| `firstAdmissionFrom` / `firstAdmissionTo` | First-admission date range, `YYYY-MM-DD`. |
| `apkExpiresFrom` / `apkExpiresTo` | APK expiry date range, `YYYY-MM-DD`. |
| `includeFuel` / `includeRecalls` / `includeInspections` | Add fuels and emissions / recalls / APK inspection history (all default on). |
| `maxItems` | Cap on vehicles returned. Default `100`. |
| `appToken` | Optional free RDW app token for higher rate limits on very large runs. |

A search needs at least one filter. Plates that are not in the register are listed in the run's
Key-Value store under `NOT_FOUND_PLATES` and are not charged.

### Output (one row per vehicle)

`plate`, `vehicleType`, `make`, `model`, `bodyType`, `color`, `secondColor`, `seats`, `doors`,
`cylinders`, `engineCapacityCc`, `emptyMassKg`, `kerbMassKg`, `maxMassKg`, `towingBrakedKg`,
`towingUnbrakedKg`, `lengthCm`, `widthCm`, `wheelbaseCm`, `catalogPriceEur`, `bpmEur`,
`firstAdmissionDate`, `firstRegistrationNlDate`, `lastRegistrationDate`, `apkExpiryDate`, `apkValid`,
`insured`, `exported`, `taxi`, `canBeRegistered`, `odometerVerdict`, `odometerYear`,
`euVehicleCategory`, `typeApprovalNumber`, `fuels`, `openRecallCount`, `recalls`, and with
`includeInspections`: `inspectionCount`, `lastInspectionDate`, `defectsFoundTotal`, `inspections`.

- `fuels`: one entry per fuel (`type`, `emissionClass`, `co2GramPerKm`, `consumptionLPer100Km`,
  `powerKw`, `electricPowerKw`, `hybridClass`). Hybrids list petrol and electricity separately.
- `recalls`: `referenceCode`, `statusCode` (`O` open, `P` producer reports repair), `status`,
  `publishedDate`, `manufacturer`, `defect`, `category`, `consequences`, `remedy`, `hazards`.
- `inspections` (newest first): `date`, `time`, `inspectionType` (for example `APK Lichte voertuigen`),
  `notificationType` (for example `periodieke controle`), `newExpiryDate`, and `defects`: each with
  `id`, `description` (the RDW's wording in force on the inspection date), `articleNumber` and `count`.
  These are the notifications garages send to the RDW; a notification with no defects means none were
  reported. Very old inspections may be missing.
- Values the register does not hold come back as `null`. The register does not hold the owner or
  any personal data; this Actor returns vehicle data only.

### Notes

- Source: RDW open data (opendata.rdw.nl), which updates daily. Data reflects the register, not a
  physical inspection.
- `apkValid` compares the APK expiry date with today's date when the run executes.

# Actor input Schema

## `licensePlates` (type: `array`):

Dutch license plates (kenteken), any format: GX-Z86-T, gxz86t. Up to thousands per run. If set, the search filters below are ignored.

## `make` (type: `string`):

Search by make, e.g. TESLA, VOLKSWAGEN, MERCEDES-BENZ. Upper or lower case.

## `model` (type: `string`):

Search by model name, matched anywhere in the name, e.g. MODEL 3, GOLF.

## `vehicleType` (type: `string`):

Type of vehicle in the register.

## `color` (type: `string`):

Main color in the register's Dutch wording, e.g. ZWART, WIT, GRIJS, BLAUW, ROOD.

## `firstAdmissionFrom` (type: `string`):

Only vehicles first admitted on or after this date. Format YYYY-MM-DD.

## `firstAdmissionTo` (type: `string`):

Only vehicles first admitted on or before this date. Format YYYY-MM-DD.

## `apkExpiresFrom` (type: `string`):

Only vehicles whose APK (MOT) expires on or after this date. Format YYYY-MM-DD.

## `apkExpiresTo` (type: `string`):

Only vehicles whose APK (MOT) expires on or before this date. Format YYYY-MM-DD.

## `includeFuel` (type: `boolean`):

Add the fuel list with emission class, CO2 and power per vehicle.

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

Add recalls (open and repaired) with the RDW's description per vehicle.

## `includeInspections` (type: `boolean`):

Add every APK/inspection notification per vehicle (date, type, new expiry date) with the defects found and their descriptions.

## `maxItems` (type: `integer`):

Cap on the number of vehicles returned.

## `maxRequestRetries` (type: `integer`):

Retries per failed request to the RDW, with growing waits.

## `appToken` (type: `string`):

Optional free app token from opendata.rdw.nl for higher rate limits on very large runs.

## Actor input object example

```json
{
  "licensePlates": [],
  "vehicleType": "",
  "includeFuel": true,
  "includeRecalls": true,
  "includeInspections": true,
  "maxItems": 100,
  "maxRequestRetries": 3
}
```

# Actor output Schema

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

All vehicles found as a dataset.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("memorable_alphabet/rdw-vehicle-lookup").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("memorable_alphabet/rdw-vehicle-lookup").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 '{}' |
apify call memorable_alphabet/rdw-vehicle-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,memorable_alphabet/rdw-vehicle-lookup"
        }
    }
}
```

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/LkWTpYKFb7OCz1ma2/builds/5drl7QMH7x0YBiBHj/openapi.json