FruxonDocs
AgentsAlerts

Lists all available alert types with labels and descriptions.

Returns the static catalog of alert types an agent can fire — these are compiled into the server via `AlertTypeRegistry`, not tenant-scoped or persisted. Use the returned identifiers when classifying alerts on agent runs so the UI can map them to friendly labels and severities. The list is stable across requests; cache aggressively client-side.

GET
/v1/alertTypes

Authorization

Bearer
AuthorizationBearer <token>

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

In: header

Response Body

curl -X GET "https://api.fruxon.com/v1/alertTypes"
[
  {
    "type": "ERROR",
    "label": "string",
    "description": "string",
    "defaultChannels": [
      "EMAIL"
    ]
  }
]
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}
Empty

Lists unhandled-escalation events across the tenant, newest first.

Defaults to the last Fruxon.Model.HumanTasks.UnhandledEscalationReadService.DefaultLookback (these events are terminal and never drain, so an unbounded all-time list would stop being an attention signal); pass `sinceMs` to widen or narrow the window. Each item carries its `agentId`, `topicId`/`participantId` (for deep-linking into the conversation), and the failure reason. Read-only — the runtime already degraded the escalation gracefully.

Lists the delivery channels an alert type can be sent on, with availability.

Returns the static catalog of channels compiled into the server via `AlertChannelRegistry`. Pair this with the alert-type list to render a per-channel preference matrix; channels with `available = false` are registered but not yet deliverable and should be shown disabled. The list is stable across requests; cache client-side.