Skip to main content
A scoped project API key lets you choose which project resources the key can access. Reach for one when a key needs only a subset of your project, such as executing tools, reading logs, or managing connected accounts.
You pick a key’s permissions when you create it, and they can’t be changed afterward. To adjust them, create a new key and rotate your application to use it.
Default project API keys keep full project API key access. Scoped keys use the permission areas and access levels on this page.

Create a scoped API key

Create a scoped key from the dashboard:
1
2
Select Platform.
3
Select your project.
4
Go to Settings.
5
Open the API Keys tab.
6
Click Create API Key, then choose the permission areas and access levels below.

Access levels

Some read routes use POST because the request body carries filters or lookup input. The access level is based on what the route does, not only the HTTP method. The REST tables show paths relative to the API base URL, with each operation listed once. Use the API reference for the full request URL and endpoint availability. MCP transports use the URL returned when you create a session or MCP server.

Permission areas

Jump to each permission area to see the routes it covers.

Auth configs

View and modify auth configs.

Connected accounts

View and manage connected accounts.

Tools

View tool definitions, inputs, scopes, and versions.

Session management

Create, view, configure, and delete sessions. This permission does not allow tool execution. The Session config read routes below are experimental and require Session configs to be enabled for your project.

Session tool execution

Search and execute tools through sessions and session-linked MCP servers. Session proxy execution is not included; grant Proxy execute for that. For session-linked MCP access, use session.mcp.url and session.mcp.headers unchanged. POST requests require Session tool execution with Write only access. The transport does not support GET (SSE) or DELETE; granting additional permissions does not enable those methods.

Toolkits

View toolkits.

Triggers

View trigger types, manage trigger instances, and subscribe to trigger events. The realtime routes are called by the SDK (triggers.subscribe()) and the CLI to receive trigger events.

Webhooks

View and manage webhook endpoints and subscriptions.

Observability

View execution logs and project usage summaries.

MCP (Legacy)

Create, manage, and connect to MCP servers. Transport access grants every capability exposed by the configured MCP server. For MCP transport access, use the returned MCP server URL unchanged. POST and DELETE requests require MCP (Legacy) with Write only or Read and write access.

Tool execution (Legacy)

Execute predefined Composio tools.

Proxy execute (Legacy)

Execute raw proxy requests against connected accounts. Proxy execute is separate from tool execution and from Session tool execution. It is the only permission that grants the session proxy route below, whether the call comes from session.proxyExecute() or from code running in that session’s sandbox. Grant it only when your application needs to call a connected account API through the raw proxy path.

Authenticating to Composio

Projects

Proxy execute

Observability