---
title: "Execute a tool within a tool router session"
method: POST
path: "/api/v3/tool_router/session/{session_id}/execute"
tags: ["Tool Router"]
---

# Execute a tool within a tool router session

`POST /api/v3/tool_router/session/{session_id}/execute`

Executes a specific tool within a tool router session. This is the primary execution endpoint for both meta tools and app tools exposed by the session. The toolkit is automatically inferred from the tool slug. For app tools, the tool must belong to an allowed toolkit and must not be disabled in the session configuration. The endpoint validates permissions, resolves connected accounts when needed, and executes the tool with the session context. The top-level account field applies only to direct app tool execution in multi-account sessions. Meta/helper tools either ignore it or define their own account-selection fields, for example COMPOSIO_MULTI_EXECUTE_TOOL.tools[].account.

## Path parameters

- `session_id` string, toolRouterSessionId — The unique identifier of the tool router session. Required for public API endpoints, optional for internal endpoints where it is injected by middleware.

## Request body

- object
  - `tool_slug` string, required — The unique slug identifier of the tool to execute. Supports both meta tools and app tools exposed by the session.
  - `arguments` object — The arguments required by the tool
  - `account` string — Account identifier to specify which connected account to use for direct tool execution. Use the account ID (e.g. "coup_hurricane_dal_analytical") or an alias. When omitted with a single account, the default is used. When omitted with multiple accounts, an error lists available accounts. Meta/helper tools either ignore this top-level field or define their own account-selection fields, for example COMPOSIO_MULTI_EXECUTE_TOOL.tools[].account.
  - `enable_auto_workbench_offload` boolean — When true, direct non-meta tool execution may return a workbench offload preview if the response exceeds the configured threshold and the session workbench is enabled. When omitted or false, direct tool execution returns the normal inline response. Meta/helper tools are unaffected, and COMPOSIO_MULTI_EXECUTE_TOOL uses session.workbench configuration for its own batch-level offload behavior.

## Response `200`

Successfully executed the tool. Returns execution result, logs, and status.

- object
  - `data` object, required — The data returned by the tool execution
  - `error` string, nullable, required — Error message if the execution failed, null otherwise
  - `log_id` string, required — Unique identifier for the execution log

## Other responses

- `400` — Bad request
- `401` — Unauthorized
- `403` — Forbidden
- `404` — Not found
- `413` — Payload too large
- `429` — Too many requests
- `500` — Internal server error
- `502` — Bad gateway

---

[API](https://skmtc.dev/composiohq/apis/composio-platform-api.md) · [All operations](https://skmtc.dev/composiohq/apis/composio-platform-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/composiohq/composio-platform-api/revisions/368fb7851f42/schema)