Utilita Status API
Public, anonymous, read-only JSON API reporting the live operational state of Utilita Energy's services. Eight GET endpoints under https://status.utilita.co.uk/api/v2 return the page status indicator, all 21 tracked components (SMETS1, SMETS1 DCC-enrolled and SMETS2 smart meters, Guest Payments, Open Banking, PayPoint in-store and IVR top-up, PayZone in-store, the My Utilita app and web portal, Power-up functionality, utilita.co.uk, join.utilita.co.uk, telephone lines, the chatbot, smart meter installations and the smart metering network), open and historical incidents with their full update timelines, and scheduled maintenance windows. No API key, no sign-up, no OAuth — every endpoint is anonymous and CORS-open with a 10-second cache window. Runs on Atlassian Statuspage under Utilita's own domain, and offers webhook, RSS, Atom, email and Slack subscriptions for push delivery. This is Utilita's only public API; it carries no customer, billing or consumption data.
Utilita Status API is published by Utilita on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Status, Incidents, Components, Scheduled Maintenance, and Smart Metering. The published artifact set on APIs.io includes API documentation, an API reference, an OpenAPI specification, and authentication docs.
This API exposes 8 operations across 8 paths, organized into 4 resource areas, and defines 13 schemas. It is described by OpenAPI 3.1.0, at version 2.
Requests are made against a single base URL, https://status.utilita.co.uk/api/v2.
Metadata
The identity and technical contract details declared by the specification.
Paths & Operations 8
Across 8 paths, the API surfaces 8 operations — 8 GET. They span 4 resource areas: Status, Components, Incidents, Scheduled Maintenance. Each is listed below with its method, path, parameters, and response codes.
Overall page status and rolled-up summary.
The individual Utilita services tracked on the status page.
Unplanned service incidents and their update timeline.
Planned maintenance windows.
Schemas 13
The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are ScheduledMaintenance (15 properties), Component (13 properties), Incident (13 properties), IncidentUpdate (11 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
This is an independent, third-party profile of Utilita Status 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.