confcall · OAuth Scopes

confcall OAuth Scopes

OAuth 2.0 searched

confcall publishes 5 OAuth 2.0 scopes via the clientCredentials flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the confcall API on a user’s behalf.

Tokens are issued from https://auth.confcall.app/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.

CompanyVideo ConferencingAI AgentsEmbeddable WidgetsTelephonyTranscriptionMCPCommunications
Scopes: 5 Flows: clientCredentials Method: searched

OAuth endpoints

Token URL
https://auth.confcall.app/oauth/token
Flows
clientCredentials

Scopes (5)

ScopeDescriptionFlows
confcall:history Read meeting artifacts (transcripts, summaries, action items) clientCredentials
confcall:rooms Manage rooms and invite/remove the AI agent clientCredentials
use:chat-agent Chat sessions (agent-widget JWT)
use:voice-agent Voice calls (agent-widget JWT)
read:ivr-config IVR config access (agent-widget JWT)

Source

OAuth Scopes

Raw ↑
generated: '2026-11-04'
method: searched
source: https://docs.confcall.app/api-reference.html
schemes:
- name: OAuth2ClientCredentials
  source: openapi/confcall-app-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.confcall.app/oauth/token
  description: 'OAuth 2.0 client-credentials grant. Exchange a client id/secret at
    the token URL for a short-lived bearer JWT and send it as `Authorization: Bearer
    <token>`. Operations with x-auth jwtOrApiKey accept either this or ApiKeyAuth;
    x-auth jwt operations need a user-context token.'
scopes:
- scope: confcall:history
  description: Read meeting artifacts (transcripts, summaries, action items)
  flows:
  - clientCredentials
  sources:
  - openapi/confcall-app-openapi.yml
  - https://docs.confcall.app/api-reference.html
  operations:
  - listRoomArtifacts
  - getArtifact
- scope: confcall:rooms
  description: Manage rooms and invite/remove the AI agent
  flows:
  - clientCredentials
  sources:
  - openapi/confcall-app-openapi.yml
  - https://docs.confcall.app/api-reference.html
  operations:
  - deleteRoom
  - inviteAiAgent
  - removeAiAgent
- scope: use:chat-agent
  description: Chat sessions (agent-widget JWT)
  flows: []
  token: short-lived JWT passed to <agent-widget> auth-token
  sources:
  - https://docs.confcall.app/agent-widget.html
- scope: use:voice-agent
  description: Voice calls (agent-widget JWT)
  flows: []
  token: short-lived JWT passed to <agent-widget> auth-token
  sources:
  - https://docs.confcall.app/agent-widget.html
- scope: read:ivr-config
  description: IVR config access (agent-widget JWT)
  flows: []
  token: short-lived JWT passed to <agent-widget> auth-token
  sources:
  - https://docs.confcall.app/agent-widget.html
docs: https://docs.confcall.app/api-reference.html
note: confcall:* scopes are declared in the OpenAPI and tagged per route on the API
  reference; use:*/read:* scopes are documented only for the <agent-widget> JWT (agent.confcall.app),
  not in the control-plane contract.

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/confcall-app-scopes"
All oauth scopes
curl "https://apis.io/api/v1/scopes?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

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