Easee Authentication

generated: '2026-10-27'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://developer.easee.com/docs/authentication-1.md
sources:
- https://developer.easee.com/docs/authentication-1.md
- https://developer.easee.com/docs/oauth-20-integration-guide.md
- https://developer.easee.com/docs/available-oauth-scopes.md
- https://developer.easee.com/reference/account_authenticate.md
description: Authentication methods for Easee APIs
schemes:
- type: apiKey
  name: Bearer
  evidence: 'JWT Authorization header using the Bearer scheme. Example: "Authorization: Bearer {token}"'
  location: header
  header: Authorization
  how_to_obtain: Call the /api/accounts/login endpoint with a JSON body containing userName and password to receive an accessToken and refreshToken.
- type: oauth2
  name: OAuth2 Authorization Code with PKCE
  evidence: Easee supports OAuth 2.0 based on the OAuth 2.0 Authorization Framework (RFC 6749) and follows the standard authorization code flow
    for user-delegated access.
  token_url: https://auth.easee.com/realms/easee/protocol/openid-connect/token
  authorize_url: https://auth.easee.com/realms/easee/protocol/openid-connect/auth
  scopes:
  - openid
  - profile
  - email
  - chargers:read
  - sites:read
  - sites:operator:manage
  - sessions:read
  - account:profile:read
  - equalizers:read
  how_to_obtain: Register an application to receive a client_id (and client_secret if confidential), then perform the Authorization Code flow
    with PKCE as described in the OAuth 2.0 Integration Guide.
docs: https://developer.easee.com/docs/authentication-1.md