Actively · OAuth Scopes

Actively OAuth Scopes

OAuth 2.0 probed

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

CompanyAi AppsAI AgentsRevenue IntelligenceSalesGo-To-MarketMCPAuthenticationSales IntelligenceEnterprise Software
Scopes: 0 Flows: Method: probed

Scopes (0)

Actively 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

actively-scopes.yml Raw ↑ 
generated: '2026-08-13'
method: probed
source: https://auth.actively.ai/.well-known/oauth-authorization-server
docs: null
docs_note: >-
  Actively publishes no scopes/permissions reference page. The scope list below
  is read verbatim from the authorization server's own scopes_supported array,
  which is the only published source.
description: >-
  OAuth scopes advertised by Actively's authorization server
  (https://auth.actively.ai), which fronts the hosted MCP server at
  https://api.actively.ai/mcp. The advertised set is the standard OpenID
  Connect quartet only — there are NO product-specific or resource-scoped
  permissions published. Whatever authorization Actively applies to
  per-account agent data is enforced server-side and is not expressed as
  OAuth scopes a client can request or a reviewer can inspect.
authorization_server: https://auth.actively.ai
resource: https://api.actively.ai/mcp
scope_count: 4
scopes:
- name: openid
  type: openid-connect
  description: >-
    Standard OIDC scope. Requests an ID token identifying the authenticated
    Actively user.
  source: scopes_supported
- name: profile
  type: openid-connect
  description: >-
    Standard OIDC scope. Grants access to basic profile claims via
    https://auth.actively.ai/oauth2/userinfo.
  source: scopes_supported
- name: email
  type: openid-connect
  description: >-
    Standard OIDC scope. Grants access to the user's email address claim.
  source: scopes_supported
- name: offline_access
  type: openid-connect
  description: >-
    Standard OIDC scope. Requests a refresh token so an agent can maintain a
    long-lived session against the MCP server without re-consent.
  source: scopes_supported
findings:
- >-
  NO RESOURCE SCOPES. The MCP resource https://api.actively.ai/mcp is
  protected, but no scope in the published set names it or any Actively data
  object (accounts, agents, memory, strategy, research). A client cannot
  request least-privilege access, and a security reviewer cannot tell from the
  token what an agent is permitted to read or write.
- >-
  This matters more than usual for this provider: the product connects
  autonomous per-account agents to CRM-derived revenue data in third-party AI
  clients (ChatGPT, Claude, Cowork). Scope granularity is the control surface
  a customer would use to bound that, and it is not published.
- >-
  Publishing resource-specific scopes (e.g. accounts:read, strategy:read,
  memory:write) in scopes_supported would be a low-cost, high-value addition
  and is the single clearest gap in an otherwise spec-clean OAuth
  implementation.
evidence:
- fetched: '2026-08-13'
  url: https://auth.actively.ai/.well-known/oauth-authorization-server
  http_status: 200
  quote: '"scopes_supported": ["email", "offline_access", "openid", "profile"]'
- fetched: '2026-08-13'
  url: https://auth.actively.ai/.well-known/openid-configuration
  http_status: 200
  quote: '"scopes_supported": ["email", "offline_access", "openid", "profile"]'
- fetched: '2026-08-13'
  url: https://api.actively.ai/.well-known/oauth-authorization-server
  http_status: 200
  note: >-
    The api-host mirror omits scopes_supported entirely, so the auth host is
    the authoritative source.

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/actively-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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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