E.ON Next · OAuth Scopes

E.ON Next OAuth Scopes

OAuth 2.0 searched

E.ON Next publishes 14 OAuth 2.0 scopes via the authorizationCode, implicit, clientCredentials, and deviceCode flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the E.ON Next API on a user’s behalf.

Tokens are issued from https://auth.eonnext.com/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.

EnergyUnited KingdomUtilitiesElectricityGasSmart MeteringEnergy RetailKrakenSolarEV ChargingIdentity

Scopes: 14 Flows: authorizationCode, implicit, clientCredentials, deviceCode Method: searched

OAuth endpoints

Authorization URL
https://auth.eonnext.com/authorize

Token URL
https://auth.eonnext.com/oauth/token

Flows
authorizationCodeimplicitclientCredentialsdeviceCode

Scopes (14)

Scope	Description	Flows
openid	Request an ID token — mandatory OIDC scope.
profile	Basic profile claims (name, given_name, family_name, nickname, picture).
email	The email claim.
address	The address claim.
phone	The phone_number claim.
offline_access	Issue a refresh token.
name	Individual claim scope for name.
given_name	Individual claim scope for given_name.
family_name	Individual claim scope for family_name.
nickname	Individual claim scope for nickname.
picture	Individual claim scope for picture.
email_verified	Individual claim scope for email_verified.
created_at	Individual claim scope for the account creation timestamp.
identities	Individual claim scope for linked identity providers.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-07-27'
method: searched
source: https://auth.eonnext.com/.well-known/openid-configuration
docs: null
docs_note: >-
  E.ON Next publishes no scopes/permissions reference page — no developer portal
  exists. The scope list below is the scopes_supported array advertised by the
  authorization server itself, fetched anonymously on 2026-07-27 and saved
  verbatim at well-known/eon-next-openid-configuration.json.
description: >-
  Every scope E.ON Next's authorization server advertises is a standard OpenID
  Connect scope or an Auth0 claim-shaped scope. There is no domain scope — no
  read:meter, no read:usage, no read:billing, no account scope of any kind. That
  absence is the finding: the authorization server governs identity for the
  customer account UI, and no energy-data resource server is exposed to
  third-party clients. Do not read this list as an entitlement model for
  consumption or billing data; that data has no published API at all.
schemes:
- name: eon-next-ciam-oidc
  issuer: https://auth.eonnext.com/
  source: well-known/eon-next-openid-configuration.json
  flows:
  - flow: authorizationCode
    authorizationUrl: https://auth.eonnext.com/authorize
    tokenUrl: https://auth.eonnext.com/oauth/token
  - flow: implicit
    authorizationUrl: https://auth.eonnext.com/authorize
  - flow: clientCredentials
    tokenUrl: https://auth.eonnext.com/oauth/token
  - flow: deviceCode
    deviceAuthorizationUrl: https://auth.eonnext.com/oauth/device/code
    tokenUrl: https://auth.eonnext.com/oauth/token
scopes:
- {scope: openid, description: 'Request an ID token — mandatory OIDC scope.', standard: 'OpenID Connect Core 1.0'}
- {scope: profile, description: 'Basic profile claims (name, given_name, family_name, nickname, picture).', standard: 'OpenID Connect Core 1.0'}
- {scope: email, description: 'The email claim.', standard: 'OpenID Connect Core 1.0'}
- {scope: address, description: 'The address claim.', standard: 'OpenID Connect Core 1.0'}
- {scope: phone, description: 'The phone_number claim.', standard: 'OpenID Connect Core 1.0'}
- {scope: offline_access, description: 'Issue a refresh token.', standard: 'OpenID Connect Core 1.0'}
- {scope: name, description: 'Individual claim scope for name.', standard: 'Auth0 claim scope'}
- {scope: given_name, description: 'Individual claim scope for given_name.', standard: 'Auth0 claim scope'}
- {scope: family_name, description: 'Individual claim scope for family_name.', standard: 'Auth0 claim scope'}
- {scope: nickname, description: 'Individual claim scope for nickname.', standard: 'Auth0 claim scope'}
- {scope: picture, description: 'Individual claim scope for picture.', standard: 'Auth0 claim scope'}
- {scope: email_verified, description: 'Individual claim scope for email_verified.', standard: 'Auth0 claim scope'}
- {scope: created_at, description: 'Individual claim scope for the account creation timestamp.', standard: 'Auth0 claim scope'}
- {scope: identities, description: 'Individual claim scope for linked identity providers.', standard: 'Auth0 claim scope'}
scope_count: 14
domain_scopes: 0
domain_scopes_note: >-
  No energy, metering, account, tariff, billing or payment scope is advertised.
  Any such scope would live on a resource-server audience that E.ON Next does not
  publish.