Snov.io · OAuth Scopes

Snov.io OAuth Scopes

OAuth 2.0 derived

Snov.io 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.snov.io/v1/oauth/access_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.

Sales EngagementEmail FinderEmail VerificationProspectingDrip CampaignsCRMLead Generation

Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://api.snov.io/v1/oauth/access_token

Flows
clientCredentials

Scopes (0)

Snov.io 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.

Snov.io uses an OAuth2 client_credentials flow that exchanges an API User ID and Secret for a Bearer token with no scope parameter; no OAuth scopes are documented, with access governed by the account plan (https://snov.io/api).

📄 Provider scope reference: https://snov.io/api

Source

OAuth Scopes

generated: '2026-07-11'
method: derived
source: openapi/snov-openapi.yml
docs: https://snov.io/api
note: Snov.io uses an OAuth2 client_credentials flow that exchanges an API User ID
  and Secret for a Bearer token with no scope parameter; no OAuth scopes are documented,
  with access governed by the account plan (https://snov.io/api).
schemes:
- name: OAuth2
  source: openapi/snov-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.snov.io/v1/oauth/access_token
  description: OAuth2 client_credentials flow. POST client_id and client_secret to /v1/oauth/access_token
    to obtain a Bearer token, then send it in the Authorization header.
scopes: []