# UK EV Charge Points – Statutory Open Data (OCPI, PCPR 2023) (`denjino/uk-ev-chargepoints-open-data`) Actor

Live UK public EV charge point locations, connectors, power, live status and tariffs from operators' statutory open-data feeds under the Public Charge Point Regulations 2023. No API key needed.

- **URL**: https://apify.com/denjino/uk-ev-chargepoints-open-data.md
- **Developed by:** [John Martinez](https://apify.com/denjino) (community)
- **Categories:** Open source, Travel, Automation
- **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

## UK EV Charge Points – Statutory Open Data (OCPI)

Get UK public EV charge points as a clean table: site, address, postcode, coordinates, EVSE ID, connector type, power (kW), **live status** and **price per kWh**. The data comes straight from operators' official open-data feeds, which the **Public Charge Point Regulations 2023** require them to publish free and without terms. There's no scraping of apps and no API key.

### Who it's for

- **Charging apps, fleet and route planners**: refresh connector status and tariffs on a schedule.
- **Property, retail and site-selection teams**: map charger density and gaps by postcode.
- **Local authorities, consultancies and researchers**: track reliability (FAULTED / OUTOFORDER), on-street rollout and pricing.
- **Competitor analysis for CPOs**: see a rival network's footprint and pence-per-kWh pricing.

### What you get (one row per connector)

`operator, partyId, locationId, locationName, address, city, postalCode, latitude, longitude, parkingType, evseId, status, connectorStandard, powerType, maxPowerKw, pricePerKwh, currency, openingTimes24x7, lastUpdated`

```json
{"operator":"char.gy","locationName":"64 Plympton Road","postalCode":"NW6 7EQ","evseId":"GB*CGY*E*00155","status":"WORKING","connectorStandard":"IEC_62196_T2","powerType":"AC_1_PHASE","maxPowerKw":5.1,"pricePerKwh":0.45,"currency":"GBP","latitude":51.5427,"longitude":-0.2045}
```

### Built-in keyless feeds

- **char.gy**: about 6,000 on-street sites.
- **Monta**: UK public open data.

**Bring your own feeds:** some operators (Gridserve, InstaVolt, bp pulse, Shell Recharge and others via Eco-Movement) issue a free key on request. Add them under *Extra OCPI feeds* with your key, and the actor will normalise them into the same table. Your key is only used during your run.

### Filters

Postcode prefixes (e.g. `N15`, `M1`), minimum power (e.g. `50` for rapid only), EVSE statuses, and max results.

### Pricing

Pay per result: **$1.00 per 1,000 connector rows**, plus a small $0.005 start fee per run. For example, a London-wide refresh of about 3,000 rows costs about $3.

### Notes

- Statuses follow OCPI (`AVAILABLE, CHARGING, FAULTED, OUTOFORDER, REMOVED…`). Some feeds publish `WORKING` instead of live availability.
- Sites anonymised by the operator (typically residential) are skipped. No personal data is collected.
- Source data is published under the Public Charge Point Regulations 2023, reg. 10. Accuracy is the operator's responsibility.

# Actor input Schema

## `sources` (type: `array`):

Keyless statutory feeds to read.

## `customFeeds` (type: `array`):

Other operators' OCPI locations endpoints you have access to, e.g. \[{"name":"Gridserve","url":"https://api.gridserve.com/ocpi/v1/locations","headers":{"ec-subscription-key":"YOUR_KEY"}}]. Keys are used only for your run.

## `postcodePrefixes` (type: `array`):

Only keep sites whose postcode starts with one of these (e.g. N15, M1, EH). Empty = all UK.

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

e.g. 50 for rapid only.

## `statuses` (type: `array`):

Only keep connectors whose EVSE has one of these statuses. Empty = all except REMOVED.

## `includeTariffs` (type: `boolean`):

Resolve tariff_ids to price per kWh where the feed publishes tariffs.

## `maxResults` (type: `integer`):

Stop after this many connector rows (0 = no limit).

## Actor input object example

```json
{
  "sources": [
    "chargy"
  ],
  "customFeeds": [],
  "postcodePrefixes": [],
  "minPowerKw": 0,
  "statuses": [],
  "includeTariffs": true,
  "maxResults": 1000
}
```

# Actor output Schema

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

One row per connector: operator, location, address, coordinates, status, connector standard, power and tariff.

# 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("denjino/uk-ev-chargepoints-open-data").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("denjino/uk-ev-chargepoints-open-data").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 denjino/uk-ev-chargepoints-open-data --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,denjino/uk-ev-chargepoints-open-data"
        }
    }
}
```

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/8cMGfHTNw9wMDf8qT/builds/al7cijwQIG1hvgaQr/openapi.json