Update incidents via the API

Weekly Update

We've added a new endpoint to our public API that enables you to update incidents. You can use this to update the incident's name or summary, or set a custom field.

This might be useful to add extra context to an incident summary, or keep a custom field up-to-date based on some information in another system.

You can use the notify_incident_channel parameter to decide whether or not responders in the incident channel should be notified of the change. We'll ignore any fields that you don't provide, so you can choose to update just the summary, or just the severity, without worrying about the rest of the payload.

You can get started with our API by reading our API documentation. We'd also love to hear what you're building in the #api channel in our Slack community!

To try this out for yourself:

# Update the incident summary
curl -i -X POST \
  'https://api.incident.io/v2/incidents/${INCIDENT_ID}/actions/edit' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer ${TOKEN}' \
  -d '{
    "incident": {
      "summary": "Look at me: I've updated the summary of the incident from the API."
    },
    "notify_incident_channel": true
  }'

๐Ÿ’… See who's currently on-call

When you escalate via PagerDuty, weโ€™ll now show you who youโ€™re about to page. That helps confirm that you've chosen the correct service, and also makes sure you aren't about to inadvertendly page yourself (which I have definitely not done before).

๐Ÿš€ What else we shipped

  • ๐Ÿ†• You can now add labels when exporting follow-ups to Linear. You can also set default labels in your Linear Settings if you want to always have the same label (e.g. incident-follow-up) appear by default when exporting.
  • ๐Ÿ’… We've made some improvements to the announcement rules settings pages.
  • ๐Ÿ’… We'll return a more useful error if we can't resolve a Confluence post-mortem destination from the provided URL.
  • ๐Ÿ’… You can now convert an action to a follow-up when editing the action in Slack.
  • ๐Ÿ’… We now show timestamps on incident updates in the web dashboard in local and UTC (on hover).
  • ๐ŸŽ Made some performance improvements to the app as a whole.
  • ๐Ÿ› We fixed a bug where post-mortems with very long text blocks couldn't be exported to Notion.
  • ๐Ÿ› We fixed a bug where we'd let you try to update a resolved Atlassian statuspage (which will always fail).
  • ๐Ÿ› We fixed a bug where we weren't handling different date-time formats when exporting to Jira.
  • ๐Ÿ› We fixed a bug where we weren't notifying some organizations when they had a broken webhook endpoint.