SAP SuccessFactors · OAuth Scopes
SAP SuccessFactors OAuth Scopes
OAuth 2.0
derived
SAP SuccessFactors 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.successfactors.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.
HCMHRHuman ResourcesTalent ManagementPayrollEnterpriseSAP
Scopes: 0
Flows: clientCredentials
Method: derived
OAuth endpoints
Token URL
https://api.successfactors.com/oauth/token
https://api.successfactors.com/oauth/token
Flows
clientCredentials
clientCredentials
Scopes (0)
SAP SuccessFactors 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 SuccessFactors OAuth 2.0 (SAML bearer assertion flow) does not use published OAuth scopes; access tokens carry an empty scope and API authorization is governed by the role-based permissions (RBP) of the user identified in the SAML assertion (https://help.sap.com/docs/successfactors-platform/sap-successfactors-api-reference-guide-odata-v2/authentication-using-oauth-2-0).
SAP SuccessFactors OAuth 2.0 (SAML bearer assertion flow) does not use published OAuth scopes; access tokens carry an empty scope and API authorization is governed by the role-based permissions (RBP) of the user identified in the SAML assertion (https://help.sap.com/docs/successfactors-platform/sap-successfactors-api-reference-guide-odata-v2/authentication-using-oauth-2-0).
📄 Provider scope reference: https://help.sap.com/docs/successfactors-platform/sap-successfactors-api-reference-guide-odata-v2/authentication-using-oauth-2-0