Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
| 1 | ## Proxy Execute requires an explicitly allowed Project API key |
| 2 | |
| 3 | Create a scoped Project API key in the Dashboard and enable **Proxy Execute** |
| 4 | during key creation before calling the v3.1 Proxy Execute API. If a request is |
| 5 | denied, verify the key's scope before debugging the provider connection. Use a |
| 6 | fresh request ID from the correctly scoped key when contacting Composio support is still necessary. |
| 7 | |
| 8 | ## Tool Router session creation requires Session management write access |
| 9 | |
| 10 | For scoped Project API keys, creating a session through `composio.sessions.create(...)` or `POST /api/v3.1/tool_router/session` requires the Session management permission with write or read/write access. |
| 11 | |
| 12 | 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`. |
| 13 | |
| 14 | Create a scoped Project API key with Session management set to Write only, then retry session creation. |
| 15 | |
| 16 | ## Tool execution requires Tool execution write access |
| 17 | |
| 18 | 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. |
| 19 | |
| 20 | Create a correctly scoped Project API key or use an appropriate full-access Project API key, then retry. The current API may return a generic permission error, so diagnose this behavior from the key's permissions. |
| 21 | |
| 22 | ## Session tool execution requires write access |
| 23 | |
| 24 | Set **Session tool execution** to Write to search and execute tools through a session or its MCP server, including session proxy requests. **Proxy execute (Legacy)** with Write access also grants the session proxy route. Either permission is sufficient for that route. The direct `/tools/execute/proxy` route requires **Proxy execute (Legacy)**. |