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.
Authorization
Bearer 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
}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.
Lists the messaging entry points claimed across the caller's Applications, as claim rows.
One row per claimed external channel address, enriched with the owning Application's name and the backing doorway's (agent, integration config) coordinates. The connect wizard uses this to grey claimed addresses ("in use by ⟨app⟩ — move…"); the Integrations page uses it to render read-only "Used by ⟨app⟩" chips. Read-only: claims change only through connect / move / detach on the per-Network surface. Scoped to the Applications the caller can open, because each row names its owning Application. An address claimed by an Application they cannot reach is therefore absent rather than greyed — the connect attempt still fails on the claim itself, which is where the conflict belongs.