ShellRecharge · OAuth Scopes

ShellRecharge OAuth Scopes

OAuth 2.0 derived

ShellRecharge 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://api.shell.com/v1/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.

EV ChargingElectric VehiclesMobilityCharge PointsOCPIEnergy

Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://api.shell.com/v1/oauth/token

Flows
clientCredentials

Scopes (0)

ShellRecharge 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.

Shell Developer APIs use the OAuth 2.0 client credentials grant with no published scopes; access is governed by partner credentials issued per app by the Shell API team (https://developer.shell.com/docs/authentication-authorisation).

📄 Provider scope reference: https://developer.shell.com/docs/authentication-authorisation

Source

OAuth Scopes

generated: '2026-07-11'
method: derived
source: openapi/shellrecharge-openapi.yml
docs: https://developer.shell.com/docs/authentication-authorisation
note: Shell Developer APIs use the OAuth 2.0 client credentials grant with no published
  scopes; access is governed by partner credentials issued per app by the Shell API
  team (https://developer.shell.com/docs/authentication-authorisation).
schemes:
- name: OAuth2ClientCredentials
  source: openapi/shellrecharge-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.shell.com/v1/oauth/token
  description: OAuth 2.0 client credentials grant. A bearer access token is obtained from the
    Shell SSO token endpoint and sent in the Authorization header; a separate API client id/secret
    pair is also required on functional requests.
scopes: []