SAP Integration Suite OAuth Scopes

OAuth 2.0 derived

SAP Integration Suite 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://{tenant}.authentication.sap.hana.ondemand.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.

API ManagementCloud IntegrationEnterprise IntegrationEvent MeshiPaaSSAPSAP BTP

Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://{tenant}.authentication.sap.hana.ondemand.com/oauth/token

Flows
clientCredentials

Scopes (0)

SAP Integration Suite 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 Integration Suite APIs use OAuth 2.0 client credentials with role-based authorization rather than published OAuth scopes; access to each API resource is granted by assigning documented role templates (for example MonitoringDataRead or WorkspacePackagesRead) to the SAP BTP service instance, per https://help.sap.com/docs/integration-suite/sap-integration-suite/tasks-and-permissions-556d5575d4b0483e85d4f3251f21d0ec.

📄 Provider scope reference: https://help.sap.com/docs/integration-suite/sap-integration-suite/tasks-and-permissions-556d5575d4b0483e85d4f3251f21d0ec

Source

OAuth Scopes

generated: '2026-07-11'
method: derived
source: openapi/sap-integration-suite-api-management-openapi.yml, openapi/sap-integration-suite-cloud-integration-openapi.yml
docs: https://help.sap.com/docs/integration-suite/sap-integration-suite/tasks-and-permissions-556d5575d4b0483e85d4f3251f21d0ec
note: >-
  SAP Integration Suite APIs use OAuth 2.0 client credentials with role-based
  authorization rather than published OAuth scopes; access to each API resource
  is granted by assigning documented role templates (for example
  MonitoringDataRead or WorkspacePackagesRead) to the SAP BTP service instance,
  per
  https://help.sap.com/docs/integration-suite/sap-integration-suite/tasks-and-permissions-556d5575d4b0483e85d4f3251f21d0ec.
schemes:
- name: oauth2
  source: openapi/sap-integration-suite-api-management-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://{tenant}.authentication.sap.hana.ondemand.com/oauth/token
- name: oauth2
  source: openapi/sap-integration-suite-cloud-integration-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://{tenant}.authentication.sap.hana.ondemand.com/oauth/token
scopes: []

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/sap-integration-suite-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 email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.