FruxonDocs
AgentsAlerts

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.

GET
/v1/alertTypes/channels

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/channels"
[
  {
    "channel": "EMAIL",
    "label": "string",
    "description": "string",
    "available": false
  }
]
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}
Empty

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.

Returns the read-only graph projection for Agent Network.

Composes existing Network primitives into nodes and typed edges for the future canvas. This endpoint does not mutate graph state; writes stay on participants, triggers, slot bindings, and channel materializers.