Pocus · OAuth Scopes

Pocus OAuth Scopes

OAuth 2.0 probed

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

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.

CompanySales IntelligenceProduct-Led SalesRevenue OperationsGo-To-MarketData EnrichmentCRMArtificial IntelligenceGraphQL

Scopes: 0 Flows: Method: probed

Scopes (0)

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

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-26'
method: probed
source: >-
  https://auth.pocus.com/.well-known/openid-configuration and
  https://auth.pocus.com/.well-known/oauth-authorization-server, both HTTP 200, fetched 2026-08-26
docs: null
docs_note: >-
  Pocus publishes no scopes/permissions reference page. The scope list below is read directly from
  the authorization server's own advertised metadata (`scopes_supported`) and nothing has been
  added to it.
name: Pocus OAuth 2.0 scopes
description: >-
  The Pocus authorization server advertises only the three standard OpenID Connect scopes. No
  product-level or resource-level scopes (read/write over accounts, playbooks, lists, signals) are
  advertised, which means the published OAuth surface authenticates a user but does not express any
  granular authorization for the Pocus data API.

issuer: https://auth.pocus.com
authorization_endpoint: https://auth.pocus.com/oauth/authorize
token_endpoint: https://auth.pocus.com/oauth/token

scopes:
- name: openid
  description: >-
    Standard OpenID Connect scope requesting an ID token. Required to use the OIDC layer.
  standard: OpenID Connect Core 1.0
  source: scopes_supported
- name: profile
  description: >-
    Standard OIDC claim scope granting access to the end user's default profile claims.
  standard: OpenID Connect Core 1.0
  source: scopes_supported
- name: email
  description: >-
    Standard OIDC claim scope granting access to the end user's email and email_verified claims.
  standard: OpenID Connect Core 1.0
  source: scopes_supported

scope_count: 3
product_scopes_published: 0

granted_grants:
- authorization_code
- refresh_token
- client_credentials
- 'urn:ietf:params:oauth:grant-type:token-exchange'
- 'urn:ietf:params:oauth:grant-type:device_code'

pkce:
  supported: true
  code_challenge_methods: [S256]

related_authorization_model:
  note: >-
    Pocus' actual permission model is role-based inside the workspace, not scope-based on the
    token. Roles and supplementary permissions are administered in Workspace Settings > User
    Management and are documented at https://docs.pocus.com/docs/permissions; Okta groups map onto
    those roles via SAML. That model is not expressed in OAuth scopes.
  docs: https://docs.pocus.com/docs/permissions

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/pocus-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.