Tests a tool using the published config credentials.
Resolves the tool by ID within the integration and executes it using the credentials from the currently published revision. Returns 400 if the config has no published revision.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The integration ID.
The configuration ID.
uuidThe tenant identifier
The tool ID and input parameters.
Tool ID within the integration (e.g. "list_channels").
Tool input parameters as key-value pairs.
Response Body
curl -X POST "https://api.fruxon.com/v1/tenants/string/integrations/string/configs/497f6eca-6276-4993-bfeb-53cbbbba6f08:testTool" \ -H "Content-Type: application/json" \ -d '{ "toolId": "string" }'{
"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
}Rolls back the configuration to a previously published revision.
Repoints `PublishedRevisionId` at the target revision without creating a new revision or version number; the draft on the config record is not modified. The target must already exist in this config's history — use `/integrations/{integration}/configs/{config}/revisions` to list valid IDs first.
Lists agents that reference this configuration.
Returns every agent whose current revision has an integration config entry pointing to this tenant config via `TenantConfigId`. Use this before deleting or rolling back a config to understand the impact.