Corebee · OAuth Scopes

Corebee OAuth Scopes

OAuth 2.0 searched

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

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 ServiceArtificial IntelligenceChatbotsHelp DeskOmnichannel MessagingVoice AgentsMCP

Scopes: 12 Flows: Method: searched

Scopes (12)

Scope	Description	Flows
conversations:read
conversations:write
contacts:read
contacts:write
contacts:delete
knowledge:read
knowledge:write
knowledge:delete
metrics:read
settings:read
settings:write
voice:bridge	Required by every voice/bridge operation; an all-access * key is not enough for some voice operations.

📄 Provider scope reference: https://corebee.ai/api/v1/openapi.json

Source

OAuth Scopes

generated: '2026-11-04'
method: searched
source: https://corebee.ai/.well-known/oauth-authorization-server
docs: https://corebee.ai/api/v1/openapi.json
name: Corebee OAuth scopes
note: OAuth 2.1 (authorization_code + refresh_token, PKCE S256, Dynamic Client Registration at https://corebee.ai/api/v1/mcp/oauth/register).
  The spec models auth as http bearer, so no oauth2 securityScheme exists to derive from; scopes are read
  from the authorization-server metadata. voice:bridge is named in the spec but not in scopes_supported
  (it is an API-key permission chosen when the key is minted).
scopes:
- name: conversations:read
  source: oauth-authorization-server scopes_supported
- name: conversations:write
  source: oauth-authorization-server scopes_supported
- name: contacts:read
  source: oauth-authorization-server scopes_supported
- name: contacts:write
  source: oauth-authorization-server scopes_supported
- name: contacts:delete
  source: oauth-authorization-server scopes_supported
- name: knowledge:read
  source: oauth-authorization-server scopes_supported
- name: knowledge:write
  source: oauth-authorization-server scopes_supported
- name: knowledge:delete
  source: oauth-authorization-server scopes_supported
- name: metrics:read
  source: oauth-authorization-server scopes_supported
- name: settings:read
  source: oauth-authorization-server scopes_supported
- name: settings:write
  source: oauth-authorization-server scopes_supported
- name: voice:bridge
  description: Required by every voice/bridge operation; an all-access * key is not enough for some voice
    operations.
  source: openapi bearerAuth description

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/corebee-ai-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.

GitHub Google LinkedIn

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