# BC Hydro

> British Columbia Hydro and Power Authority (BC Hydro) is a provincial Crown corporation and the monopoly electricity retailer for most of British Columbia, generating and delivering electricity to 95% of the province's population and serving over five million people. It owns the generation fleet, the transmission and distribution system, and the customer relationship, under rate regulation by the B.C. Utilities Commission. No consumer energy data right binds it: Ontario Regulation 633/21 stops at Ontario's border and Canada has no federal energy equivalent. BC Hydro adopted Green Button voluntarily — but only the Download My Data file half. There is no public API.

Generated by API Evangelist from the BC Hydro APIs.json profile. Method: generated. Date: 2026-07-27.
BC Hydro publishes no llms.txt of its own (https://www.bchydro.com/llms.txt and https://app.bchydro.com/llms.txt both return HTTP 200 and redirect to the /siteinfo/404.html soft-404 page).

## What an agent needs to know first

- **There is no BC Hydro API.** No OpenAPI, Swagger, GraphQL, AsyncAPI, gRPC or MCP surface exists. `/openapi.json`, `/openapi.yaml`, `/swagger.json`, `/api-docs` and `/graphql` all soft-404 on both www.bchydro.com and app.bchydro.com, and the site's own 3,703-URL sitemap.xml contains no developer, API or open-data path. `developer.`, `docs.`, `data.` and `apis.bchydro.com` do not resolve.
- **`api.bchydro.com` exists but is closed.** It resolves to a BC Hydro-owned IP and completes a TLS 1.3 handshake with a valid Entrust OV certificate issued to "British Columbia Hydro and Power Authority" — then returns nothing to any anonymous HTTP request, on any path, and refuses TLS 1.2 outright. Do not treat it as a public API; nothing about it is documented.
- **Consumer energy data is reachable only by the account holder, by hand.** Sign in to MyHydro, then "Download a CSV or Green Button XML file with your metered electricity use" — available through the previous day, up to three years of history. There is **no Green Button Connect My Data**, no OAuth authorization or token endpoint, no vendor onboarding, no data-recipient terms and no resource base URI, so **no third party can obtain a customer's data programmatically**.
- **Grid and market data is registration-gated or documentary.** Wholesale transmission information goes to an OATI-hosted OASIS node open to registered transmission customers only; the BCUC Order G-127-06 postings are documents on a schedule, not feeds. No open data portal is published.
- **Soft 404s.** This site answers unknown paths with HTTP 200 and a redirect to `https://www.bchydro.com/siteinfo/404.html`. A 200 proves nothing here — inspect the final URL. An F5 WAF also rejects some non-browser clients with a "Request Rejected" interstitial.

## APIs

None. BC Hydro documents no public API, and `apis[]` in the APIs.json profile is deliberately empty.

## The one machine-readable surface (undocumented)

- [Outage map feed](https://www.bchydro.com/power-outages/app/outages-map-data.json): a bare JSON array of current outages (id, gisId, regionId, regionName, municipality, area, cause, numCustomersOut, crewStatus, crewEta/crewEtr, dateOff/dateOn/lastUpdated as epoch milliseconds, latitude, longitude, polygon). Anonymous and machine-readable — but **undocumented, unlicensed, unversioned and never claimed by BC Hydro as an API**. It backs https://www.bchydro.com/power-outages/app/outage-map.html. Treat it as an internal browser endpoint that may change or vanish without notice.
- Schema derived by API Evangelist from a live fetch: [json-schema/bc-hydro-outages-map.json](https://raw.githubusercontent.com/api-evangelist/bc-hydro/refs/heads/main/json-schema/bc-hydro-outages-map.json)

## Docs

- [Viewing and exporting your bill and account history](https://app.bchydro.com/accounts-billing/bill-payment/view-bill.html): the Green Button XML / CSV download evidence.
- [Access your building or strata's electricity use history](https://app.bchydro.com/accounts-billing/rates-energy-use/access-load-data.html): peak load data by request form; kWh in one-hour intervals; no API or feed.
- [MyHydro log in](https://www.bchydro.com/login): redirects to a ForgeRock/OpenAM-style SSO endpoint (`/sso/UI/Login`, realm `bch-ps`). This is the only authentication that exists.
- [OASIS transmission scheduling](https://www.bchydro.com/energy-in-bc/operations/transmission/transmission-scheduling/oasis.html): registered users only.
- [Transaction data postings](https://www.bchydro.com/energy-in-bc/operations/transmission/transmission-scheduling/transaction-data.html): BCUC Order G-127-06 documents.
- [Cybersecurity requirements for suppliers](https://www.bchydro.com/work-with-us/suppliers/doing-business-with-bchydro/contractor-cybersecurity.html): NERC CIP-013-2 supply-chain requirements, directed by the BCUC and NERC.
- [Terms, conditions & pricing (tariffs)](https://www.bchydro.com/toolbar/about/strategies-plans-regulatory/tariffs-terms-conditions.html)
- [Contact us](https://www.bchydro.com/contact.html) · [Get help](https://app.bchydro.com/accounts-billing/get-help.html)

## Open data

- [BC Data Catalogue — BC Hydro and Power Authority](https://catalogue.data.gov.bc.ca/organization/bc-hydro-and-power-authority): exactly one dataset, "BC Hydro Resource Options Mapping - 2013" (licence "Access Only"), served as an OGC WMS GetCapabilities service and a KML ground overlay on openmaps.gov.bc.ca. Real open data, but a 2013 planning map layer published through the provincial catalogue — not grid or market data, and not a BC Hydro API.

## Standards and regulation

- [Green Button Alliance](https://www.greenbuttonalliance.org/): the standard body. BC Hydro is not named as certified.
- [B.C. Utilities Commission](https://www.bcuc.com/): the regulator — economic and rate regulation only, no data-sharing mandate.
- [O. Reg. 633/21 (Energy Data), Electricity Act, 1998](https://www.ontario.ca/laws/regulation/210633): the Ontario mandate that does **not** apply here — the reason BC Hydro's Green Button support is voluntary and file-only.

## API Evangelist artifacts

- [APIs.json profile](https://raw.githubusercontent.com/api-evangelist/bc-hydro/refs/heads/main/apis.yml)
- [Review — full probe log with HTTP statuses](https://raw.githubusercontent.com/api-evangelist/bc-hydro/refs/heads/main/review.yml)
- [Authentication profile](https://raw.githubusercontent.com/api-evangelist/bc-hydro/refs/heads/main/authentication/bc-hydro-authentication.yml)
- [Conventions](https://raw.githubusercontent.com/api-evangelist/bc-hydro/refs/heads/main/conventions/bc-hydro-conventions.yml)
- [Conformance](https://raw.githubusercontent.com/api-evangelist/bc-hydro/refs/heads/main/conformance/bc-hydro-conformance.yml)
- [Lifecycle](https://raw.githubusercontent.com/api-evangelist/bc-hydro/refs/heads/main/lifecycle/bc-hydro-lifecycle.yml)
- [Domain security probe](https://raw.githubusercontent.com/api-evangelist/bc-hydro/refs/heads/main/security/bc-hydro-domain-security.yml)
- [Well-known probe index](https://raw.githubusercontent.com/api-evangelist/bc-hydro/refs/heads/main/well-known/bc-hydro-well-known.yml)
- [Packages search](https://raw.githubusercontent.com/api-evangelist/bc-hydro/refs/heads/main/packages/bc-hydro-packages.yml)

## Not available

- OpenAPI / Swagger / GraphQL / AsyncAPI / gRPC definitions — none exist.
- First-party SDKs, CLI, Postman collection, embedded components — none. One unofficial community Python package (`bchydro` on PyPI, MIT, by Eric McNiece) drives the customer portal; it is not a BC Hydro product.
- MCP server or agent skills — none; there is no specification to ground them in.
- Webhooks, events, streaming — none.
- API status page, SLA, changelog, deprecation policy, roadmap, sandbox, developer signup — none.
- security.txt, trust centre, published vulnerability disclosure programme — none found.