Lists the delivery channels an alert type can be sent on, with availability.
Catalog of alert delivery channels. Pair it with the alert-type catalog for preferences. available=false means the channel cannot currently deliver. Stable across requests; clients may cache it.
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.
Catalog of alert types available to agents, with identifiers, labels and severities. Shared across workspaces and stable across requests; clients may cache it.
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 / disconnect 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.