# EV Charging Stations Scraper - Connectors, Power & Operators (`ninhothedev/ev-charging-scraper`) Actor

$0.5/1K 🔥 EV charging station scraper! Locations, connectors, power output & operators worldwide. No key. JSON, CSV, Excel or API in seconds. Build EV apps & route planners ⚡

- **URL**: https://apify.com/ninhothedev/ev-charging-scraper.md
- **Developed by:** [ninhothedev](https://apify.com/ninhothedev) (community)
- **Categories:** Developer tools, Travel
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.50 / 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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## EV Charging Stations Scraper - Connectors, Power & Operators Worldwide

Scrape **EV charging stations anywhere in the world** - names, operators, addresses, GPS coordinates, connector types, maximum charging power in kW, AC/DC current, access rules and payment requirements - and export them as **JSON, CSV, Excel or XML**.

No API key. No login. No proxy. Give it a coordinate pair and a radius (or just a country code) and it returns clean, structured charging-station records.

***

### Why use this actor

Charging-infrastructure data is normally locked behind paid APIs with per-request quotas and restrictive licences. This actor pulls from a **fully open, keyless dataset** so you can build EV apps, plan routes, research charging deserts or scout new charge-point sites without signing up for anything.

- **Zero configuration** - works on the first run with the default input
- **Worldwide coverage** - any coordinates on Earth, or a whole country by ISO code
- **Connector-level detail** - Type 2, CCS, CHAdeMO, Tesla, Schuko, GB/T and more
- **Real power values** - max kW per station, derived from socket outputs or voltage/amperage
- **AC vs DC classification** - instantly filter fast chargers from slow AC posts
- **Permissive output schema** - never fails a run because a field is missing

***

### Data source

This actor uses the **OpenStreetMap Overpass API** (`amenity=charging_station`), which is public, keyless and community-maintained.

> **A note on Open Charge Map.** Open Charge Map's `/v3/poi` endpoint was evaluated as the primary source, but it now rejects anonymous requests with `403 - You must specify an API key using the key query parameter or x-api-key header`. Because this actor is designed to run with **zero setup and no credentials**, OpenStreetMap Overpass was chosen instead. Every item carries a `source` field (`"overpass"`) so downstream pipelines always know where the record came from.

The actor rotates over several public Overpass mirrors, so a single overloaded instance does not fail your run.

**Licence:** OpenStreetMap data is available under the [Open Database License (ODbL)](https://www.openstreetmap.org/copyright). If you publish or redistribute this data, credit "© OpenStreetMap contributors".

***

### Use cases

| Use case | How this actor helps |
|---|---|
| **EV charging apps & maps** | Seed or refresh your station database with coordinates, connectors and power ratings |
| **Route planning** | Find every charger along a corridor by running several radius searches and filtering on `max_power_kw` |
| **Charging infrastructure research** | Measure charger density, AC/DC split and operator market share per city or country |
| **Site selection** | Spot underserved areas before deciding where to install new charge points |
| **Fleet & logistics planning** | Check whether depots and delivery routes have adequate charging nearby |
| **Competitive intelligence** | Track which operators (Ionity, Tesla, EnBW, Shell Recharge...) dominate which regions |

***

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `mode` | select | `stations` | What to scrape. `stations` returns one item per charging station. |
| `latitude` | string | `"52.52"` | Latitude of the search centre in decimal degrees (-90 to 90). |
| `longitude` | string | `"13.405"` | Longitude of the search centre in decimal degrees (-180 to 180). |
| `radiusKm` | integer | `25` | Search radius in kilometres (1-100). |
| `countryCode` | string | `""` | Optional ISO-3166-1 alpha-2 code (`DE`, `NL`, `FR`, `US`...). When set, the whole country is scanned and lat/lon/radius are ignored. |
| `maxItems` | integer | `200` | Maximum number of stations to return (1-2000). |

#### Example - chargers around Berlin

```json
{
  "mode": "stations",
  "latitude": "52.52",
  "longitude": "13.405",
  "radiusKm": 25,
  "maxItems": 200
}
```

#### Example - chargers across the Netherlands

```json
{
  "mode": "stations",
  "countryCode": "NL",
  "maxItems": 2000
}
```

***

### Output

One dataset item per charging station. All fields are nullable - OpenStreetMap coverage varies by region, so treat a missing value as *unknown*, never as *zero*.

```json
{
  "station_id": "node/429740871",
  "name": "Innogy",
  "operator": "E.ON",
  "address": "Hardenbergstraße 12",
  "town": "Berlin",
  "state": null,
  "postcode": "10623",
  "country": "DE",
  "latitude": 52.5236617,
  "longitude": 13.3808678,
  "connection_count": 2,
  "connection_types": ["Type 2 (Mennekes)"],
  "max_power_kw": 22.2,
  "current_types": ["AC"],
  "total_points": 2,
  "is_operational": true,
  "usage_type": "Public (pay to use)",
  "pay_at_location": true,
  "membership_required": false,
  "phone": null,
  "access_comments": "Opening hours: 24/7 | Covered: no | Level: 0",
  "last_verified": "2025-04-11T00:00:00+00:00",
  "date_created": null,
  "source": "overpass",
  "scraped_at": "2026-07-28T14:02:11+00:00"
}
```

#### Field reference

| Field | Meaning |
|---|---|
| `station_id` | Stable OpenStreetMap identifier, e.g. `node/429740871` |
| `name` | Station title (falls back to brand, operator or reference number) |
| `operator` | Charging network operator (falls back to brand / network / owner) |
| `address`, `town`, `state`, `postcode`, `country` | Postal address components |
| `latitude`, `longitude` | WGS-84 coordinates (centroid for mapped areas) |
| `connection_count` | Total number of individual connectors |
| `connection_types` | Readable connector list: `Type 2 (Mennekes)`, `CCS Combo 2`, `CHAdeMO`, ... |
| `max_power_kw` | Highest advertised charging power in kW |
| `current_types` | `["AC"]`, `["DC"]` or both |
| `total_points` | Vehicles that can charge simultaneously |
| `is_operational` | `false` when tagged broken, disused or under construction |
| `usage_type` | Public / private classification plus free vs. pay to use |
| `pay_at_location` | Whether on-site payment (card, app, coins) is accepted |
| `membership_required` | Whether an RFID / membership card is needed |
| `phone` | Support phone number |
| `access_comments` | Free-text notes, opening hours, level, covered (max 1000 chars) |
| `last_verified` | Last survey / check date, ISO-8601 |
| `date_created` | Commissioning date, ISO-8601 |
| `source` | Always `"overpass"` - the live data source used |
| `scraped_at` | Run timestamp, ISO-8601 |

***

### Pricing

Roughly **$1 per 1,000 charging stations**, plus the usual Apify platform usage. A default Berlin run (200 stations) costs a few cents and finishes in well under a minute.

***

### Tips

- **Nothing found?** Increase `radiusKm`, move the coordinates closer to a city, or double-check the `countryCode`.
- **Only fast chargers?** Export to CSV and filter on `max_power_kw >= 50` or `current_types` containing `DC`.
- **Country runs are heavier.** Large countries take longer because the whole boundary is scanned; keep `maxItems` sensible.
- **Coverage varies.** Western Europe is extremely well mapped; some regions have coordinates but few connector details.

***

### Related actors

- [OSM Local Business Scraper](https://apify.com/ninhothedev/osm-local-business-scraper) - any business category from OpenStreetMap
- [CityBikes Scraper](https://apify.com/ninhothedev/citybikes-scraper) - bike-sharing networks and live station availability
- [Geocoding Scraper](https://apify.com/ninhothedev/geocoding-scraper) - turn addresses into coordinates and back
- [Energy Charts Scraper](https://apify.com/ninhothedev/energy-charts-scraper) - electricity generation, prices and grid data

***

### Legal

This actor reads publicly available OpenStreetMap data through the public Overpass API. No personal data is collected. Redistribution of the output is subject to the ODbL - attribute "© OpenStreetMap contributors".

# Actor input Schema

## `mode` (type: `string`):

What to scrape. 'stations' returns one dataset item per EV charging station, either around a coordinate pair or inside a whole country.

## `latitude` (type: `string`):

Latitude of the search centre in decimal degrees (-90 to 90). Used together with Longitude and Radius. Ignored when a Country code is given. Example: 52.52 for Berlin.

## `longitude` (type: `string`):

Longitude of the search centre in decimal degrees (-180 to 180). Used together with Latitude and Radius. Ignored when a Country code is given. Example: 13.405 for Berlin.

## `radiusKm` (type: `integer`):

Search radius around the centre coordinates in kilometres. Minimum 1, maximum 100. Larger radii return more stations but take longer to query.

## `countryCode` (type: `string`):

Optional ISO-3166-1 alpha-2 country code, e.g. 'DE', 'NL', 'FR', 'US'. When set, the whole country is scanned and Latitude/Longitude/Radius are ignored. Leave empty for a radius search.

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

Maximum number of charging stations to return. Minimum 1, maximum 2000. Keep it low for quick test runs.

## Actor input object example

```json
{
  "mode": "stations",
  "latitude": "52.52",
  "longitude": "13.405",
  "radiusKm": 25,
  "countryCode": "",
  "maxItems": 200
}
```

# Actor output Schema

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

// Run the Actor and wait for it to finish
const run = await client.actor("ninhothedev/ev-charging-scraper").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("ninhothedev/ev-charging-scraper").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 ninhothedev/ev-charging-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ninhothedev/ev-charging-scraper"
        }
    }
}

```

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/j5wEmXlSt0T0eGYTa/builds/HscXvwvPNwc6EfhHB/openapi.json