# Incident.io

Incident response on incident.io — read incident state end-to-end (incidents, updates, actions, follow-ups), discover the org's severities, incident types, statuses, custom fields, and roles, see who is on call (schedules, schedule entries, escalation paths), raise incidents, and page people through escalations.

Run these through `omni-cli` once a human has connected the platform (`omni-cli incidentio login`). Full parameter and output schemas come from `omni-cli discovery incidentio`.

## actions

| Command | What it does | Kind |
|---|---|---|
| `omni-cli incidentio action get` | Get one action by ID. | read |
| `omni-cli incidentio action list` | List actions (tasks raised during incident response), optionally filtered to one incident. | read |

## discovery

| Command | What it does | Kind |
|---|---|---|
| `omni-cli incidentio custom-field list` | List the org's custom fields (discovers the custom_field_id each incident.create custom-field-entries entry needs). | read |
| `omni-cli incidentio incident-role list` | List the org's incident roles (lead, reporter, and custom roles people are assigned to during incidents). | read |
| `omni-cli incidentio incident-status list` | List the org's incident statuses (discovers the status IDs the incident.list status filter takes). | read |
| `omni-cli incidentio incident-type list` | List the org's incident types (discovers the incident-type IDs incident.create and the incident.list incident-type filter take). | read |
| `omni-cli incidentio severity list` | List the org's severities (discovers the severity IDs incident.create and the incident.list severity filters take). | read |

## on call

| Command | What it does | Kind |
|---|---|---|
| `omni-cli incidentio escalation-path list` | List escalation paths (discovers the escalation-path-id escalation.create can follow, with who each path would page right now). | read |
| `omni-cli incidentio escalation create` | Page people — escalate to an escalation path OR directly to specific users. Reusing an idempotency key returns the existing escalation instead of paging again. Rate-limited to 60 requests/minute (the global default is 1200/minute per key). | write |
| `omni-cli incidentio schedule-entry list` | List a schedule's entries in a time window — who is (or will be) on call; the final list is the effective on-call after overrides. | read |
| `omni-cli incidentio schedule get` | Get one on-call schedule by ID, including its full rotation/layer config. | read |
| `omni-cli incidentio schedule list` | List on-call schedules (discovers the schedule-id schedule.get and schedule-entry.list need, with who is on shift right now). | read |

## follow ups

| Command | What it does | Kind |
|---|---|---|
| `omni-cli incidentio follow-up get` | Get one follow-up by ID. | read |
| `omni-cli incidentio follow-up list` | List follow-ups (post-incident work items, often linked to external tickets), optionally filtered to one incident or team. | read |

## incidents

| Command | What it does | Kind |
|---|---|---|
| `omni-cli incidentio incident-update list` | List incident status updates — the timeline of status/severity changes and update messages, newest first. | read |
| `omni-cli incidentio incident create` | Create (declare) an incident. Requires an idempotency key — retries with the same key return the existing incident instead of creating a duplicate. | write |
| `omni-cli incidentio incident get` | Get one incident by ID, including role assignments, custom-field entries, timestamps, and the postmortem link. | read |
| `omni-cli incidentio incident list` | List incidents with status, severity, type, mode, and time-window filters. By default upstream returns only standard and retrospective incidents — pass mode to include test or tutorial ones. | read |