Prove · OAuth Scopes

Prove OAuth Scopes

OAuth 2.0 derived

Prove 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.prove.com/v3/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.

Identity VerificationAuthenticationPhone IntelligenceKYCFraud Prevention

Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://api.prove.com/v3/token

Flows
clientCredentials

Scopes (0)

Prove 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.

Prove's API uses an OAuth 2.0 client_credentials flow with no published scopes - access is governed by the client_id/client_secret credentials themselves, and Prove's official server SDKs request tokens with an empty scope list (see https://developer.prove.com/tutorial/access-api-keys and https://github.com/prove-identity/prove-sdk-server-go).

📄 Provider scope reference: https://developer.prove.com/tutorial/access-api-keys

Source

OAuth Scopes

generated: '2026-07-11'
method: derived
source: openapi/prove-openapi.yml
docs: https://developer.prove.com/tutorial/access-api-keys
note: Prove's API uses an OAuth 2.0 client_credentials flow with no published scopes
  - access is governed by the client_id/client_secret credentials themselves, and
  Prove's official server SDKs request tokens with an empty scope list (see
  https://developer.prove.com/tutorial/access-api-keys and
  https://github.com/prove-identity/prove-sdk-server-go).
schemes:
- name: oauth2
  source: openapi/prove-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.prove.com/v3/token
scopes: []