Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

next
md 35 lines 1.83 KB
Rendered Raw
1 ---
2 type: "troubleshooting"
3 title: "Project API Key Permissions"
4 description: "Public guidance for scoped Project API key permissions."
5 category: "authentication"
6 visibility: "public"
7 timestamp: "2026-07-16T00:00:00Z"
8 tags:
9 - "api-keys"
10 - "permissions"
11 - "sessions"
12 - "tool-router"
13 ---
14 # Project API Key Permissions
15
16 ## Proxy Execute requires an explicitly allowed Project API key
17
18 Create a scoped Project API key in the Dashboard and enable **Proxy Execute**
19 during key creation before calling the v3.1 Proxy Execute API. If a request is
20 denied, verify the key's scope before debugging the provider connection. Use a
21 fresh request ID from the correctly scoped key when escalation is still needed.
22
23 ## Tool Router session creation requires Sessions write access
24
25 For scoped Project API keys, creating a session through `composio.sessions.create(...)` or `POST /api/v3.1/tool_router/session` requires the Sessions permission with write or read/write access.
26
27 A key can successfully call `GET /api/v3.1/toolkits` with Toolkits read access and still be unable to create a session. The SDK can surface a scoped-permission denial as a generic 401 `Invalid API key`.
28
29 Create a new Project API key with Sessions set to Read and write, or use an appropriate full-access Project API key, then retry session creation.
30
31 ## Tool execution requires Tool execution write access
32
33 For a scoped Project API key, `composio.tools.execute()` and the tool-execute API require Tool execution set to Write or Read and write. A key without that permission can surface a generic 401 `Invalid API key` even when the key exists and is active.
34
35 Create a correctly scoped Project API key or use an appropriate full-access Project API key, then retry. A future API improvement may return a clearer permission error, but support should diagnose the current behavior from the key's permissions.