Greenchoice · OAuth Scopes

Greenchoice OAuth Scopes

OAuth 2.0 probed

Greenchoice publishes 6 OAuth 2.0 scopes via the authorization_code, client_credentials, and device_code flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Greenchoice API on a user’s behalf.

Tokens are issued from https://sso.greenchoice.nl/connect/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.

EnergyElectricityGasRenewablesSustainabilityNetherlands

Scopes: 6 Flows: authorization_code, client_credentials, device_code Method: probed

OAuth endpoints

Authorization URL
https://sso.greenchoice.nl/connect/authorize

Token URL
https://sso.greenchoice.nl/connect/token

Flows
authorization_codeclient_credentialsdevice_code

Scopes (6)

Scope	Description	Flows
openid	Requests an ID token; required for any OIDC authentication request.
profile	Default profile claim set. This deployment advertises name, family_name, given_name, middle_name, nickname, preferred_username, picture, website, gender, birthdate, zoneinfo, locale and updated_at among claims_supported.
email	Releases the email and email_verified claims.
offline_access	Requests a refresh token for long-lived access.
id	Non-standard scope advertised by this issuer. A matching `id` claim appears in claims_supported alongside `klant_id` (customer id). Greenchoice publishes no definition; treated as an identifier-releasing scope, unverified.
api-genesys-beheer	Non-standard scope. The name indicates administrative ("beheer") access to a Genesys API — Genesys is the contact-centre platform Greenchoice operates. Its presence in a public discovery document is the only evidence that any internal API exists behind this issuer. Greenchoice publishes no definition, no documentation and no route for a third party to be granted it.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-09-12'
method: probed
source: https://sso.greenchoice.nl/.well-known/openid-configuration
note: >-
  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.
docs: null
docs_note: No published scopes/permissions reference exists on any Greenchoice surface.
issuer: https://sso.greenchoice.nl
flows:
  - type: authorization_code
    authorizationUrl: https://sso.greenchoice.nl/connect/authorize
    tokenUrl: https://sso.greenchoice.nl/connect/token
  - type: client_credentials
    tokenUrl: https://sso.greenchoice.nl/connect/token
  - type: device_code
    deviceAuthorizationUrl: https://sso.greenchoice.nl/connect/deviceauthorization
scope_count: 6
scopes:
  - name: openid
    standard: true
    spec: OpenID Connect Core 1.0
    description: Requests an ID token; required for any OIDC authentication request.
  - name: profile
    standard: true
    spec: OpenID Connect Core 1.0
    description: >-
      Default profile claim set. This deployment advertises name, family_name, given_name,
      middle_name, nickname, preferred_username, picture, website, gender, birthdate,
      zoneinfo, locale and updated_at among claims_supported.
  - name: email
    standard: true
    spec: OpenID Connect Core 1.0
    description: Releases the email and email_verified claims.
  - name: offline_access
    standard: true
    spec: OpenID Connect Core 1.0
    description: Requests a refresh token for long-lived access.
  - name: id
    standard: false
    description: >-
      Non-standard scope advertised by this issuer. A matching `id` claim appears in
      claims_supported alongside `klant_id` (customer id). Greenchoice publishes no
      definition; treated as an identifier-releasing scope, unverified.
  - name: api-genesys-beheer
    standard: false
    description: >-
      Non-standard scope. The name indicates administrative ("beheer") access to a Genesys
      API — Genesys is the contact-centre platform Greenchoice operates. Its presence in a
      public discovery document is the only evidence that any internal API exists behind this
      issuer. Greenchoice publishes no definition, no documentation and no route for a third
      party to be granted it.
claims_supported:
  - sub
  - auth_method
  - stp
  - account_type
  - medewerker_afkorting
  - updated_at
  - locale
  - zoneinfo
  - birthdate
  - gender
  - website
  - picture
  - profile
  - preferred_username
  - nickname
  - middle_name
  - given_name
  - family_name
  - name
  - emailAlreadyRegistered
  - permission
  - id
  - email
  - email_verified
  - klant_id

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/greenchoice-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 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.

GitHub Google LinkedIn

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