NotificationRoutingRule
One rule = one match -> one destination (notification-channel-routing-telegram, v1.126). Every match dimension is optional; absent = wildcard, ANDed when present. No rules = no Telegram traffic; email/webhook are governed by preferences, untouched by this capability.
Properties
| Name | Type | Description |
|---|---|---|
| id | string | |
| recipient_email | string | |
| project_id | stringnull | Wildcard when null. |
| source | stringnull | Wildcard when null. |
| event_types | arraynull | Wildcard when null. An explicit [] matches NO event_type — a real, if unsatisfiable, filter — distinct from omitting the field. |
| classes | arraynull | Wildcard when null; same [] semantics as event_types. |
| min_severity | string | event-attention-rules: only events at or above this severity match. Never null: a rule created without one stores `notice` when it names no event_types (routine traffic stays in the feed) and `info` w |
| group_by | arraynull | event-attention-rules: 1 to 3 top-level payload keys (^[A-Za-z_][A-Za-z0-9_]{0,63}$) whose values group a window's events; needs window_seconds. A rule holds at most 200 distinct keys per window; furt |
| window_seconds | integernull | event-attention-rules: reduce a run of events to ONE message per closed wall-clock window (aligned to multiples of window_seconds), with one line per group key ordered by count, ten lines then a summa |
| next_window_closes_at | string | Windowed rules only: when the current window closes — the earliest a message can arrive. Computed at read. |
| escalation_level | integernull | event-attention-rules: set exactly for channel escalation — the ladder level a match raises at (the lowest staffed level at or above it). |
| escalation_refused_count | integer | Escalation rules: raises the bounds refused (20 per rule per UTC day; 20 open per organization). 0 otherwise. |
| last_escalation_refused_at | stringnull | |
| channel | string | event-attention-rules: `telegram` sends to telegram_binding_id; `escalation` raises on the organization's escalation ladder at escalation_level (mandatory delivery to the contacts there, one-tap ack, |
| telegram_binding_id | string | |
| enabled | boolean | |
| created_at | string | |
| updated_at | string |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://artifacts.apis.io/run402-com/json-schema/run402-com-notification-routing-rule-schema.json",
"title": "NotificationRoutingRule",
"description": "One rule = one match -> one destination (notification-channel-routing-telegram, v1.126). Every match dimension is optional; absent = wildcard, ANDed when present. No rules = no Telegram traffic; email/webhook are governed by preferences, untouched by this capability.",
"x-generated": "2026-11-10",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/run402-com-agent-api-openapi.yml#/components/schemas/NotificationRoutingRule",
"type": "object",
"properties": {
"id": {
"type": "string",
"format": "uuid"
},
"recipient_email": {
"type": "string"
},
"project_id": {
"type": [
"string",
"null"
],
"description": "Wildcard when null."
},
"source": {
"type": [
"string",
"null"
],
"enum": [
"app",
"platform",
null
],
"description": "Wildcard when null."
},
"event_types": {
"type": [
"array",
"null"
],
"items": {
"type": "string"
},
"description": "Wildcard when null. An explicit [] matches NO event_type — a real, if unsatisfiable, filter — distinct from omitting the field."
},
"classes": {
"type": [
"array",
"null"
],
"items": {
"type": "string"
},
"description": "Wildcard when null; same [] semantics as event_types."
},
"min_severity": {
"type": "string",
"enum": [
"info",
"notice",
"warn",
"critical"
],
"description": "event-attention-rules: only events at or above this severity match. Never null: a rule created without one stores `notice` when it names no event_types (routine traffic stays in the feed) and `info` when it names some (naming a type opts in to it). Rules that existed before severity shipped read `info` and deliver exactly what they did."
},
"group_by": {
"type": [
"array",
"null"
],
"items": {
"type": "string"
},
"description": "event-attention-rules: 1 to 3 top-level payload keys (^[A-Za-z_][A-Za-z0-9_]{0,63}$) whose values group a window's events; needs window_seconds. A rule holds at most 200 distinct keys per window; further keys are counted under (other), so varying a payload value multiplies neither messages nor stored state."
},
"window_seconds": {
"type": [
"integer",
"null"
],
"minimum": 60,
"maximum": 86400,
"description": "event-attention-rules: reduce a run of events to ONE message per closed wall-clock window (aligned to multiples of window_seconds), with one line per group key ordered by count, ten lines then a summary, plus the total and up to three bounded samples. 60 to 86400. Null delivers per event."
},
"next_window_closes_at": {
"type": "string",
"format": "date-time",
"description": "Windowed rules only: when the current window closes — the earliest a message can arrive. Computed at read."
},
"escalation_level": {
"type": [
"integer",
"null"
],
"minimum": 1,
"maximum": 10,
"description": "event-attention-rules: set exactly for channel escalation — the ladder level a match raises at (the lowest staffed level at or above it)."
},
"escalation_refused_count": {
"type": "integer",
"description": "Escalation rules: raises the bounds refused (20 per rule per UTC day; 20 open per organization). 0 otherwise."
},
"last_escalation_refused_at": {
"type": [
"string",
"null"
],
"format": "date-time"
},
"channel": {
"type": "string",
"enum": [
"telegram",
"escalation"
],
"description": "event-attention-rules: `telegram` sends to telegram_binding_id; `escalation` raises on the organization's escalation ladder at escalation_level (mandatory delivery to the contacts there, one-tap ack, deadman climb), and one open escalation per rule: a repeat attaches. Was generic on purpose (widening to email/webhook rules later is a CHECK-constraint migration, not a reshape); v1 only ever writes 'telegram'."
},
"telegram_binding_id": {
"type": "string",
"format": "uuid"
},
"enabled": {
"type": "boolean"
},
"created_at": {
"type": "string",
"format": "date-time"
},
"updated_at": {
"type": "string",
"format": "date-time"
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/json-schemas/run402-com-notification-routing-rule"
curl "https://apis.io/api/v1/json-schemas?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.