# Test Support Tool

POST /api/v2/projects/{projectId}/support/tools/test

Runs one server or MCP support tool with the supplied testValues and returns { ok, status, body }. Does not save the tool. endpoint, when present, must be an https URL on a public host. Auth is resolved from authSource and is not included in the result. testValues supplies model and context parameter values in place of a live visitor.

## Request

- projectId: string, path, required — ID of the project that owns the tool.
- testValues: object, required — Values for the model and context parameters, keyed by name, in place of a live visitor.
- authHeaderName: string — Header name for authType "apiKey", such as X-API-Key. The token is read from the integration, not from this field.
- authSource: object — Where the auth token is stored. { kind: "integration", integrationId } or { kind: "integration", serviceName }. Never send the token or the integration key.
  - kind: string, required
  - integrationId: string
  - serviceName: string
- authType: none | bearer | apiKey — How the proxied request authenticates. "none" sends no credential. "bearer" sends Authorization: Bearer from the integration. "apiKey" sends authHeaderName from the integration. The token is not stored on the tool.
- contentType: json | form — Body encoding for a server tool. "json" is the default. "form" sends application/x-www-form-urlencoded.
- contextParameters: string[] — Parameter names filled from the live visitor, not by the model. Use {name} in the endpoint, body, or a header.
- endpoint: string — https URL on a public host. Omit it for an endpointless catalog or MCP tool.
- method: GET | POST | PUT | PATCH | DELETE — HTTP method the tool calls. Omit it for an MCP tool, which has no URL.
- requestBody: string — JSON or form template. A parameter is sent in the body when its {name} placeholder appears here.
- requestHeaders: object[] — Extra headers. value may be a literal or a {param} template.
  - key: string, required
  - value: string, requi
…

## Response

- 200: Successful response
  - body: value, required
  - ok: boolean, required
  - status: number, required
- 400: Invalid input data
- 401: Authorization not provided
- 403: Insufficient access
- 500: Internal server error
