Composio · Authentication Profile

Composio Authentication

Authentication

Composio secures its APIs with apiKey across 4 declared security schemes, as derived from its OpenAPI definitions.

AI AgentsAuthenticationIntegrationMCPSandboxToolsTriggersUnified-APIWebhook
Methods: apiKey Schemes: 4 OAuth flows: API key in: cookie, header

Security Schemes

ApiKeyAuth apiKey
· in: header (x-api-key)
UserApiKeyAuth apiKey
· in: header (x-user-api-key)
CookieAuth apiKey
· in: cookie (authToken)
OrgApiKeyAuth apiKey
· in: header (x-org-api-key)

Source

Authentication Profile

Raw ↑ 
generated: '2026-06-20'
method: searched
source: openapi/composio-openapi-original.json, openapi/composio-openapi-original.yml
docs: https://docs.composio.dev/faq/api_key/api_key
notes: >-
  The Composio platform API is API-key authenticated (project, user, and org keys via
  header, plus a cookie session for the dashboard). API keys can carry scoped
  permissions (e.g. MCP, files, realtime routes). Distinct from this, Composio manages
  OAuth2 flows on behalf of end users to connect third-party toolkits (delegated auth);
  those tokens are held by Composio and never exposed to the agent, so they are not a
  securityScheme on this API.
summary:
  types:
  - apiKey
  api_key_in:
  - cookie
  - header
schemes:
- name: ApiKeyAuth
  type: apiKey
  in: header
  parameter: x-api-key
  description: Project API key authentication
  sources:
  - openapi/composio-openapi-original.json
  - openapi/composio-openapi-original.yml
- name: UserApiKeyAuth
  type: apiKey
  in: header
  parameter: x-user-api-key
  description: User API key authentication
  sources:
  - openapi/composio-openapi-original.json
- name: CookieAuth
  type: apiKey
  in: cookie
  parameter: authToken
  description: Cookie-based session authentication
  sources:
  - openapi/composio-openapi-original.json
- name: OrgApiKeyAuth
  type: apiKey
  in: header
  parameter: x-org-api-key
  description: Organization API key authentication
  sources:
  - openapi/composio-openapi-original.json