Appsmith · Authentication Profile
Appsmith Authentication
Authentication
Appsmith secures its APIs with cookie, http-bearer, and apiKey across 3 declared security schemes, as derived from its OpenAPI definitions.
Low-CodeOpen-SourceInternal ToolsWorkflow-AutomationDeveloper Tools
Methods: cookie, http-bearer, apiKey
Schemes: 3
OAuth flows:
API key in:
Security Schemes
editorSession cookie
· in: cookie ()
mcpToken http
scheme: bearer
scimApiKey apiKey
· in: header ()
Source
Authentication Profile
generated: '2026-09-04'
method: searched
source: https://docs.appsmith.com + appsmithorg/appsmith source + live probes of https://app.appsmith.com/api/v1
name: Appsmith authentication
note: 'Upgraded from a derived profile that read a single bearerAuth scheme out of the scaffold OpenAPI in this repository.
Appsmith has no general-purpose REST API key: there are three distinct credential kinds, each scoped to a different
surface.'
summary:
types:
- cookie
- http-bearer
- apiKey
public_api_key: false
schemes:
- name: editorSession
type: cookie
in: cookie
surface: https://app.appsmith.com/api/v1
description: Session cookie established by the browser sign-in flow (form login, Google SSO on Free, SAML/OIDC on
Enterprise). This is what the /api/v1 platform API actually authenticates. Unauthenticated calls return the anonymousUser
identity (GET /api/v1/users/me -> 200 with "email":"anonymousUser") or 401.
documented_as_public_api: false
evidence: https://app.appsmith.com/api/v1/users/me (HTTP 200, 2026-09-04)
- name: mcpToken
type: http
scheme: bearer
prefix: mcp_
surface: https://{your-appsmith-instance}/mcp
description: Per-user MCP bearer token created at Profile -> MCP tokens. Every tool call it authorizes stays bounded
by that user's own ACL. Rejected with 401 and non-creatable while APPSMITH_MCP_ENABLED is off; authentication
attempts are throttled to 5 per minute.
source: https://github.com/appsmithorg/appsmith/blob/release/app/client/packages/mcp/README.md
- name: scimApiKey
type: apiKey
in: header
header: Authorization
surface: https://{your-domain}/scim
description: API key generated in the Appsmith admin UI ("API key to setup SCIM") and configured in the identity
provider for SCIM 2.0 user and group provisioning. Enterprise plan.
source: https://docs.appsmith.com/advanced-concepts/user-provisioning-group-sync
instance_sso:
free:
- Google SSO
enterprise:
- SAML 2.0
- OIDC
source: https://www.appsmith.com/pricing
recovery: appsmithctl enable-form-login re-enables email/password sign-in if SSO configuration locks an instance
out.
datasource_auth:
note: 'Distinct from platform auth: Appsmith CONSUMES auth on behalf of apps — Authenticated API datasources support
API keys, bearer tokens, basic auth and OAuth 2.0, with credentials stored server-side rather than in the app
definition.'
source: https://docs.appsmith.com/connect-data/reference/authenticated-api
oauth_scopes:
published: false
note: Appsmith is an OAuth relying party, not an authorization server; there is no scope surface to document.
evidence:
- url: https://app.appsmith.com/api/v1/users/me
http_status: 200
- url: https://app.appsmith.com/api/v1/workspaces
http_status: 401
- url: https://docs.appsmith.com/advanced-concepts/user-provisioning-group-sync
http_status: 200
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.
Call it yourself
curl for this page
This security artifact
curl "https://apis.io/api/v1/security/appsmith-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.
A second provider on the same verified email joins the account you already have.