Aedifion · OAuth Scopes

Aedifion OAuth Scopes

OAuth 2.0 probed

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

Tokens are issued from https://auth.aedifion.io/realms/aedifion/protocol/openid-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.

Building AutomationSmart BuildingsEnergy ManagementIoTReal EstateHVACSustainabilityTime SeriesAnalyticsMQTTBuilding OperationsESGPropTechGermanyReal-Time

Scopes: 13 Flows: implicit, authorizationCode, password, clientCredentials Method: probed

OAuth endpoints

Authorization URL
https://auth.aedifion.io/realms/aedifion/protocol/openid-connect/auth

Token URL
https://auth.aedifion.io/realms/aedifion/protocol/openid-connect/token

Flows
implicitauthorizationCodepasswordclientCredentials

Scopes (13)

Scope	Description	Flows
openid	Use OpenID Connect (required). The only scope the OpenAPI itself declares.	implicit, authorizationCode
profile	Basic profile claims (name, preferred_username, locale).
email	Email address and verification status.
address	Address claim.
phone	Phone number claim.
roles	Realm and client role mappings, which carry the platform's RBAC assignments.
api	Access to the aedifion HTTP API as a resource.
offline_access	Issue a refresh token usable while the user is offline.
service_account	Client-credentials service account access.
basic	Keycloak basic scope (sub, auth_time claims).
acr	Authentication context class reference claim.
microprofile-jwt	MicroProfile JWT claims (upn, groups).
web-origins	CORS allowed origins claim.

📄 Provider scope reference: https://docs.aedifion.io/en/developers/http-api/guides-and-tutorials/authentication/

Source

OAuth Scopes

generated: '2026-09-09'
method: probed
source: https://auth.aedifion.io/realms/aedifion/.well-known/openid-configuration
docs: https://docs.aedifion.io/en/developers/http-api/guides-and-tutorials/authentication/
note: >-
  The OpenAPI declares a single openIDConnect scheme exposing only the mandatory `openid`
  scope. The authoritative scope list is the one advertised by the aedifion Keycloak realm's
  own OIDC discovery document, fetched live and saved to
  well-known/aedifion-openid-configuration.json. These are Keycloak's standard realm scopes
  plus an `api` scope; aedifion publishes no per-resource scope reference page, and
  fine-grained authorization on the HTTP API is enforced by role-based access control on
  projects and datapoints rather than by OAuth scopes.
schemes:
- name: openIDConnect
  source: openapi/aedifion-openapi.yml
  issuer: https://auth.aedifion.io/realms/aedifion
  flows:
  - flow: implicit
    authorizationUrl: https://auth.aedifion.io/realms/aedifion/protocol/openid-connect/auth
  - flow: authorizationCode
    authorizationUrl: https://auth.aedifion.io/realms/aedifion/protocol/openid-connect/auth
    tokenUrl: https://auth.aedifion.io/realms/aedifion/protocol/openid-connect/token
  - flow: password
    tokenUrl: https://auth.aedifion.io/realms/aedifion/protocol/openid-connect/token
  - flow: clientCredentials
    tokenUrl: https://auth.aedifion.io/realms/aedifion/protocol/openid-connect/token
scopes:
- scope: openid
  description: Use OpenID Connect (required). The only scope the OpenAPI itself declares.
  flows: [implicit, authorizationCode]
  sources: [openapi/aedifion-openapi.yml, well-known/aedifion-openid-configuration.json]
- scope: profile
  description: Basic profile claims (name, preferred_username, locale).
  sources: [well-known/aedifion-openid-configuration.json]
- scope: email
  description: Email address and verification status.
  sources: [well-known/aedifion-openid-configuration.json]
- scope: address
  description: Address claim.
  sources: [well-known/aedifion-openid-configuration.json]
- scope: phone
  description: Phone number claim.
  sources: [well-known/aedifion-openid-configuration.json]
- scope: roles
  description: Realm and client role mappings, which carry the platform's RBAC assignments.
  sources: [well-known/aedifion-openid-configuration.json]
- scope: api
  description: Access to the aedifion HTTP API as a resource.
  sources: [well-known/aedifion-openid-configuration.json]
- scope: offline_access
  description: Issue a refresh token usable while the user is offline.
  sources: [well-known/aedifion-openid-configuration.json]
- scope: service_account
  description: Client-credentials service account access.
  sources: [well-known/aedifion-openid-configuration.json]
- scope: basic
  description: Keycloak basic scope (sub, auth_time claims).
  sources: [well-known/aedifion-openid-configuration.json]
- scope: acr
  description: Authentication context class reference claim.
  sources: [well-known/aedifion-openid-configuration.json]
- scope: microprofile-jwt
  description: MicroProfile JWT claims (upn, groups).
  sources: [well-known/aedifion-openid-configuration.json]
- scope: web-origins
  description: CORS allowed origins claim.
  sources: [well-known/aedifion-openid-configuration.json]

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