Skip to main content
Tools are the individual executable actions inside a toolkit, like GMAIL_SEND_EMAIL or GITHUB_CREATE_ISSUE. Each tool has an input schema describing its parameters and an output schema describing what it returns. Tool slugs are SCREAMING_SNAKE_CASE and follow a {TOOLKIT}_{ACTION} pattern. Reach for these endpoints when you want to:
  • List or search the catalog of available tools, optionally scoped to one or more toolkits.
  • Fetch a single tool’s input and output schema by tool_slug before constructing a call.
  • Execute a tool on behalf of a user’s connected account, or generate the inputs for an execution from natural language.
  • Look up the OAuth scopes a set of tools requires, or send an authenticated proxy request to an app’s underlying API.
These endpoints authenticate with your project API key in the x-api-key header.
Manual tool execution requires an explicit toolkit version. Pass toolkit_versions=latest (or pin a dated version like 20251027_00) so calls resolve to a known tool definition. See the toolkit versioning migration guide.
For the concepts behind tools, schemas, and authentication, see Tools and toolkits.

Proxy execute

Proxy execute sends an authenticated HTTP request through a toolkit’s connected account without a predefined tool, and Composio injects the OAuth token, API key, or other credentials on the server side so your code never touches raw secrets. Reach for it when you need an endpoint that Composio’s predefined tools do not cover, when you need a request shape (custom query parameters, field masks, or advanced filters) that a predefined tool cannot express, or when a terminal agent would otherwise hardcode a bearer token in a curl call. Call it with composio.tools.proxyExecute() in the TypeScript SDK, composio.tools.proxy() in the Python SDK, or POST /api/v3.1/tools/execute/proxy over HTTP. The endpoint can be an absolute URL (https://api.example.com/v1/resource) or a path relative to the toolkit’s base URL (/v1/resource), method is the HTTP verb, connectedAccountId selects the account to authenticate as, body carries the JSON payload, and parameters adds extra headers and query parameters. The response forwards the upstream status, headers, and parsed data verbatim.
Proxy execute rejects cross-domain requests, so the endpoint must resolve to the same domain as the connected account’s toolkit, and you should not set the Authorization header yourself because Composio injects the correct credential for the account’s auth scheme. This is an intentional security boundary, not a quota, so it cannot be bypassed by reshaping the request.
Proxy execute is a form of direct tool execution: it bypasses session state, tool schemas, and modifiers. If you are building an agent, prefer sessions, and use the proxy only for the specific API call that is not available as a tool. The full request and response schema lives in the POST /api/v3.1/tools/execute/proxy reference.

List available tools

Retrieve a paginated list of available tools with comprehensive filtering, sorting and search capabilities. Use query parameters to narrow down results by toolkit, tags, or search terms.

Get tool by slug

Retrieve detailed information about a specific tool using its slug identifier. This endpoint returns full metadata about a tool including input/output parameters, versions, and toolkit information.

Get tool enum list

Retrieve a list of all available tool enumeration values (tool slugs) from latest version of each toolkit. This endpoint returns a comma-separated string of tool slugs that can be used in other API calls.

Execute tool

Execute a specific tool operation with provided arguments and authentication. This is the primary endpoint for integrating with third-party services and executing tools. You can provide structured arguments or use natural language processing by providing a text description of what you want to accomplish.

Generate tool inputs from natural language (DEPRECATED)

DEPRECATED: This endpoint is no longer maintained. It still works for existing integrations but may be removed in a future release. To build tool arguments, fetch the tool's input schema with `GET /api/v3/tools/{tool_slug}` and generate the arguments in your own application. Uses AI to translate a natural language description into structured arguments for a specific tool.

Execute proxy request

Proxy an HTTP request to a third-party API using connected account credentials. This endpoint allows making authenticated API calls to external services while abstracting away authentication details.