Revenue.io · OAuth Scopes

Revenue.io OAuth Scopes

OAuth 2.0 probed

Revenue.io publishes 1 OAuth 2.0 scope via the authorizationCode flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Revenue.io API on a user’s behalf.

Tokens are issued from https://app.ringdna.com/mcp/oauth/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.

Revenue IntelligenceSales EngagementConversation IntelligenceRevenue OperationsCall AnalyticsReal-Time GuidanceCRM IntegrationSalesforce

Scopes: 1 Flows: authorizationCode Method: probed

OAuth endpoints

Authorization URL
https://app.ringdna.com/mcp/oauth/authorize

Token URL
https://app.ringdna.com/mcp/oauth/token

Flows
authorizationCode

Scopes (1)

Scope	Description	Flows
mcp	The only value in scopes_supported. Advertised by both the authorization server metadata and the protected-resource metadata for https://app.ringdna.com/mcp. Coarse-grained: one scope covers the entire MCP tool surface, with no read/write or per-resource separation published.	authorizationCode

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-13'
method: probed
source: https://api.revenue.io/.well-known/oauth-authorization-server
note: >-
  Derived from live RFC 8414 authorization-server metadata, not from an OpenAPI —
  Revenue.io publishes no machine-readable spec. Revenue.io publishes no scopes
  or permissions reference page in its knowledge center; the single scope below
  is everything the provider advertises. A granular scope model, if one exists
  behind the OAuth flow, is not published.
schemes:
  - name: mcp-oauth2
    source: well-known/revenue-io-oauth-authorization-server.json
    issuer: https://app.ringdna.com
    flows:
      - flow: authorizationCode
        authorizationUrl: https://app.ringdna.com/mcp/oauth/authorize
        tokenUrl: https://app.ringdna.com/mcp/oauth/token
        pkce: S256
scopes:
  - scope: mcp
    description: >-
      The only value in scopes_supported. Advertised by both the authorization
      server metadata and the protected-resource metadata for
      https://app.ringdna.com/mcp. Coarse-grained: one scope covers the entire
      MCP tool surface, with no read/write or per-resource separation published.
    flows: [authorizationCode]
    sources:
      - well-known/revenue-io-oauth-authorization-server.json
      - well-known/revenue-io-oauth-protected-resource.json
summary:
  scope_count: 1
  granularity: coarse
  docs_page: null

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/revenue-io-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.