Leena AI · OAuth Scopes

Leena AI OAuth Scopes

OAuth 2.0 searched

Leena AI uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

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 MlAgentic AIArtificial IntelligenceEnterprise SoftwareHuman ResourcesITSMEmployee ExperienceWorkflow-AutomationConversational AIMCPKnowledge-Management
Scopes: 0 Flows: Method: searched

Scopes (0)

Leena AI implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

📄 Provider scope reference: https://docs.leena.ai/docs/audit-logs-external-api-authentication-usage-guide-beta

Source

OAuth Scopes

Raw ↑ 
generated: '2026-07-19'
method: searched
docs: https://docs.leena.ai/docs/audit-logs-external-api-authentication-usage-guide-beta
source: https://docs.leena.ai/docs/audit-logs-external-api-authentication-usage-guide-beta
summary: >-
  Leena AI's external APIs are OAuth 2.0 protected and the documentation names one concrete
  scope. Leena AI does not publish a consolidated scope reference page, so only the scope
  it documents explicitly is recorded here. Insufficient scope is signalled as HTTP 401
  with the message "Insufficient OAuth scope" rather than the more usual 403.
oauth_flow: password
token_endpoint: 'https://<region-code>-acl.leena.ai/api/v1.0/oauth/token'
scopes:
  - name: audit-logs:read
    description: Read audit log records via GET /external/v1/audit-logs.
    api: openapi/leena-ai-audit-logs-openapi.yml
    operations:
      - listAuditLogs
    source: https://docs.leena.ai/docs/audit-logs-external-api-authentication-usage-guide-beta
naming_convention:
  pattern: '<resource>:<action>'
  observed:
    - audit-logs:read
  note: >-
    Only one scope is publicly documented. The External AOP API returns 403 "insufficient
    scope" on its execute and status operations, implying additional scopes exist, but
    Leena AI does not publish their names — they are deliberately not guessed here.
enforcement:
  insufficient_scope_status: 401
  insufficient_scope_message: Insufficient OAuth scope
gaps:
  - No public consolidated OAuth scope / permissions reference page.
  - AOP execute and status scope names are not published.

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/leena-ai-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 email required.

GitHub Google LinkedIn

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