How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Incident.io Follow-ups API

The Follow-ups API from Incident.io — 2 operation(s) for follow-ups.

Incident.io Follow-ups API is one of 25 APIs that Incident.io publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Follow-ups. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 2 operations across 2 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against a single base URL, https://api.incident.io/v2.

2 operations 2 paths 2 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Server
https://api.incident.io/v2
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Incident.io Follow-ups API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (API Key) (bearerAuth). By default, every request must be authenticated.

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 GET. Each is listed below with its method, path, parameters, and response codes.

Follow-ups 2
GET
/follow-ups
listFollowUps → 200
GET
/follow-ups/{id}
getFollowUp 1 param → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed is ListResponse (2 properties). Each schema is shown below with its type and property counts.

Resource
object
ListResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

incident-io-follow-ups-api-openapi.yml Raw ↑

Other APIs Incident.io publishes across the network.

Incident.io Actions API
Incident.io Alert Attributes API
Incident.io Alert Routes API
Incident.io Alert Sources API
Incident.io Alerts API
Incident.io API Keys API
Incident.io Catalog Entries API
Incident.io Catalog Types API
Incident.io Custom Fields API
Incident.io Escalation Paths API
Incident.io Escalations API
Incident.io Incident Roles API
Where this information came from

This is an independent, third-party profile of Incident.io Follow-ups API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.