Skip to main content
POST
Test an HTTP tool
Testing sends a real request to the configured destination and can change data in that service.
Requires Editor, Admin, or Owner, plus Admin or Owner for tools with stored credentials, headers, or preset values. Only HTTP API tools support this operation; other types return 400. Supply arguments matching the tool parameters. Inspect the response success/error fields: an HTTP 200 response does not by itself mean the downstream request succeeded.

Authorizations

Authorization
string
header
required

Bandwidth Labs OAuth access token. Uses the user's selected workspace; the workspace header is not required. Do not also send an API key. Bearer-only operations may additionally require the Labs super_user role.

Headers

X-VOAI-ORGANIZATION-ID
string | null

Required with X-BW-LABS-AGENTS-API-KEY: the positive local workspace ID to access. The key owner must be a current member. Missing or invalid IDs return 400; non-member workspaces return 403. Not required for bearer authentication, which uses the user's selected workspace.

Path Parameters

tool_uuid
string
required

Body

application/json
arguments
Arguments · object

Response

Successful Response

latency_ms
number
required
status
string
required
error
string | null
status_code
integer | null