Session AI · OAuth Scopes

Session AI OAuth Scopes

OAuth 2.0 probed

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

Tokens are issued from https://jsaqyxhgmkgcyaocjnzz.supabase.co/auth/v1/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.

CompanyArtificial IntelligenceEcommerceRetailPersonalizationMarketingAgentic AIDecisioningCustomer DataEventsReal TimeMCP

Scopes: 5 Flows: authorizationCode Method: probed

OAuth endpoints

Authorization URL
https://jsaqyxhgmkgcyaocjnzz.supabase.co/auth/v1/oauth/authorize

Token URL
https://jsaqyxhgmkgcyaocjnzz.supabase.co/auth/v1/oauth/token

Flows
authorizationCode

Scopes (5)

Scope	Description	Flows
openid	OpenID Connect sign-in; returns an ID token for the authenticated subject.	authorizationCode
profile	Access to the authenticated user's basic profile claims.	authorizationCode
email	Access to the authenticated user's email claim.	authorizationCode
phone	Access to the authenticated user's phone claim.	authorizationCode
offline_access	Issues a refresh token so the client can act without the user present.	authorizationCode

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-13'
method: probed
source: https://jsaqyxhgmkgcyaocjnzz.supabase.co/auth/v1/.well-known/oauth-authorization-server
note: >-
  Scopes are read from the live RFC 8414 authorization-server metadata that Session AI's
  own RFC 9728 protected-resource metadata names for its MCP server. Session AI publishes
  no scopes reference page of its own, and these are the generic OIDC scopes advertised by
  the authorization server rather than Session AI product permissions. The REST platform
  API is API-key authenticated and has no OAuth scope surface at all.
applies_to: https://sessionai.com/mcp
schemes:
- name: mcp-oauth
  issuer: https://jsaqyxhgmkgcyaocjnzz.supabase.co/auth/v1
  source: well-known/sessionai-oauth-authorization-server.json
  flows:
  - flow: authorizationCode
    authorizationUrl: https://jsaqyxhgmkgcyaocjnzz.supabase.co/auth/v1/oauth/authorize
    tokenUrl: https://jsaqyxhgmkgcyaocjnzz.supabase.co/auth/v1/oauth/token
scopes:
- scope: openid
  description: OpenID Connect sign-in; returns an ID token for the authenticated subject.
  flows: [authorizationCode]
- scope: profile
  description: Access to the authenticated user's basic profile claims.
  flows: [authorizationCode]
- scope: email
  description: Access to the authenticated user's email claim.
  flows: [authorizationCode]
- scope: phone
  description: Access to the authenticated user's phone claim.
  flows: [authorizationCode]
- scope: offline_access
  description: Issues a refresh token so the client can act without the user present.
  flows: [authorizationCode]
scope_count: 5
product_scopes_published: false