# Electromaps Scraper (`reventadata/electromaps-scraper`) Actor

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

## Pricing

from $1.00 / 1,000 stations

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

## Electromaps Scraper — EV Charging Stations & Connectors

> **Unofficial.** This Actor is not affiliated with, authorised by, endorsed by,
> or in any way officially connected to Electromaps.
> "Electromaps" is a trademark of its respective owner and is used here only to
> describe what this tool reads.

Charging stations inside any bounding box with **connector mix, power levels,
ratings, opening hours and published prices** — the coverage-map picture for
Electromaps in one call.

### Input

| Field | What it does |
|---|---|
| `bboxWest/bboxSouth/bboxEast/bboxNorth` | Search box, WGS84 degrees. |
| `locationTypes` | Site filter (`ON_STREET`, `PARKING`, `HOTEL`, …); omit for all. |
| `minPowerKw` | Minimum connector power in kW (0 = off). |
| `connectors` | Connector filter (`IEC_62196_T2`, `CHADEMO`, …); empty = off. |
| `realtimeOnly` | Only realtime-capable stations (sharply fewer rows). |
| `maxItems` | Station cap. |
| `fetchDetails` | Per-station connectors/ratings/prices (on by default). |
| `proxyConfiguration` | Optional Apify Proxy; direct calls are the default. |

### Output

One row per station:

```json
{
  "id": 307432,
  "name": "Ribes Roges 11 Vilanova i la Geltrú",
  "city": "Vilanova i la Geltrú",
  "offlineStatus": "WORKING",
  "maxPowerKw": 22,
  "chargePrice": "Gratuito"
}
```

(Sample from a real run, 2026-09-22.)

### FAQ

**Is availability live?** Only where the site reports it: rows carry the
`realtime` flag, and connector statuses are crowdsourced verbatim
(`UNKNOWN` stays `UNKNOWN`) unless the station reports live.

# Actor input Schema

## `bboxWest` (type: `number`):

Western edge of the search box, WGS84 decimal degrees (-180 to 180).

## `bboxSouth` (type: `number`):

Southern edge of the search box, WGS84 decimal degrees (-90 to 90).

## `bboxEast` (type: `number`):

Eastern edge of the search box, WGS84 decimal degrees. Must be greater than the west edge.

## `bboxNorth` (type: `number`):

Northern edge of the search box, WGS84 decimal degrees. Must be greater than the south edge.

## `locationTypes` (type: `array`):

Site-location filter (ON\_STREET, PARKING, HOTEL, MALL, …). Unknown values are rejected by the site with HTTP 403; omit for all types.

## `minPowerKw` (type: `integer`):

Minimum connector power threshold in kW. 0 disables the filter.

## `connectors` (type: `array`):

Connector filter, e.g. IEC\_62196\_T2, CHADEMO. Empty disables the filter.

## `realtimeOnly` (type: `boolean`):

When true, the site returns only realtime-capable stations (a server-side filter, sharply fewer rows).

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

Hard cap on stations processed (search hits and detail fetches). Keep low for the daily QA run.

## `fetchDetails` (type: `boolean`):

When true, each station's detail endpoint is called for connectors, ratings and prices. When false, only search-level fields are emitted.

## `proxyConfiguration` (type: `object`):

Optional Apify Proxy for the API calls. The API answers direct calls; enable residential if direct egress is refused.

## Actor input object example

```json
{
  "bboxWest": 1.7227,
  "bboxSouth": 41.2135,
  "bboxEast": 1.724,
  "bboxNorth": 41.2145,
  "locationTypes": [
    "ON_STREET",
    "PARKING"
  ],
  "minPowerKw": 0,
  "connectors": [],
  "realtimeOnly": false,
  "maxItems": 10,
  "fetchDetails": true,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `stations` (type: `string`):

Charging stations: connector mix, power, ratings, hours and published prices.

# 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 = {
    "bboxWest": 1.7227,
    "bboxSouth": 41.2135,
    "bboxEast": 1.724,
    "bboxNorth": 41.2145,
    "locationTypes": [
        "ON_STREET",
        "PARKING"
    ],
    "minPowerKw": 0,
    "connectors": [],
    "realtimeOnly": false,
    "maxItems": 10,
    "fetchDetails": true
};

// Run the Actor and wait for it to finish
const run = await client.actor("reventadata/electromaps-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 = {
    "bboxWest": 1.7227,
    "bboxSouth": 41.2135,
    "bboxEast": 1.724,
    "bboxNorth": 41.2145,
    "locationTypes": [
        "ON_STREET",
        "PARKING",
    ],
    "minPowerKw": 0,
    "connectors": [],
    "realtimeOnly": False,
    "maxItems": 10,
    "fetchDetails": True,
}

# Run the Actor and wait for it to finish
run = client.actor("reventadata/electromaps-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 '{
  "bboxWest": 1.7227,
  "bboxSouth": 41.2135,
  "bboxEast": 1.724,
  "bboxNorth": 41.2145,
  "locationTypes": [
    "ON_STREET",
    "PARKING"
  ],
  "minPowerKw": 0,
  "connectors": [],
  "realtimeOnly": false,
  "maxItems": 10,
  "fetchDetails": true
}' |
apify call reventadata/electromaps-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,reventadata/electromaps-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/Ha0Cv3DG34LbCJ3Qk/builds/HPRNUW9Z8fkPPheoF/openapi.json