Okapi Okapi

incident.io API Follow-ups V2 API removal

Stops workingin 55 daysSubscribe to incident.io APIShare

On December 31, 2026, the Follow-ups V2 API will be removed. Requests sent to /v2/follow_ups* endpoints will fail after this date. This change affects all calls targeting the /v2/follow_ups* path.


Calls it hits

  • /v2/follow_ups*

What to use instead of these calls

Use the Follow-ups V3 endpoints: GET/POST /v3/follow_ups, GET/PUT/DELETE /v3/follow_ups/{id} and POST /v3/follow_ups/{id}/actions/connect_external_issue.

In incident.io API's words

follow-up payload, and will be removed on 31 December 2026.

incident.io API, Announcement

Facts

API
incident.io API api.incident.io
Kind
Removal
Takes effect
December 31, 2026
Calls after that day
Fail
Source
Announcement
Last updated
Verified
, against incident.io API's own pages

Questions

When does this change take effect?

Calls to /v2/follow_ups* on incident.io API stop working on December 31, 2026.

What happens to calls after December 31, 2026?

They fail from that day.

How do I find the calls this hits in my code?

Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.


More from incident.io API 1

  1. /v2/actions*Removal Stops workingin 55 days

Is your code calling this?

Okapi finds the calls this change hits in your repo and opens the pull request with the fix before December 31, 2026.

Add to GitHub

Get notifications

Subscribe to incident.io API

Hear about each breaking change incident.io API announces, in your feed reader, calendar or Slack.

1What to follow

Provider
  • incident.io API

2Where to get it

/breaking-changes/feed.xml

Paste it into Feedly, Inoreader, NetNewsWire or any reader. New changes show up as they're announced.