CaptivateIQ · OAuth Scopes

CaptivateIQ OAuth Scopes

OAuth 2.0 probed

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

CompanyCloud SaasSales CommissionsIncentive Compensation ManagementSales Performance ManagementRevenue OperationsFinancePayoutsCommission PlansSales Compensation

Scopes: 0 Flows: Method: probed

Scopes (0)

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

These scopes were read from CaptivateIQ's own RFC 8414 authorization-server metadata document (HTTP 200, application/json), NOT from the OpenAPI and NOT from the docs. The public developer reference documents only static token auth ("Authorization: Token ") and never mentions OAuth, so there is no scopes/permissions reference page to enrich this from — the OAuth surface is served but undocumented. The server advertises exactly one scope, `read`, which means the OAuth path as published is read-only and cannot authorize any of the write operations (create/update/delete/batch/import) in the ciq/v1 OpenAPI; those require a static API token. Do not infer additional scopes: the metadata document names one.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-13'
method: probed
source: https://app.captivateiq.com/.well-known/oauth-authorization-server
docs: null
verbatim: well-known/captivateiq-oauth-authorization-server.json
note: >-
  These scopes were read from CaptivateIQ's own RFC 8414 authorization-server metadata document
  (HTTP 200, application/json), NOT from the OpenAPI and NOT from the docs. The public developer
  reference documents only static token auth ("Authorization: Token <value>") and never mentions
  OAuth, so there is no scopes/permissions reference page to enrich this from — the OAuth surface
  is served but undocumented. The server advertises exactly one scope, `read`, which means the
  OAuth path as published is read-only and cannot authorize any of the write operations
  (create/update/delete/batch/import) in the ciq/v1 OpenAPI; those require a static API token.
  Do not infer additional scopes: the metadata document names one.
issuer: https://app.captivateiq.com
authorization_endpoint: https://app.captivateiq.com/o/authorize/
token_endpoint: https://app.captivateiq.com/o/token/
revocation_endpoint: https://app.captivateiq.com/o/revoke_token/
introspection_endpoint: https://app.captivateiq.com/o/introspect/
grant_types_supported:
- authorization_code
- refresh_token
response_types_supported:
- code
code_challenge_methods_supported:
- S256
token_endpoint_auth_methods_supported:
- none
- client_secret_post
- client_secret_basic
client_id_metadata_document_supported: true
scope_count: 1
scopes:
- name: read
  description: >-
    The only scope advertised in scopes_supported. Description is not published by the
    provider; no scope reference page exists.
  source: scopes_supported in the RFC 8414 metadata document
  documented_by_provider: false
gaps:
- No write scope is advertised, so OAuth clients cannot perform ciq/v1 write operations.
- No scope-to-operation mapping is published; the OpenAPI declares only the apiKey scheme.
- No /.well-known/openid-configuration and no jwks.json (404) — OAuth 2.0 only, not OIDC.
evidence:
- url: https://app.captivateiq.com/.well-known/oauth-authorization-server
  status: 200
- url: https://app.captivateiq.com/.well-known/openid-configuration
  status: 404

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/captivateiq-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.