Ariba Sourcing · OAuth Scopes
Ariba Sourcing OAuth Scopes
OAuth 2.0
derived
Ariba Sourcing 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.
ApprovalsAuctionsB2BContractsProcurementRFxSAPSourcingSupplier ManagementSupply 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 Sourcing 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 a two-legged OAuth client credentials flow (grant_type=client_credentials) with no scope parameter; access is governed by per-API access requests, application keys, and realm approval rather than documented OAuth scopes (https://help.sap.com/docs/ariba-apis/help-for-sap-ariba-developer-portal/use-of-api-gateway-and-oauth-to-authenticate-applications).
SAP Ariba APIs use a two-legged OAuth client credentials flow (grant_type=client_credentials) with no scope parameter; access is governed by per-API access requests, application keys, and realm approval rather than documented OAuth scopes (https://help.sap.com/docs/ariba-apis/help-for-sap-ariba-developer-portal/use-of-api-gateway-and-oauth-to-authenticate-applications).
📄 Provider scope reference: https://help.sap.com/docs/ariba-apis/help-for-sap-ariba-developer-portal/use-of-api-gateway-and-oauth-to-authenticate-applications