inc_1, inc_2, and inc_3. Use those values in {incident_id} paths. Existing UUID incident links remain accepted for compatibility.
When a monitor incident opens within 60 minutes of a completed deployment, incident responses include suspectDeployment with the deployment id, service, version, deployedAt, and gapSeconds. The field is null when no recent deployment is available.
Incident operations
Service ownership operations
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
Usesquasher 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
Set a public post-incident review link
PATCH /v1/projects/{project_id}/incidents/{incident_id}/postmortem sets the public review link for a resolved, published incident. It requires status_pages:write.
null to remove the link, including after the linked status page is deleted. The response is { "postmortemUrl": "..." } or { "postmortemUrl": null }. The URL must use HTTP or HTTPS, have no embedded credentials, and contain at most 2,048 characters. An unpublished or unresolved incident returns 409. An incident outside the project returns 404.
client.incidents.updatePostmortem(incidentId, urlOrNull). MCP exposes incidents.updatePostmortem through Code Mode.