okokumo Sentinel API (1)

Owners/admins only. Only the display prefix is returned, never the raw key.

Owners/admins only. The raw key is returned once, at creation — store it somewhere safe; only key_prefix is retrievable afterwards.

interval_seconds is floored by your plan (free 300s, starter 60s, pro 30s). For type: heartbeat or cron, omit url/method/assertions and send grace_seconds instead — the response includes a ping_token. A cron check may carry cron_expression (+ cron_timezone) to be judged against a crontab schedule rather than a flat period.

Replaces the whole check — it does not patch. Omitted fields are not kept from the existing row. type is immutable after creation.

Resolves a crontab expression to its next runs without writing anything, so a schedule can be checked before it is relied on. Uses the same parser as the silence detector, so the preview and the deadline that actually pages you cannot disagree.

Last 50 state changes, newest first.

The last 20 delivery attempts, newest first. A state change and a delivered notification are different things; this reports the second. A skipped row with no channel means nobody was told, and detail says why — no channels, none confirmed, routing that excludes them, or a maintenance window. Records begin when the endpoint shipped.

No rows = every org channel fires (default). Assigned rows = only those channels fire.

For type: webhook, a signing secret is auto-generated if config.secret is omitted — always send the existing secret back unchanged on update, or a new one is minted and downstream signature verification silently breaks.

Read-only with an API key; changing the page's configuration (slug, components, custom domain, publishing the page) is session-only, so a leaked key can't repoint your public address. components[].id is what component_ids on an incident refers to. 404 until the page exists.

Every incident on the page, drafts included — this is the authoring view, not the public one. Newest first.

Owner/admin, Pro plan or above. Starts as a private draft — send published: true (here or on a later PUT) to show it to visitors. body, when present, becomes the first timeline entry.

Replaces the incident itself — title, severity, affected components, whether it's published. Timeline entries are posted separately and are never rewritten from here. published and archived are applied only when present, so an edit that omits them can't silently unpublish a live incident. archived: true also resolves it.

Removes the incident and its timeline. To close one while keeping the story on the page, archive it instead.

Append-only. status is optional — an update that doesn't move the incident along is still worth posting; when present it moves the incident, and resolved stamps resolved_at. Posting to an archived incident un-archives it.