FruxonDocs
IntegrationsCore

Gets the health of every application-level credential the agent's current published revision references that has a connected credential.

Resolves the configs the agent's deployed revision references, then reports each connected application-level credential's last observed health (from its most recent OAuth token refresh). `unhealthyCount` drives the agent-overview "credential needs attention" banner. User-level (per chat-user) credentials are not included — those are handled in-conversation. Returns an empty rollup when the agent has no deployed revision, references nothing, or has no connected credentials.

GET
/v1/tenants/{tenant}/agents/{agent}/credentialHealth

Authorization

Bearer
AuthorizationBearer <token>

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

In: header

Path Parameters

agent*string

The unique identifier of the agent.

tenant*string

The tenant identifier

Response Body

curl -X GET "https://api.fruxon.com/v1/tenants/string/agents/string/credentialHealth"
{
  "items": [
    {
      "configId": "00000000-0000-0000-0000-000000000000",
      "integrationId": "string",
      "displayName": "string",
      "health": "HEALTHY",
      "detail": "string",
      "since": 0
    }
  ],
  "unhealthyCount": 0
}
Empty
Empty
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}

Gets a specific revision of a configuration.

Returns the immutable snapshot of `Parameters`, `Auth`, and `AuthMap` captured when the revision was published, along with its version number and any publish note. The revision must belong to the supplied config; mismatched pairs return 404.

Lists integrations in the workspace, paginated.

Returns a page of configured integrations, each annotated with its tool count. Use the `search`, `types`, and `tags` query parameters to filter server-side, and `pageSize`/`pageToken` to page through results. The full tool collection for an integration is fetched separately via `/integrations/{integration}/tools`.