Western Power website screenshot

Western Power

Western Power is the Western Australian state-owned statutory corporation that owns and operates the electricity transmission and distribution network — the poles, wires, substations and streetlights — across the South West Interconnected System (SWIS), from Kalbarri in the north to Albany in the south and east to Kalgoorlie, across more than 103,000 km of powerlines, 825,788 poles and towers, 276,000 streetlights and 154 transmission substations. It is a regulated network distributor (DNO/DSO), not a retailer and not a generator; Synergy is the SWIS retailer for residential and small-business customers and AEMO operates the WA Wholesale Electricity Market. Its API posture is honestly minimal — there is no developer portal, no published API program, no developer documentation and no published OpenAPI anywhere on westernpower.com.au (developer./api./docs./data. subdomains all fail to resolve; /developers, /docs and /openapi.json all return 404). It is nonetheless not API-less. Three anonymous machine-readable surfaces were verified on 2026-07-27 — an undocumented first-party JSON API at westernpower.com.au/api/corp/outage/* that backs the public outage tracker and returns every current and upcoming outage, one outage with hazard flags and update history, and a per-suburb rollup; an Esri ArcGIS Online feature service serving the same outages as polygons with SQL, spatial and statistical query; and the corporate site's own search, news and vacancy endpoints. All are internal endpoints of Western Power's web applications — robots.txt disallows /api/ — with no reference, no terms of use, no versioning, no SLA and no support channel. Consumer energy data is real but not programmatic — a third party must register a business with Western Power and collect verifiable customer consent, after which up to two years of interval and accumulated metering data is delivered by email or a web portal, never an API. Australia's Consumer Data Right, the mandate that forced identical banking APIs and was then transplanted into energy, does not reach this organisation at all — CDR energy covers National Electricity Market retailers, and Western Australia sits outside the NEM while distributors were never designated data holders in any state. Its 36 network asset and capacity datasets are published through the WA Government DataWA/SLIP portals as "open data subject to registering for access" under Western Power's own data licence — WFS, WMS and ArcGIS REST endpoints that return HTTP 401 to an anonymous caller.

Western Power publishes 5 APIs on the APIs.io network, including Content API, Metadata API, Outages API, and 2 more. Tagged areas include Energy, Australia, Utilities, Electricity, and Grid.

Western Power’s developer surface includes authentication, support, engineering blog, documentation, developer portal, and 27 more developer resources.

33.2/100 thin ▬ flat Agent 27/100 agent aware saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
3 APIs
EnergyAustraliaUtilitiesElectricityGridNetwork DistributionSmart MeteringOpen DataGISOutages

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Regulatory Posture applies to this provider. Its tags matched the Energy & Utilities regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics does not apply to this provider. The published contracts declare no write operations, and a read-only API cannot create-or-update. The facet is excluded from this provider's denominator entirely — not scored zero. A reference or data API is not deficient for being unable to upsert.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/western-power: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 6

Individual APIs this provider publishes, each with its own machine-readable definition.

Western Power Public Secure Services (SLIP)

Western Power's network asset and capacity spatial data — distribution and transmission overhead powerlines, underground cables, poles, pillars, pits, transformers, enclosures, ...

Western Power Content API

The Content API from Western Power — 2 operation(s) for content.

Western Power Metadata API

The Metadata API from Western Power — 2 operation(s) for metadata.

Western Power Outages API

Live planned and unplanned outage data for the South West Interconnected System.

Western Power Query API

The Query API from Western Power — 1 operation(s) for query.

Western Power Search API

The Search API from Western Power — 1 operation(s) for search.

Open Collections 3

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Examples 4

Example request and response payloads for these APIs.

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Western Power Authentication

none/esri-token/session-cookie · 5 schemes

SECURITY

Western Power Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Western Power Agentic Access

9 operations

9 operations · 0 acting

AGENTIC

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 7

MCP servers, agent skills, and machine-readable catalogs

Scroll for all 7

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Other 6

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: western-power
url: https://raw.githubusercontent.com/api-evangelist/western-power/refs/heads/main/apis.yml
name: Western Power
kind: company
description: Western Power is the Western Australian state-owned statutory corporation that owns and operates the electricity
  transmission and distribution network — the poles, wires, substations and streetlights — across the South West Interconnected
  System (SWIS), from Kalbarri in the north to Albany in the south and east to Kalgoorlie, across more than 103,000 km of
  powerlines, 825,788 poles and towers, 276,000 streetlights and 154 transmission substations. It is a regulated network distributor
  (DNO/DSO), not a retailer and not a generator; Synergy is the SWIS retailer for residential and small-business customers
  and AEMO operates the WA Wholesale Electricity Market. Its API posture is honestly minimal — there is no developer portal,
  no published API program, no developer documentation and no published OpenAPI anywhere on westernpower.com.au (developer./api./docs./data.
  subdomains all fail to resolve; /developers, /docs and /openapi.json all return 404). It is nonetheless not API-less. Three
  anonymous machine-readable surfaces were verified on 2026-07-27 — an undocumented first-party JSON API at westernpower.com.au/api/corp/outage/*
  that backs the public outage tracker and returns every current and upcoming outage, one outage with hazard flags and update
  history, and a per-suburb rollup; an Esri ArcGIS Online feature service serving the same outages as polygons with SQL, spatial
  and statistical query; and the corporate site's own search, news and vacancy endpoints. All are internal endpoints of Western
  Power's web applications — robots.txt disallows /api/ — with no reference, no terms of use, no versioning, no SLA and no
  support channel. Consumer energy data is real but not programmatic — a third party must register a business with Western
  Power and collect verifiable customer consent, after which up to two years of interval and accumulated metering data is
  delivered by email or a web portal, never an API. Australia's Consumer Data Right, the mandate that forced identical banking
  APIs and was then transplanted into energy, does not reach this organisation at all — CDR energy covers National Electricity
  Market retailers, and Western Australia sits outside the NEM while distributors were never designated data holders in any
  state. Its 36 network asset and capacity datasets are published through the WA Government DataWA/SLIP portals as "open data
  subject to registering for access" under Western Power's own data licence — WFS, WMS and ArcGIS REST endpoints that return
  HTTP 401 to an anonymous caller.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-09-02'
  method: derived
image: https://www.westernpower.com.au/faviconImages/apple-touch-icon.png
tags:
- Energy
- Australia
- Utilities
- Electricity
- Grid
- Network Distribution
- Smart Metering
- Open Data
- GIS
- Outages
created: '2026-07-27'
modified: '2026-07-27'
specificationVersion: '0.23'
apis:
- aid: western-power:western-power-public-secure-services-slip
  name: Western Power Public Secure Services (SLIP)
  description: Western Power's network asset and capacity spatial data — distribution and transmission overhead powerlines,
    underground cables, poles, pillars, pits, transformers, enclosures, substations, streetlights, underground power project
    areas and the Network Capacity Mapping Tool forecast remaining-capacity layers — published as 36 datasets on the WA Government
    DataWA catalogue and served from the Landgate SLIP platform as ArcGIS REST MapServer/FeatureServer, OGC WFS and OGC WMS
    endpoints plus GeoJSON, GeoPackage, File Geodatabase and Shapefile downloads. DataWA labels these "open data subject to
    registering for access"; access is automatically granted on registering an email address and agreeing to Western Power's
    data licence terms and conditions. Anonymous calls are rejected — both the MapServer root and layer 10 returned HTTP 401
    Unauthorized on 2026-07-27, and the bulk download host redirects to /Account/Login. Authenticated access uses Esri token
    authentication via token.slip.wa.gov.au.
  humanURL: https://catalogue.data.wa.gov.au/dataset/distribution-overhead-power-lines-wp-031
  baseURL: https://services.slip.wa.gov.au/arcgis/rest/services/WP_Public_Secure_Services/WP_Public_Secure_Services/MapServer
  tags:
  - Open Data
  - GIS
  - Grid
  - Network Capacity
  - WFS
  properties:
  - type: Catalog
    url: catalog/datawa-western-power-datasets.json
  - type: CatalogEntry
    url: catalog/datawa-wp-031-distribution-overhead-powerlines.json
  - type: Documentation
    url: https://catalogue.data.wa.gov.au/group/about/western-power-group
  - type: License
    url: https://catalogue.data.wa.gov.au/dataset/wp-licence-terms-and-conditions
  - type: Application
    url: https://www.westernpower.com.au/resources-education/calculators-tools/network-capacity-mapping-tool/
- aid: western-power:western-power-content-api
  name: Western Power Content API
  description: The Content API from Western Power — 2 operation(s) for content.
  humanURL: https://www.westernpower.com.au/outages/
  baseURL: https://www.westernpower.com.au/api/corp/outage
  tags:
  - Content
  properties:
  - type: OpenAPI
    url: openapi/western-power-content-api-openapi.yml
  - type: Examples
    url: examples/western-power-all-outages-sample.json
  - type: Examples
    url: examples/western-power-outage-details-sample.json
  - type: Examples
    url: examples/western-power-outage-status-sample.json
  - type: Documentation
    url: https://www.westernpower.com.au/outages/
  - type: Examples
    url: examples/western-power-search-sample.json
  - type: Examples
    url: examples/western-power-vacancies-sample.json
  - type: ServiceMetadata
    url: arcgis/wp-outage-featureserver.json
  - type: ServiceMetadata
    url: arcgis/wp-outage-layer0-outage-areas.json
  - type: SampleResponse
    url: arcgis/wp-outage-sample-query-response.json
- aid: western-power:western-power-metadata-api
  name: Western Power Metadata API
  description: The Metadata API from Western Power — 2 operation(s) for metadata.
  humanURL: https://www.westernpower.com.au/outages/
  baseURL: https://www.westernpower.com.au/api/corp/outage
  tags:
  - Metadata
  properties:
  - type: OpenAPI
    url: openapi/western-power-metadata-api-openapi.yml
  - type: Examples
    url: examples/western-power-all-outages-sample.json
  - type: Examples
    url: examples/western-power-outage-details-sample.json
  - type: Examples
    url: examples/western-power-outage-status-sample.json
  - type: Documentation
    url: https://www.westernpower.com.au/outages/
  - type: Examples
    url: examples/western-power-search-sample.json
  - type: Examples
    url: examples/western-power-vacancies-sample.json
  - type: ServiceMetadata
    url: arcgis/wp-outage-featureserver.json
  - type: ServiceMetadata
    url: arcgis/wp-outage-layer0-outage-areas.json
  - type: SampleResponse
    url: arcgis/wp-outage-sample-query-response.json
- aid: western-power:western-power-outages-api
  name: Western Power Outages API
  description: Live planned and unplanned outage data for the South West Interconnected System.
  humanURL: https://www.westernpower.com.au/outages/
  baseURL: https://www.westernpower.com.au/api/corp/outage
  tags:
  - Outages
  properties:
  - type: OpenAPI
    url: openapi/western-power-outages-api-openapi.yml
  - type: Examples
    url: examples/western-power-all-outages-sample.json
  - type: Examples
    url: examples/western-power-outage-details-sample.json
  - type: Examples
    url: examples/western-power-outage-status-sample.json
  - type: Documentation
    url: https://www.westernpower.com.au/outages/
  - type: Examples
    url: examples/western-power-search-sample.json
  - type: Examples
    url: examples/western-power-vacancies-sample.json
  - type: ServiceMetadata
    url: arcgis/wp-outage-featureserver.json
  - type: ServiceMetadata
    url: arcgis/wp-outage-layer0-outage-areas.json
  - type: SampleResponse
    url: arcgis/wp-outage-sample-query-response.json
- aid: western-power:western-power-query-api
  name: Western Power Query API
  description: The Query API from Western Power — 1 operation(s) for query.
  humanURL: https://www.westernpower.com.au/outages/
  baseURL: https://www.westernpower.com.au/api/corp/outage
  tags:
  - Query
  properties:
  - type: OpenAPI
    url: openapi/western-power-query-api-openapi.yml
  - type: Examples
    url: examples/western-power-all-outages-sample.json
  - type: Examples
    url: examples/western-power-outage-details-sample.json
  - type: Examples
    url: examples/western-power-outage-status-sample.json
  - type: Documentation
    url: https://www.westernpower.com.au/outages/
  - type: Examples
    url: examples/western-power-search-sample.json
  - type: Examples
    url: examples/western-power-vacancies-sample.json
  - type: ServiceMetadata
    url: arcgis/wp-outage-featureserver.json
  - type: ServiceMetadata
    url: arcgis/wp-outage-layer0-outage-areas.json
  - type: SampleResponse
    url: arcgis/wp-outage-sample-query-response.json
- aid: western-power:western-power-search-api
  name: Western Power Search API
  description: The Search API from Western Power — 1 operation(s) for search.
  humanURL: https://www.westernpower.com.au/outages/
  baseURL: https://www.westernpower.com.au/api/corp/outage
  tags:
  - Search
  properties:
  - type: OpenAPI
    url: openapi/western-power-search-api-openapi.yml
  - type: Examples
    url: examples/western-power-all-outages-sample.json
  - type: Examples
    url: examples/western-power-outage-details-sample.json
  - type: Examples
    url: examples/western-power-outage-status-sample.json
  - type: Documentation
    url: https://www.westernpower.com.au/outages/
  - type: Examples
    url: examples/western-power-search-sample.json
  - type: Examples
    url: examples/western-power-vacancies-sample.json
  - type: ServiceMetadata
    url: arcgis/wp-outage-featureserver.json
  - type: ServiceMetadata
    url: arcgis/wp-outage-layer0-outage-areas.json
  - type: SampleResponse
    url: arcgis/wp-outage-sample-query-response.json
common:
- type: Overlay
  url: overlays/western-power-outage-overlay.yaml
- type: AgentSkill
  url: skills/western-power-check-outages.md
- type: Overlay
  url: overlays/western-power-corporate-web-overlay.yaml
- type: Overlay
  url: overlays/western-power-arcgis-outage-overlay.yaml
- type: AgentSkill
  url: skills/western-power-query-outage-geography.md
- type: X-MCPServerCandidate
  url: mcp/western-power-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: AgenticAccess
  url: agentic-access/western-power-agentic-access.yml
- type: DomainSecurity
  url: security/western-power-domain-security.yml
- type: Authentication
  name: Authentication profile — anonymous, Esri token, session login
  url: authentication/western-power-authentication.yml
- type: Conventions
  name: API conventions — pagination, date formats, caching, rate limiting
  url: conventions/western-power-conventions.yml
- type: ErrorCatalog
  name: Error behaviour — three inconsistent idioms, 204-as-not-found
  url: errors/western-power-problem-types.yml
- type: Lifecycle
  name: Lifecycle — no versioning, no deprecation policy, no SLA
  url: lifecycle/western-power-lifecycle.yml
- type: Conformance
  name: Standards conformance — geospatial only, no energy data standard
  url: conformance/western-power-conformance.yml
- type: DataModel
  name: Data model — one Outage entity projected two incompatible ways
  url: data-model/western-power-data-model.yml
- type: WellKnown
  name: /.well-known/ discovery probe — every path 404
  url: well-known/western-power-well-known.yml
- type: Packages
  name: Client libraries — none published (probed negative)
  url: packages/western-power-packages.yml
- type: LLMsTxt
  url: llms/western-power-llms.txt
- type: AgentSkill
  name: Agent skills index
  url: skills/_index.yml
- type: GitHubOrganization
  name: GitHub organisation (verified, 0 public repositories)
  url: https://github.com/Western-Power
- type: TermsOfService
  url: https://www.westernpower.com.au/terms--conditions/
- type: PrivacyPolicy
  url: https://www.westernpower.com.au/privacy-policy/
- type: Support
  url: https://www.westernpower.com.au/about/contact-us/
- type: Website
  url: https://www.westernpower.com.au/
- type: About
  url: https://www.westernpower.com.au/about/
- type: Blog
  url: https://www.westernpower.com.au/news/
- type: OpenData
  url: https://catalogue.data.wa.gov.au/group/about/western-power-group
- type: License
  url: https://catalogue.data.wa.gov.au/dataset/wp-licence-terms-and-conditions
- type: Documentation
  url: https://www.westernpower.com.au/resources-education/industry-resources/retailers-and-generators/
- type: Registration
  url: https://www.westernpower.com.au/issues-enquiries/requests-preferences/registration-for-access-to-energy-data/
- type: Consent
  url: https://www.westernpower.com.au/issues-enquiries/requests-preferences/verifiable-consent-for-access-to-energy-data/
- type: Portal
  url: https://services.westernpower.com.au/online/nbu/do/restricted/Home
- type: Portal
  url: https://www.mywpprojects.westernpower.com.au/
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/western-power"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/western-power/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/western-power/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.