Execute tool
Execute a tool. Connection is resolved implicitly from the caller’s account-user, the tool’s parent application, and optional toolsetId. Tool-runtime failures return 200 with isSuccess=false; all other failures use the standard error envelope.
Authorizations
Enter your JWT token
Path Parameters
The slug identifying the tool to execute.
Query Parameters
Optional toolset identifier used to scope connection resolution.
Optional explicit connection identifier to use instead of the implicitly resolved connection.
Body
The execution request containing the tool's input arguments.
Body shape for POST /api/DeveloperAPI/v1/tools/{toolSlug}/execute. activityName is intentionally absent — the activity is resolved from the path slug (+ optional ?applicationSlug=). Connection is resolved implicitly from the caller's account-user, the tool's parent application, and the optional ?toolsetId= query param. See applications-tools-spec.md §"POST /api/DeveloperAPI/v1/tools/{toolSlug}/execute".
Input field values for the tool, keyed by field name.
Optional context value passed to the tool.
Filter conditions to apply to the tool's results.
Sort clauses to apply to the tool's results.
Number of leading results to skip (pagination offset).
Maximum number of results to return.
Sub-item input values for the tool, keyed by name.
Per-call overrides for the resolved connection's fields; only fields marked overridable are accepted.
Response
The tool execution result, including success status and any output.
200 response shape for POST /api/DeveloperAPI/v1/tools/{toolSlug}/execute. Tool-runtime failures (downstream API errors) return 200 + IsSuccess=false
- ErrorMessage — not the standard error envelope. All non-200 responses use the standard ErrorResponse envelope, not this type. See applications-tools-spec.md §"Response 200".
Whether the tool executed successfully. When false, see ErrorMessage.
Human-readable failure reason when IsSuccess is false; otherwise null.
Metadata about the execution (HTTP status, headers, timing, payload size).
The tool's result payload. Intentionally free-form (any JSON): its shape is defined by the individual tool's output schema, not by this envelope (api-spec-feedback.md C3).
Identifier of the workflow-history record for this execution, when one was created.