LeanIX · OAuth Scopes

LeanIX OAuth Scopes

OAuth 2.0 derived

LeanIX 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 /services/mtm/v1/oauth2/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.

Enterprise ArchitectureSaaS ManagementIT Portfolio ManagementApplication PortfolioTechnology Risk

Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
/services/mtm/v1/oauth2/token

Flows
clientCredentials

Scopes (0)

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

SAP LeanIX OAuth 2.0 does not use published scopes; the client_credentials token response returns an empty scope value and access is governed by the permission role (Admin, Member, Viewer) of the technical user or API token encoded in the JWT (https://help.sap.com/docs/leanix/ea/authentication-to-sap-leanix-services).

📄 Provider scope reference: https://help.sap.com/docs/leanix/ea/authentication-to-sap-leanix-services

Source

OAuth Scopes

generated: '2026-07-11'
method: derived
source: openapi/leanix-openapi.json
docs: https://help.sap.com/docs/leanix/ea/authentication-to-sap-leanix-services
note: >-
  SAP LeanIX OAuth 2.0 does not use published scopes; the client_credentials
  token response returns an empty scope value and access is governed by the
  permission role (Admin, Member, Viewer) of the technical user or API token
  encoded in the JWT
  (https://help.sap.com/docs/leanix/ea/authentication-to-sap-leanix-services).
schemes:
- name: token
  source: openapi/leanix-openapi.json
  flows:
  - flow: clientCredentials
    tokenUrl: /services/mtm/v1/oauth2/token
scopes: []