Insider · OAuth Scopes

Insider OAuth Scopes

OAuth 2.0 searched

Insider 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://gw.useinsider.com/oauth2/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.

CompanyCustomer EngagementPersonalizationCustomer Data PlatformMarketingJourney OrchestrationOmnichannelCDPArtificial IntelligenceMessagingWhatsAppEmailSMSPush NotificationsRecommendationsSearchProduct CatalogAnalyticsMCPAgentsConsentGDPR

Scopes: 0 Flows: clientCredentials, authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://gw.useinsider.com/oauth2/authorize

Token URL
https://gw.useinsider.com/oauth2/token

Flows
clientCredentialsauthorizationCode

Scopes (0)

Insider 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: https://academy.insiderone.com/docs/set-up-insider-one-mcp

Source

OAuth Scopes

generated: '2026-08-13'
method: searched
source: https://academy.insiderone.com/docs/set-up-insider-one-mcp
docs: https://academy.insiderone.com/docs/set-up-insider-one-mcp
sources:
- https://academy.insiderone.com/docs/set-up-insider-one-mcp
- https://academy.insiderone.com/docs/insider-one-mcp-functions
- https://gw.useinsider.com/.well-known/oauth-authorization-server
- https://mcp.insiderone.com/.well-known/oauth-protected-resource
- openapi/insider-gateway-openapi.yml
authorization_server: https://gw.useinsider.com
protected_resource: https://gw.useinsider.com
scope_model: >-
  Insider One issues OAuth 2.0 credentials from the InOne panel (Settings > InOne Settings >
  Integration Settings > OAuth 2.0 Credentials) and the operator SELECTS SCOPES AT GENERATION TIME,
  one per channel. Insider One states plainly that "a tool is available only if the corresponding
  scope is included in the credential", so the scope set is the access-control boundary for both the
  gateway API and the MCP server.
published_scope_names: false
published_scope_names_note: >-
  The RFC 9728 protected-resource document advertises scopes_supported: ["*"] — a wildcard, not a
  list. Insider One does not publish the concrete scope strings anywhere public; they are only
  visible in the credential-generation screen. The channel-level GRANULARITY below is documented in
  the MCP setup and functions pages; the literal scope tokens are NOT, and are deliberately not
  guessed here.

schemes:
- name: OAuth2
  source: openapi/insider-gateway-openapi.yml
  flows:
  - {flow: clientCredentials, tokenUrl: 'https://gw.useinsider.com/oauth2/token'}
  - {flow: authorizationCode, authorizationUrl: 'https://gw.useinsider.com/oauth2/authorize', tokenUrl: 'https://gw.useinsider.com/oauth2/token'}
  pkce: [S256]
  revocation_endpoint: https://gw.useinsider.com/oauth2/revoke

scopes: []

scope_dimensions:
- {dimension: channel, values: [Email, SMS, WhatsApp, Web Push, Mobile App, Architect], evidence: 'MCP setup page: "Select the scopes you want to grant. For full MCP functionality, enable all available channels."'}
- {dimension: access, values: [read, write], evidence: 'MCP functions page: 28 read-only tools and 7 write tools, with write tools defaulting to needs-approval.'}
- {dimension: excluded, values: [OnSite], evidence: 'MCP functions page: "On-site is currently unsupported."'}

guidance:
- Create a dedicated OAuth 2.0 credential for each client (Insider One explicitly recommends against
  reusing credentials for MCP).
- The Client Secret is displayed once.
- Access tokens live up to 90 minutes; the refresh_token grant is supported.

gaps:
- No public scope reference page; scopes_supported is a wildcard.
- No OpenID Connect discovery document, so no scopes_supported from that direction either.

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