VoiceOps · OAuth Scopes

VoiceOps OAuth Scopes

OAuth 2.0 probed

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

Tokens are issued from https://clerk.voiceops.com/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.

CompanyAi AppsConversation IntelligenceCall CentersSales CoachingCustomer ExperienceArtificial IntelligenceSpeech AnalyticsMCPAgents
Scopes: 6 Flows: authorizationCode Method: probed

OAuth endpoints

Authorization URL
https://clerk.voiceops.com/oauth/authorize
Token URL
https://clerk.voiceops.com/oauth/token
Flows
authorizationCode

Scopes (6)

ScopeDescriptionFlows
openid Issue an OpenID Connect ID token for the signed-in user. authorizationCode
profile Basic profile claims (name, given_name, family_name, picture, preferred_username). authorizationCode
email Email address and email_verified claim. authorizationCode
public_metadata Read the user's public metadata held by the identity provider. authorizationCode
private_metadata Read the user's private metadata held by the identity provider. authorizationCode
offline_access Issue a refresh token so the client can act without the user present. authorizationCode

Source

OAuth Scopes

voiceops-scopes.yml Raw ↑
generated: '2026-08-14'
method: probed
source: https://clerk.voiceops.com/.well-known/oauth-authorization-server
docs: https://clerk.com/docs/oauth/scoped-access
docs_note: >-
  The service_documentation URL in the authorization-server metadata points at
  Clerk's own documentation, not at a VoiceOps-authored scope reference —
  VoiceOps publishes none.
scope_source_caveat: >-
  IMPORTANT: these are the scopes advertised by the OpenID Connect / OAuth 2.0
  provider that signs users in to the VoiceOps application
  (clerk.voiceops.com, issuer https://clerk.voiceops.com, CNAME to
  frontend-api.clerk.services). They are Clerk's platform scoped-access
  vocabulary. They are NOT scopes on a VoiceOps business API, and they do NOT
  govern the remote MCP server at mcp.voiceops.com, which uses an API key with
  no scope surface at all.
schemes:
  - name: clerkOAuth2
    source: well-known/voiceops-oauth-authorization-server.json
    issuer: https://clerk.voiceops.com
    flows:
      - flow: authorizationCode
        authorizationUrl: https://clerk.voiceops.com/oauth/authorize
        tokenUrl: https://clerk.voiceops.com/oauth/token
scopes:
  - scope: openid
    description: Issue an OpenID Connect ID token for the signed-in user.
    flows: [authorizationCode]
    sources: [well-known/voiceops-oauth-authorization-server.json]
  - scope: profile
    description: Basic profile claims (name, given_name, family_name, picture, preferred_username).
    flows: [authorizationCode]
    sources: [well-known/voiceops-oauth-authorization-server.json]
  - scope: email
    description: Email address and email_verified claim.
    flows: [authorizationCode]
    sources: [well-known/voiceops-oauth-authorization-server.json]
  - scope: public_metadata
    description: Read the user's public metadata held by the identity provider.
    flows: [authorizationCode]
    sources: [well-known/voiceops-oauth-authorization-server.json]
  - scope: private_metadata
    description: Read the user's private metadata held by the identity provider.
    flows: [authorizationCode]
    sources: [well-known/voiceops-oauth-authorization-server.json]
  - scope: offline_access
    description: Issue a refresh token so the client can act without the user present.
    flows: [authorizationCode]
    sources: [well-known/voiceops-oauth-authorization-server.json]

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

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