Read AI · OAuth Scopes

Read AI OAuth Scopes

OAuth 2.0 searched

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

Tokens are issued from https://authn.read.ai/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.

CompanyMeeting IntelligenceArtificial IntelligenceTranscriptionProductivityCollaborationModel Context ProtocolAgentsWebhooksSaaS

Scopes: 7 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://authn.read.ai/oauth2/auth

Token URL
https://authn.read.ai/oauth2/token

Flows
authorizationCode

Scopes (7)

Scope	Description	Flows
openid	OpenID Connect — request an ID token identifying the Read AI user.	authorizationCode
profile	Basic profile claims for the authenticated Read AI user.	authorizationCode
email	The user's primary email address claim.	authorizationCode
offline_access	Issue a refresh token so the client can renew the 10-minute access token without a new browser round trip.	authorizationCode
offline	Legacy alias for offline_access, advertised by the authorization server.	authorizationCode
meeting:read	Read access to the authenticated user's meeting reports — metadata, participants, summaries, chapter summaries, action items, key questions, topics, transcripts, metrics and recording download URLs. Backs GET /v1/meetings, GET /v1/meetings/{id} and GET /v1/meetings/{id}/live.	authorizationCode
mcp:execute	Permission to invoke tools on the Read AI MCP server at https://api.read.ai/mcp.	authorizationCode

📄 Provider scope reference: https://support.read.ai/hc/en-us/articles/49380809380371-API-Keys-Authentication

Source

OAuth Scopes

generated: '2026-08-05'
method: searched
source: https://api.read.ai/.well-known/oauth-protected-resource/mcp
docs: https://support.read.ai/hc/en-us/articles/49380809380371-API-Keys-Authentication
description: >-
  Scopes advertised by Read AI's OAuth 2.1 authorization server (authn.read.ai) and
  by the MCP resource server's RFC 9728 protected-resource metadata. Read AI does not
  publish a standalone scope-reference page; the descriptions below are the standard
  OIDC meanings plus the two Read-specific scopes named in the provider's
  registration example.
schemes:
  - name: OAuth2
    source: well-known/read-ai-oauth-authorization-server.json
    flows:
      - flow: authorizationCode
        authorizationUrl: https://authn.read.ai/oauth2/auth
        tokenUrl: https://authn.read.ai/oauth2/token
scopes:
  - scope: openid
    description: OpenID Connect — request an ID token identifying the Read AI user.
    flows: [authorizationCode]
    sources: [well-known/read-ai-openid-configuration.json]
  - scope: profile
    description: Basic profile claims for the authenticated Read AI user.
    flows: [authorizationCode]
    sources: [well-known/read-ai-openid-configuration.json]
  - scope: email
    description: The user's primary email address claim.
    flows: [authorizationCode]
    sources: [well-known/read-ai-openid-configuration.json]
  - scope: offline_access
    description: >-
      Issue a refresh token so the client can renew the 10-minute access token
      without a new browser round trip.
    flows: [authorizationCode]
    sources: [well-known/read-ai-openid-configuration.json]
  - scope: offline
    description: Legacy alias for offline_access, advertised by the authorization server.
    flows: [authorizationCode]
    sources: [well-known/read-ai-oauth-authorization-server.json]
  - scope: 'meeting:read'
    description: >-
      Read access to the authenticated user's meeting reports — metadata,
      participants, summaries, chapter summaries, action items, key questions,
      topics, transcripts, metrics and recording download URLs. Backs GET
      /v1/meetings, GET /v1/meetings/{id} and GET /v1/meetings/{id}/live.
    flows: [authorizationCode]
    sources:
      - well-known/read-ai-oauth-protected-resource-mcp.json
      - https://support.read.ai/hc/en-us/articles/49380809380371-API-Keys-Authentication
  - scope: 'mcp:execute'
    description: >-
      Permission to invoke tools on the Read AI MCP server at https://api.read.ai/mcp.
    flows: [authorizationCode]
    sources:
      - well-known/read-ai-oauth-protected-resource-mcp.json
      - https://support.read.ai/hc/en-us/articles/49380809380371-API-Keys-Authentication
audience:
  - https://api.read.ai/v1/meetings
  - https://api.read.ai/mcp
notes:
  - >-
    Read AI's own dynamic-client-registration example requests the full set:
    "openid email offline_access profile meeting:read mcp:execute".
  - >-
    No write scopes are advertised. The public API surface is read-only over meeting
    data; every documented endpoint is a GET.
x-evidence:
  fetched: '2026-08-05'
  url: https://api.read.ai/.well-known/oauth-protected-resource/mcp
  http_status: 200