ScottishPower
ScottishPower (Scottish Power Limited, Glasgow) is one of the "Big Six" British energy companies and has been wholly owned by Spain's Iberdrola since 2007. It is unusual in the post-liberalisation UK market for still spanning three regulated roles at once: ScottishPower Energy Retail supplies electricity and gas to millions of British homes and businesses; SP Energy Networks is the licensed distribution network operator for central and southern Scotland (SP Distribution), Merseyside, Cheshire and North Wales (SP Manweb), plus the transmission owner for southern Scotland (SP Transmission); and ScottishPower Renewables develops and operates onshore and offshore wind. That structure produces the sharpest possible version of this sector's split, and the split is the finding. On the consumer side there is nothing — Britain has no Consumer Data Right, no Green Button mandate and no consumer energy data-portability obligation of any kind, and ScottishPower publishes no developer portal, no self-serve API programme and no documented way for a third party to obtain an individual customer's usage or billing data. developer.scottishpower.co.uk, developers.scottishpower.co.uk, data.scottishpower.co.uk and docs.scottishpower.co.uk do not resolve at all, api.scottishpower.co.uk exists in DNS but returns HTTP 403, and www.scottishpower.co.uk returns HTTP 403 to every anonymous client on every path including /robots.txt. The only public account of ScottishPower's API programme is a WSO2 customer story describing an API Manager deployment used to expose services to commercial partners — an internal, partner-gated estate, not a developer programme. On the network side the picture inverts completely. Ofgem's Data Best Practice Guidance, made a licence condition under the RIIO-ED2 price control (Special Licence Condition 9.5), obliges electricity network licensees to treat their data as "presumed open", and SP Energy Networks has actually built that: the SP Energy Networks Open Data Portal at spenergynetworks.opendatasoft.com serves 150 datasets — embedded capacity register, network flow, historic substation demand, LV monitoring, smart-meter penetration, generation heat maps, flexibility and connections data — through a live, fully anonymous Opendatasoft Explore API v2.1 with a real OpenAPI 3.0.3 contract, CORS wide open, a 5,000 request/day anonymous quota, a DCAT-AP catalogue export, and an SP Energy Networks Open Data Licence based on Creative Commons Attribution 4.0. Britain mandated the infrastructure and the network data, not the data right — ScottishPower is the proof. Its smart-meter obligation runs through the Smart DCC and the Smart Energy Code, which is an infrastructure monopoly for licensed parties rather than a consumer data right, and no public register entry or endpoint for that obligation could be verified from outside.
ScottishPower publishes 2 APIs on the APIs.io network: Catalog API and Dataset API. Tagged areas include Energy, United Kingdom, Utilities, Electricity, and Gas.
ScottishPower’s developer surface includes authentication, changelog, code examples, API reference, getting-started guide, signup flow, documentation, and 32 more developer resources.
Kin Score
APIs 3
Individual APIs this provider publishes, each with its own machine-readable definition.
SP Energy Networks Open Data Search API (v1.0)
The legacy Opendatasoft Search API v1.0 still served alongside Explore v2.1 on the SP Energy Networks Open Data Portal. Verified anonymously on 2026-07-27: GET /api/datasets/1.0...
ScottishPower Catalog API
API to enumerate datasets
ScottishPower Dataset API
API to work on records
Open Collections 1
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Explore API
OPEN COLLECTIONRate Limits 1
Documented rate limits and quota policies.
Scottishpower Rate Limits
RATE LIMITSExamples 3
Example request and response payloads for these APIs.
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 5
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll for all 7
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 6
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 3
Properties that don't map to a standard resource type
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.