Retrieve a resolved incident with full detail: GET https://api.incident.io/v2/incidents/{id} including the timeline, role assignments, and custom fields
Fetch incident updates: GET https://api.incident.io/v2/incident_updates?incident_id={id} to reconstruct the chronological timeline of status changes and communications
Fetch action items: GET https://api.incident.io/v2/incident_action_items?incident_id={id} to capture follow-up tasks generated during the incident
Assemble a structured postmortem document from the fetched data, populating sections for timeline, impact, root cause, contributing factors, and action items
Create a follow-up task in your project management tool (e.g., POST to Jira or Linear API) for each action item, referencing the incident ID for traceability
Optionally trigger a postmortem workflow via PATCH to mark the incident as in_post_incident_review status and assign the postmortem owner using role assignments
Known gotchas
incident.io's Scribe AI feature auto-generates postmortem drafts from Slack timelines and call transcripts; the API reflects the draft content only after Scribe has run — poll for completion before fetching
Custom fields defined by the organization are returned in the custom_field_entries array and must be fetched from GET /v2/custom_fields to map IDs to human-readable labels
Action items created outside of incident.io (e.g., in Jira directly) are not automatically synced back; use bidirectional webhooks or nightly reconciliation to keep action item status consistent
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp