Hydro Ottawa · OAuth Scopes

Hydro Ottawa OAuth Scopes

OAuth 2.0 derived

Hydro Ottawa 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.

EnergyCanadaOntarioUtilitiesElectricityElectricity DistributionSmart MeteringGreen ButtonESPIMunicipal UtilityRenewablesHydroelectricSolarDemand ResponseGrid

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)

Hydro Ottawa 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 Hydro Ottawa 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 Hydro Ottawa's; Hydro Ottawa publishes no OAuth endpoints. In the Green Button model the effective grant is expressed through the customer's selection of data types, duration and frequency at authorization time, and is carried on the Authorization resource (fields scope, grant_type, expires_at, status) rather than through a published scope catalogue.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-07-27'
method: derived
source: openapi/hydro-ottawa-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 Hydro Ottawa 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 Hydro Ottawa's; Hydro Ottawa
  publishes no OAuth endpoints. In the Green Button model the effective grant is expressed
  through the customer's selection of data types, duration and frequency at authorization
  time, and is carried on the Authorization resource (fields scope, grant_type, expires_at,
  status) rather than through a published scope catalogue.
schemes:
- name: oauth2
  source: openapi/hydro-ottawa-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: []

Work with this as data

Every scope set 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 oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
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 scope set

curl "https://apis.io/api/v1/scopes/hydro-ottawa-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

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

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

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