EV Database Scraper

Scrape public electric vehicle listings and specifications from EV Database. The actor is intended for EV market research, comparison datasets, automotive analysis, and lead or inventory workflows that need consistent vehicle-level records.

What it extracts

Each dataset item represents one EV variant and includes:

Field group	Examples
Identity	vehicle ID, make, model, name, canonical vehicle URL
Index facts	availability, drive configuration, market segment, seats, heat pump, towing support, safety rating
Core metrics	real range, efficiency, curb weight, 0–100 km/h, one-stop range
Battery and utility	usable battery, fast-charge power, towing capacity, cargo volume
Pricing	displayed Germany, Netherlands, and UK prices plus price-per-range indicator
Optional details	sectioned tables for battery, charging, range, performance, efficiency, pricing, and other vehicle-page data

The source covers electric vehicles listed by EV Database, with regional indexes such as Europe and the UK. Values are published-source estimates and should not be treated as a substitute for manufacturer homologation or a live dealer quote.

Input

{
  "query": "Tesla Model 3",
  "market": "eu",
  "maxResults": 25,
  "includeDetails": true
}

query is optional and performs a case-insensitive match against the vehicle make and model. Leave it blank to scan the selected regional index. Supported markets are eu, uk, nl, de, fr, it, and es. maxResults accepts 1–500 and defaults to 25. includeDetails defaults to false; enabling it fetches one additional public page per returned vehicle. requestDelayMs controls pacing and defaults to 800 ms.

Pricing

This Actor uses Pay per event pricing:

Event	Price
Actor start	$0.00005
EV Database vehicle record	$0.005 per dataset record

The maximum event cost for the default 25-record run is $0.12505, excluding platform usage if the user enables Apify's pay-per-event + usage option. The Actor logs the cap at run start and stops when the user's spending limit is reached.

Output

The default mode writes compact index records. With includeDetails: true, specifications contains a stable object keyed by source section, for example:

{
  "vehicleId": "1319",
  "name": "Dacia Spring Electric",
  "vehicleUrl": "https://ev-database.org/car/1319/Dacia-Spring-Electric",
  "realRangeKm": 160,
  "usableBatteryKwh": 25,
  "fastChargePowerKw": 30,
  "specifications": {
    "battery": { "Battery Type": "Lithium-ion" },
    "charging": { "Fastcharge Port": "CCS" }
  },
  "scrapedAt": "2026-08-13T00:00:00.000Z"
}

The SUMMARY key-value record reports result count, selected market, detail mode, timestamp, and warnings. A valid query with no matches returns an empty dataset and a truthful warning.

Reliability and limits

The actor uses server-rendered HTML over public HTTP with bounded retries and a configurable delay. It does not log in, bypass access controls, use private APIs, or require user cookies. If the source returns an error or changes its markup, the run reports the failure rather than fabricating vehicle records. Detail-page failures are retained as warnings while valid index data is preserved.

Use a moderate result limit and respectful request delay for large detail runs. Confirm that your use of the source data complies with EV Database terms, licensing, and applicable law. The source also offers official data services for licensed or higher-volume integrations.

Local development

npm install
npm test

This project is local-ready after the TypeScript build and parser tests pass. Cloud deployment, pricing, and publication are intentionally separate owner-authorized steps.