Accurate Background · OAuth Scopes
Accurate Background OAuth Scopes
OAuth 2.0
derived
Accurate Background 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.accuratebackground.com/v3/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 ChecksEmployment ScreeningIdentity VerificationComplianceHR TechScreening
Scopes: 0
Flows: clientCredentials
Method: derived
OAuth endpoints
Token URL
https://api.accuratebackground.com/v3/oauth/token
https://api.accuratebackground.com/v3/oauth/token
Flows
clientCredentials
clientCredentials
Scopes (0)
Accurate Background 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.
Accurate's API authenticates via an OAuth 2.0 client-credentials exchange of a ClientID/ClientSecret pair from the developer portal, and no OAuth scopes are documented anywhere in the API reference or developer portal (https://accurate.readme.io/reference/authentication).
Accurate's API authenticates via an OAuth 2.0 client-credentials exchange of a ClientID/ClientSecret pair from the developer portal, and no OAuth scopes are documented anywhere in the API reference or developer portal (https://accurate.readme.io/reference/authentication).
📄 Provider scope reference: https://accurate.readme.io/reference/authentication