Greenchoice · OAuth Scopes
Greenchoice OAuth Scopes
OAuth 2.0
probed
Greenchoice 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.
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.
EnergyElectricityGasRenewablesSustainabilityNetherlands
Scopes: 0
Flows:
Method: probed
Scopes (0)
Greenchoice 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.
The scopes below are the complete scopes_supported array Greenchoice's own OpenID Connect discovery document advertises, read live on 2026-09-12. Greenchoice publishes no scope or permission reference page, so the descriptions for the two non-standard scopes record what can honestly be said about them and nothing more. No scope here was invented or inferred.
The scopes below are the complete scopes_supported array Greenchoice's own OpenID Connect discovery document advertises, read live on 2026-09-12. Greenchoice publishes no scope or permission reference page, so the descriptions for the two non-standard scopes record what can honestly be said about them and nothing more. No scope here was invented or inferred.
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.