Tests a tool execution with the provided parameters.
Runs a tool in test mode to validate its configuration and inputs before using it in agent workflows.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The tenant identifier
The integration identifier
The tool test configuration and input parameters.
Represents the metadata for configuration of an integration.
A concrete, usable configuration of an integration — the connection parameters plus auth credentials a tool runs against. An agent revision references these by id from its tool steps.
Response Body
curl -X POST "https://api.fruxon.com/v1/tenants/string/integrations/string/tools:test" \ -H "Content-Type: application/json" \ -d '{}'{
"response": "string"
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Updates an existing Python script tool.
Replaces the Python-script tool definition at `(integration, tool)`; the script body and its input schema are validated together before the write commits, so a malformed script or schema returns 400 without modifying the stored definition. This is the script-tool counterpart to `PUT /integrations/{integration}/tools/{tool}` and must be used for tools whose execution is sandboxed Python rather than an HTTP call.
List webhooks, optionally filtered by provider.
Returns every webhook in the tenant, or just those for one provider when `provider` is supplied (e.g. `github`, `stripe`). Subscription details are not embedded — fetch them per webhook via `GET WebhookSubscriptions`.