Fireflies.ai · OAuth Scopes

Fireflies.ai OAuth Scopes

OAuth 2.0 searched

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

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

CompanyMeetingsTranscriptionSpeech to TextConversation IntelligenceArtificial IntelligenceGraphQLMCPProductivity

Scopes: 2 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://api.fireflies.ai/authorize

Token URL
https://api.fireflies.ai/token

Flows
authorizationCode

Scopes (2)

Scope	Description	Flows
profile	Access to profile information.	authorizationCode
email	Access to the account email address.	authorizationCode

📄 Provider scope reference: https://docs.fireflies.ai/fundamentals/authorization

Source

OAuth Scopes

generated: '2026-07-19'
method: searched
source: https://api.fireflies.ai/.well-known/oauth-authorization-server
docs: https://docs.fireflies.ai/fundamentals/authorization
schemes:
  - name: oauth2
    source: well-known/fireflies-ai-oauth-authorization-server.json
    flows:
      - flow: authorizationCode
        authorizationUrl: https://api.fireflies.ai/authorize
        tokenUrl: https://api.fireflies.ai/token
        pkce: S256
scopes:
  - scope: profile
    description: Access to profile information.
    flows: [authorizationCode]
    sources: [well-known/fireflies-ai-oauth-authorization-server.json]
  - scope: email
    description: Access to the account email address.
    flows: [authorizationCode]
    sources: [well-known/fireflies-ai-oauth-authorization-server.json]
notes: >-
  Scopes are those advertised in the RFC 8414 authorization-server metadata
  (scopes_supported: profile, email). The bearer-token GraphQL API itself is not
  scope-gated; access is governed by team role and plan tier.