FruxonDocs
IntegrationsConfigs

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.

GET
/v1/tenants/{tenant}/integrations/{integration}/configs/{config}/usage

Authorization

Bearer
AuthorizationBearer <token>

JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.

In: header

Path Parameters

config*string

The configuration ID.

Formatuuid
tenant*string

The tenant identifier

integration*string

The integration identifier

Response Body

curl -X GET "https://api.fruxon.com/v1/tenants/string/integrations/string/configs/497f6eca-6276-4993-bfeb-53cbbbba6f08/usage"
[
  {
    "agentId": "string",
    "agentDisplayName": "string",
    "revision": 0
  }
]
Empty
Empty
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}

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.

Verifies the auth credentials stored in the configuration.

For non-OAuth auth types (API key, bearer token, basic auth), tests whether the stored credentials can successfully connect to the integration. For OAuth2, returns an `authorizationUrl` the frontend should redirect the user to in order to complete the OAuth flow. When the config uses an AuthMap (per-request auth), each entry is verified independently and the results are returned in `authMapResults`. Use the optional `authMapIndex` query parameter to verify a single entry. Returns 400 if the config has neither Auth nor AuthMap configured.