Outage Pro API

What you can build

The Outage Pro API turns nationwide power-outage data into something your systems can act on. Teams use it to run live operational dashboards, to drive alerting that pages the right people when an area loses power, and to feed outage context into internal apps, risk models, and maps. Because the data goes from a national total down to state, county, and utility, the same feed serves a national newsroom map and a single company watching its own sites. Every record carries current customers out and customers served, the outage % for that area, and a last-updated time, so whatever you build reflects how fresh the data is. Delivery is a standard REST API returning JSON, with optional county boundary geometry (GeoJSON) for mapping and webhooks that push data on each refresh cycle, so you can pull on demand or be notified as things change.

API at a glance

• RESTProtocol
• JSONFormat standard envelope
• ~ Every 10 MinutesRefresh
• 96.04%Coverage Monitored US electricity customers
• 1,200+Utilities & cooperatives
• State, County, UtilityGranularity
• AuthAPI key (Client ID + Secret)
• TimestampsUTC, ISO 8601 (each response includes meta.timezone: 'UTC')
• GeometryOptional county boundary GeoJSON
• WebhooksPush on each refresh cycle
• Rate-Limited TiersPlans, Pagination on large responses

What the data covers

The API is organized around the questions operators actually ask. At the national level you get total outages and customers out. At state, county, and utility level you get the same current counts, customers served, and outage %, so you can go from a national overview to a single utility in one request. The most-affected states and counties come pre-ranked, and there's a full list of monitored utilities with their current counts. Coverage is measured against the US Energy Information Administration (EIA) baseline and reflects monitored US electricity customers, not the whole country. Historical outage data is available on request. The page describes what the API returns rather than listing raw endpoint paths, since the exact request-and-response reference lives in the authenticated documentation you get with access.

What the API offers

Getting started and access

Getting to production takes four steps. You request access through the Request Data Access form, we issue a Client ID and Secret Key, you review the API documentation, and then you integrate and scale your plan as your usage grows. Authentication is a simple API key, responses are JSON over standard REST, and large responses are paginated. Plans are tiered and rate-limited to match your volume, so talk to us about the tier that fits your use case.