> ## Documentation Index
> Fetch the complete documentation index at: https://docs.squasher.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Incidents API

> List incidents, inspect timelines and evidence, change incident state, and manage service ownership.

Use the Incidents API for operational workflows around alerts, monitors, service ownership, and incident response.

Incident routing is project-scoped: the organization owns members, each project represents a service boundary, and service ownership maps operational services to owner teams inside that project.

Incident IDs returned by this API are project-scoped display IDs such as `inc_1`, `inc_2`, and `inc_3`. Use those values in `{incident_id}` paths. Existing UUID incident links remain accepted for compatibility.

## Incident operations

| Operation                             | Method and path                                                  | Purpose                                                                                                          |
| ------------------------------------- | ---------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
| `incidents.list`                      | `GET /v1/projects/{project_id}/incidents`                        | List incidents with status, severity, monitor, search, and pagination filters.                                   |
| `incidents.get`                       | `GET /v1/projects/{project_id}/incidents/{incident_id}`          | Get one incident with timeline events, evidence, recent checks, and service attribution.                         |
| `incidents.resolveServiceAttribution` | `POST /v1/projects/{project_id}/service-attribution/resolve`     | Resolve service ownership metadata from monitor, trace, alert, repository, runbook, or status component signals. |
| `incidents.ack`                       | `POST /v1/projects/{project_id}/incidents/{incident_id}/ack`     | Acknowledge an incident and append a timeline event.                                                             |
| `incidents.resolve`                   | `POST /v1/projects/{project_id}/incidents/{incident_id}/resolve` | Resolve an incident and append a timeline event.                                                                 |

## Service ownership operations

| Operation family           | Paths                                                             | Purpose                                                               |
| -------------------------- | ----------------------------------------------------------------- | --------------------------------------------------------------------- |
| Debt and import candidates | `/service-ownership/debt`, `/service-ownership/import-candidates` | Find ownership gaps and candidate services from current product data. |
| Teams                      | `/service-ownership/teams`                                        | List, create, update, or delete owner teams.                          |
| Services                   | `/service-ownership/services`                                     | List, create, update, link, or delete operational service records.    |
| Candidate apply            | `/service-ownership/import-candidates/{suggested_slug}/apply`     | Create or merge a service from a current import candidate.            |

State changes, deletions, and ownership writes are confirmation-required. Link replacement is a full replacement; pass every link set that should remain. Use owner teams for human routing and services for the technical component or app that triggered the incident.

## CLI and MCP

Use `squasher incidents ...` for terminal workflows. In MCP Code Mode, call `search("incidents")` and inspect the operation schema before executing. Hosted MCP may require approval for `ack`, `resolve`, delete, and write operations.

## Agent handoff

```text theme={null}
Investigate Squasher incident <incident_id> in project <project_id>. Fetch incident detail, recent checks, evidence, and service attribution. Use service ownership debt or import candidates only when ownership context is missing. Do not acknowledge, resolve, delete, or rewrite ownership links without explicit confirmation.
```

Related: [Status monitoring](/features/status-monitoring), [Alerts](/features/alerts).