Ariba Guided Buying · OAuth Scopes
Ariba Guided Buying OAuth Scopes
OAuth 2.0
derived
Ariba Guided Buying 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.ariba.com/v2/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.
B2BCatalogERPProcurementRequisitionsSAPSupply Chain
Scopes: 0
Flows: clientCredentials
Method: derived
OAuth endpoints
Token URL
https://api.ariba.com/v2/oauth/token
https://api.ariba.com/v2/oauth/token
Flows
clientCredentials
clientCredentials
Scopes (0)
Ariba Guided Buying 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 Ariba APIs use two-legged OAuth (client credentials / grant_type=openapi_2lo) with a per-application OAuth client ID plus Application Key, and access is granted per API through SAP Ariba approval rather than OAuth scopes; no scopes are documented (https://help.sap.com/docs/ariba-apis/help-for-sap-ariba-developer-portal/sap-ariba-developer-portal-authentication).
SAP Ariba APIs use two-legged OAuth (client credentials / grant_type=openapi_2lo) with a per-application OAuth client ID plus Application Key, and access is granted per API through SAP Ariba approval rather than OAuth scopes; no scopes are documented (https://help.sap.com/docs/ariba-apis/help-for-sap-ariba-developer-portal/sap-ariba-developer-portal-authentication).
📄 Provider scope reference: https://help.sap.com/docs/ariba-apis/help-for-sap-ariba-developer-portal/sap-ariba-developer-portal-authentication