SP Energy Networks Open Data Explore API
The live, anonymous REST API behind the SP Energy Networks Open Data Portal — ScottishPower's regulated distribution and transmission arm publishing its network data under Ofgem's Data Best Practice "presumed open" licence condition. Implements the Opendatasoft Explore API v2.1 contract (OpenAPI 3.0.3, 16 paths) over a catalogue of 150 datasets covering the embedded capacity register, network flow, historic substation demand curves, LV monitoring, smart-meter penetration by transformer, secondary substations, generation heat maps, connections insight and per-dataset data-quality scores. Verified on 2026-07-27 with no API key and no account: GET /catalog/datasets returned HTTP 200 with total_count 150, access-control-allow-origin "*", and x-ratelimit-limit 5000 with x-ratelimit-remaining 4990 resetting daily. Records, facets, attachments and exports (CSV, Parquet, GPX, DCAT-AP RDF/XML) are all served from the same base URL. An optional apikey query parameter, obtainable from a free self-serve portal account, raises quotas; none is required for public datasets. Data is published under the SP Energy Networks Open Data Licence, which the portal states is based on the Creative Commons Attribution 4.0 International Public Licence.
SP Energy Networks Open Data Explore API is one of 2 APIs that ScottishPower publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Open Data, Energy, Electricity, Grid, and Distribution Network Operator. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, and a getting-started guide.
This API exposes 16 operations across 16 paths, organized into 2 resource areas, and defines 9 schemas. It is described by OpenAPI 3.0.3, at version v2.1.
Requests are made against a single base URL, https://spenergynetworks.opendatasoft.com/api/explore/v2.1.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
SP Energy Networks Open Data Explore API declares
1 security scheme
for authenticating requests.
An API key is passed in the query as apikey (apikey).
By default, every request must be authenticated.
apikey— API key to make authenticated requests.
Paths & Operations 16
Across 16 paths, the API surfaces 16 operations — 16 GET. They span 2 resource areas: Catalog, Dataset. Each is listed below with its method, path, parameters, and response codes.
API to enumerate datasets
API to work on records
Schemas 9
The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are dataset (9 properties), record (4 properties), facet_value_enumeration (4 properties), datasets (3 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from ScottishPower 1
Other APIs ScottishPower publishes across the network.
This is an independent, third-party profile of SP Energy Networks Open Data Explore API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.