Sterling · OAuth Scopes
Sterling OAuth Scopes
OAuth 2.0
derived
Sterling 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://auth.sterlingcheck.app/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.
Background ScreeningIdentity VerificationBackground CheckHR TechComplianceGated API
Scopes: 0
Flows: clientCredentials
Method: derived
OAuth endpoints
Token URL
https://auth.sterlingcheck.app/oauth/token
https://auth.sterlingcheck.app/oauth/token
Flows
clientCredentials
clientCredentials
Scopes (0)
Sterling 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.
Sterling's API uses OAuth2 client_credentials only (Base64 client_id:client_secret sent to the oauth token endpoint) and documents no scope parameter or scope list; access is governed by the Client ID/Client Secret issued per account and screening region (https://sterling.readme.io/reference/authentication).
Sterling's API uses OAuth2 client_credentials only (Base64 client_id:client_secret sent to the oauth token endpoint) and documents no scope parameter or scope list; access is governed by the Client ID/Client Secret issued per account and screening region (https://sterling.readme.io/reference/authentication).
📄 Provider scope reference: https://sterling.readme.io/reference/authentication