Toronto Hydro · OAuth Scopes

Toronto Hydro OAuth Scopes

OAuth 2.0 derived

Toronto Hydro uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

Tokens are issued from https://sandbox.greenbuttonalliance.org:8443/oauth/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

EnergyCanadaUtilitiesElectricitySmart MeteringGreen ButtonGridOntarioConsumer DataElectricity Distribution
Scopes: 0 Flows: authorizationCode, clientCredentials Method: derived

OAuth endpoints

Authorization URL
https://sandbox.greenbuttonalliance.org:8443/oauth/authorize
Token URL
https://sandbox.greenbuttonalliance.org:8443/oauth/token
Flows
authorizationCodeclientCredentials

Scopes (0)

Toronto Hydro implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

Zero scopes is the real, expected result. The oauth2 scheme in the Green Button Alliance source specification declares an EMPTY scopes object, and Toronto Hydro publishes no scopes or permissions reference page anywhere — no scope names were invented. The authorization and token URLs below are the GBA sandbox's, not Toronto Hydro's; Toronto Hydro publishes no OAuth endpoints. In the Green Button model the effective grant is expressed through the customer's authorization at consent time and carried on the Authorization resource (fields scope, grant_type, expires_at, status) rather than through a published scope catalogue. Toronto Hydro describes the data classes covered — consumption details, billing information and customer information — but does not express them as scopes.

📄 Provider scope reference:

Source

OAuth Scopes

Raw ↑ 
generated: '2026-07-27'
method: derived
source: openapi/toronto-hydro-green-button-espi-openapi.yml
note: >-
  Zero scopes is the real, expected result. The oauth2 scheme in the Green Button Alliance
  source specification declares an EMPTY scopes object, and Toronto Hydro publishes no
  scopes or permissions reference page anywhere — no scope names were invented. The
  authorization and token URLs below are the GBA sandbox's, not Toronto Hydro's; Toronto
  Hydro publishes no OAuth endpoints. In the Green Button model the effective grant is
  expressed through the customer's authorization at consent time and carried on the
  Authorization resource (fields scope, grant_type, expires_at, status) rather than
  through a published scope catalogue. Toronto Hydro describes the data classes covered —
  consumption details, billing information and customer information — but does not
  express them as scopes.
schemes:
- name: oauth2
  source: openapi/toronto-hydro-green-button-espi-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://sandbox.greenbuttonalliance.org:8443/oauth/authorize
    tokenUrl: https://sandbox.greenbuttonalliance.org:8443/oauth/token
  - flow: clientCredentials
    tokenUrl: https://sandbox.greenbuttonalliance.org:8443/oauth/token
scopes: []