Sana · Authentication Profile

Sana Authentication

Authentication

Sana secures its APIs with oauth2 and http across 4 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials flow(s).

CompanyEnterprise AIArtificial IntelligenceLearning ManagementLMSKnowledge-ManagementAgentsSCIMxAPIREST API

Methods: oauth2, http Schemes: 4 OAuth flows: clientCredentials API key in:

Security Schemes

oauth2ClientCredentials oauth2

bearerAuth http

scheme: bearer

xapiOauth oauth2

scim2 bearer-or-basic

Source

Authentication Profile

generated: '2026-07-21'
method: searched
source: https://docs.sana.ai/api-docs/
docs: https://docs.sana.ai/api-docs/
summary:
  types: [oauth2, http]
  http_schemes: [bearer]
  oauth2_flows: [clientCredentials]
  scim: '2.0'
  sso: [saml2, oidc]
schemes:
  - name: oauth2ClientCredentials
    type: oauth2
    flow: clientCredentials
    token_url: https://{domain}.sana.ai/api/token
    grant_type: client_credentials
    credentials: [client_id, client_secret]
    scopes: [read, write]
    scope_delimiter: comma
    token_type: bearer
    token_lifetime_seconds: 3600
    note: >-
      Create an API client in Sana to obtain client_id/client_secret. GET requests
      require the `read` scope; POST/PATCH/DELETE require the `write` scope.
    sources: [https://docs.sana.ai/api-docs/]
  - name: bearerAuth
    type: http
    scheme: bearer
    applies_to: all REST endpoints
    header: 'Authorization: Bearer <accessToken>'
    sources: [openapi/sana-openapi.yml, https://docs.sana.ai/api-docs/]
  - name: xapiOauth
    type: oauth2
    flow: clientCredentials
    token_url: https://{domain}.sana.ai/api/oauth/token
    applies_to: xAPI statement submission (/xapi/v1/statements)
    sources: [https://docs.sana.ai/api-docs/]
  - name: scim2
    type: bearer-or-basic
    endpoint: https://{domain}.sana.ai/scim/v2
    version: '2.0'
    note: >-
      SCIM 2.0 user provisioning. Bearer (SCIM token, 1-year validity) for Microsoft
      Entra/Azure; Basic auth (Client ID / Client Secret) for Okta.
    sources: [https://help.sana.ai/en/articles/23062-how-to-configure-scim]
sso:
  protocols: [SAML 2.0, OIDC]
  providers: [Okta, Microsoft Entra, OneLogin, JumpCloud, Google Workspace, Auth0, Salesforce, ADFS, Ping Identity, CyberArk]
  docs: https://help.sana.ai/en/articles/23060-setting-up-sso

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact 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 security artifact

curl "https://apis.io/api/v1/security/sana-authentication"

All security posture

curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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.