This is not our API. This repository is an independent, third-party profile of a company's publicly available API surface, maintained by API Evangelist. API Evangelist does not operate, host, resell, or support this company's APIs, and is not affiliated with or endorsed by the company unless stated on the profile.
Where the information came from. Everything here is assembled from material a member of the public can reach with a browser and no credentials — the company's own website, developer portal and documentation, the specifications it publishes for public use (OpenAPI, AsyncAPI, JSON Schema,
apis.json,llms.txtand similar), its public repositories, and its public status, pricing and changelog pages. Nothing here is obtained by breaching a system, defeating an access control, or using credentials of any kind.The rating is an independent assessment. The Kin Score and Agent Readiness rating are independently calculated scores of a company's public API artifacts, produced by API Evangelist against a published rubric. They are not certifications, endorsements, security assessments, or audits, and they score published artifacts — not the quality, safety, or security of the software.
Corrections, re-scores, and removal are free. No partnership, contract, or purchase is required, and you do not need to justify the request.
- Something wrong? Open an issue on this repository, or email info@apievangelist.com.
- Published something new? Ask for a re-score and we will re-run the rating.
- Want the listing taken down? Say so and we will honor it. The profile is reduced to your company name, a factual description, and a link to your own site, and the company is recorded as unrated — never scored zero for having asked.
Response times. Acknowledgement within one business day; removal or restriction within two business days; corrections and re-scores within five business days.
Not from the company, and here with a question? You are welcome here — we would rather be the front line and point you the right way than have a good report go nowhere. What this repository can answer is narrow, though, so it is worth knowing who you are actually looking for:
- A question about how the API works, an account, billing, or a bug in the service — that is the company's own support, not us. We profile this API; we do not operate it and cannot see your account.
- A bug in an open-source project we only catalog — file it on that project's own repository. This has happened with a real and correct bug report that reached us instead of the people who could fix it, which helped nobody.
- Anything about this listing itself — the description, the tags, the rating, a missing or wrong artifact — is ours. Open an issue here.
- Not sure, or something general about API Evangelist or APIs.io — open an issue on the APIs.io Inbox and we will route it.
This repository contains no software, and we will never ask you to download anything. There is no build, release, installer, or binary here — only text and machine-readable API descriptions, so there is nothing here that can be "corrupt" or need "repairing". Any issue, comment, or email claiming otherwise and offering a download link is not from us and is hostile. Do not follow the link; it is a lure. Report it to GitHub and, if you like, tell us at info@apievangelist.com so we can take it down.
On a security or compliance team? Email info@apievangelist.com with 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 so your team can see the same surface we did, and we will take the listing down on request while you work through it.
Full detail: Where this data comes from
Ofgem, the Office of Gas and Electricity Markets, is the non-ministerial government department that regulates the gas and electricity markets of Great Britain (England, Scotland and Wales), drawing its powers from the Gas Act 1986, the Electricity Act 1989 and the Energy Act 2023. It licenses the companies that make, transport and sell energy, sets the price cap, runs the RIIO network price controls, administers environmental and social schemes such as the Renewables Obligation, REGO and Feed-in Tariffs on behalf of government, grants and supervises the Smart Meter Communication Licence held by the Smart DCC, and imposes the Data Best Practice licence obligation that requires network licensees to treat Energy System Data as presumed open. It sits above the value chain rather than in it — it holds no customers, no meters and no wires. Its own API posture is the plain finding: Ofgem publishes no API of any kind. There is no developer portal, no api., docs., data. or developer. subdomain, no OpenAPI, no CKAN endpoint. Market data is genuinely open but delivered as chart images, CSV and XLSX file downloads from the Ofgem Data Portal; consumer data does not exist here at all, because Great Britain mandated the smart-meter infrastructure rather than a consumer data right, and no CDR-equivalent obligation binds either Ofgem or the suppliers it licenses. Ofgem's two operational registers — the Electronic Public Register and the Renewable Electricity Register — are login-gated applications whose backends are undocumented and unpublished. Ofgem is therefore a regulator that demands open, discoverable, interoperable data from the industry it supervises while shipping none of it programmatically itself.
APIs.json: https://raw.githubusercontent.com/api-evangelist/ofgem/refs/heads/main/apis.yml
- Energy
- United Kingdom
- Utilities
- Electricity
- Gas
- Energy Markets
- Regulator
- Smart Metering
- Open Data
- Energy Regulation
- Renewables
- Great Britain
- Created: 2026-07-27
- Modified: 2026-07-27
None. Ofgem publishes no documented public API.
Every developer-facing host was probed on 2026-07-27 and none resolves: api.ofgem.gov.uk, developer.ofgem.gov.uk, developers.ofgem.gov.uk, docs.ofgem.gov.uk, data.ofgem.gov.uk, portal.ofgem.gov.uk, open.ofgem.gov.uk, opendata.ofgem.gov.uk, dsi.ofgem.gov.uk, dataexchange.ofgem.gov.uk. Every developer-facing path on the main site returns 404, including /developers, /api, /data, /openapi.json, /swagger.json, /jsonapi, /graphql and /llms.txt. No OpenAPI, AsyncAPI, GraphQL schema or Postman collection exists to harvest, so no openapi/ directory is present in this repo.
| Mandate regime | smart-meter-infrastructure — Ofgem grants and regulates the Smart Meter Communication Licence held by Smart DCC Ltd and oversees the Smart Energy Code. Ofgem administers this regime; it is not a data holder under it. |
| Mandate status | live-implemented — the regime and Ofgem's own licence-condition data obligations are in force and verified (Data Best Practice Guidance v1.0, November 2021, fetched at HTTP 200; live Electronic Public Register at HTTP 200). This says nothing about an API. Ofgem implemented no API. |
| Consumer data right | None. Great Britain has no CDR-energy, no Green Button regulation, no accredited-recipient scheme. DESNZ's energy smart data call for evidence (January 2025) under the Data (Use and Access) Act 2025 and Ofgem's Consumer Consent Decision (OFG1164, April 2025) are policy work, not endpoints. |
| Data standard | No standard reference found — no Green Button/ESPI, no CDR Consumer Data Standards, no IEC CIM, no IEEE 2030.5, no OpenADR, no OCPP/OCPI. |
| Market data | Open and anonymous, but as files. The Ofgem Data Portal publishes charts with PNG and CSV downloads across retail, wholesale, network and customer-service indicators; price cap levels and FIT installation reports are XLSX. |
| Consumer data API | None, and structurally so — a regulator holds no meters, no accounts and no consumption records. |
| Access gate | none-published — no developer portal, no key request, no application route, no accreditation, no data licence. The Data Exchange Service is the only Ofgem system that mentions an API and it is inbound-only, in Beta, and invitation-only (ofgemdataservices@ofgem.gov.uk). |
| Auth model | No public API to authenticate against. The Electronic Public Register uses OAuth 2.0 authorization code + PKCE via AWS Cognito; the Renewable Electricity Register uses OpenID Connect authorization code + PKCE via Azure AD B2C. No OIDC discovery document is served anywhere. |
| Home market | United Kingdom (Great Britain — England, Scotland, Wales). |
Ofgem's Data Best Practice licence condition works — on everyone except Ofgem. The "presumed open" obligation Ofgem placed on RIIO-price-controlled licensees produced NESO's public CKAN API and the DNO open-data portals. The regulator that wrote the rule ships spreadsheets.
- Website
- About
- Data Portal
- Data
- Data release calendar
- Digitalisation
- Data Best Practice Guidance v1.0
- Electronic Public Register
- Renewable Electricity Register
- Vulnerability disclosure
- security.txt
- News
- Blog
- RSS
- Publications
Enrichment round 2026-07-27. Ofgem publishes no API, so there is no openapi/, asyncapi/, mcp/, packages/, sandbox/, errors/ or skills/ directory — none could be produced without fabricating one. What follows is what was actually found on the wire.
| Artifact | Method | What it records |
|---|---|---|
well-known/ofgem-well-known.yml |
searched | Every /.well-known/ path probed across six Ofgem-operated hosts, with status. Two documents exist in the whole estate. |
well-known/ofgem-security.txt |
searched | RFC 9116 document, saved verbatim. HackerOne submission route plus the disclosure policy. |
well-known/ofgem-rer-openid-configuration.json |
searched | New this round. A live OpenID Connect discovery document, served by the Azure AD B2C tenant behind the Renewable Electricity Register. Saved verbatim. |
graphql/ofgem-epr-operations.graphql |
derived | New this round. The 48 queries, 21 mutations and 3 fragments the Electronic Public Register web app sends, extracted verbatim from Ofgem's own public JavaScript bundle. Server-side introspection is disabled, so the SDL itself is unobtainable. |
graphql/ofgem-epr-graphql.yml |
derived | The surface record for that endpoint, including the anonymous-read verification. |
authentication/ofgem-authentication.yml |
searched | The identity layer in front of both registers — AWS Cognito (EPR) and Azure AD B2C (RER), both authorization code with PKCE. No public API auth exists. |
scopes/ofgem-scopes.yml |
searched | The OAuth/OIDC scopes the register applications request of their own IdPs. Not grantable to third parties. |
conformance/ofgem-conformance.yml |
derived | Standards assessment, including the energy data standards (Green Button/ESPI, CDR, IEC CIM, IEEE 2030.5, OpenADR, OCPP/OCPI, CKAN, DCAT) Ofgem does not use — and Ofgem's partial conformance to its own Data Best Practice guidance. |
lifecycle/ofgem-lifecycle.yml |
searched | No API versioning, no deprecation policy, no SLA, no status page (status.ofgem.gov.uk does not resolve). The data release calendar is the only cadence commitment. |
security/ofgem-domain-security.yml |
probed | TLS/HSTS across four hosts, plus DNSSEC/CAA/SPF/DMARC for ofgem.gov.uk. HSTS is set on the corporate site and on none of the three register hosts; no DNSSEC, no CAA; DMARC p=reject. |
security/ofgem-vulnerability-disclosure.yml |
searched | security.txt-backed disclosure route. |
llms/ofgem-llms.txt |
generated | Agent-facing summary. Ofgem serves no /llms.txt — https://www.ofgem.gov.uk/llms.txt returns 404. |
Two things turned up that the first pass did not have. First, a real OpenID Connect discovery document is live for the Renewable Electricity Register — the only machine-readable contract of any kind anywhere in Ofgem's estate, and it is served by Microsoft on Ofgem's tenant rather than by Ofgem. Second, the Electronic Public Register's GraphQL backend at https://epre-api.ofgem.gov.uk/graphql/ answers anonymously with real register content — GetCollectionsAndPublications returned 12 licence collections and GetAnnouncements returned live licensing notices, with no cookie, key or token. Introspection is disabled, but the full client operation set sits in Ofgem's own public JS bundle.
That surface is deliberately not listed as an API in apis.yml. Ofgem publishes no schema, no reference, no terms of use, no rate limits and no versioning promise for it, and cataloguing an undocumented application backend as a published API would misrepresent the posture this repo exists to record. The finding is sharper than "no API": Ofgem is already serving public register data over a machine-readable interface and has simply never published it as one.
- Kin Lane — kin@apievangelist.com