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

Better Stack Incidents API

The Incidents API from Better Stack — 7 operation(s) for incidents.

Better Stack Incidents API is one of 4 APIs that Better Stack publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Incidents. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 9 operations across 7 paths, and defines 1 schema. It is described by OpenAPI 3.1.0, at version 2.0.0.

Requests are made against 2 base URLs: https://uptime.betterstack.com/api/v2, https://uptime.betterstack.com/api/v3.

9 operations 7 paths 1 schemas 1 DELETE3 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
2.0.0
Base URL
https://uptime.betterstack.com/api/v2
Authentication
HTTP Bearer
License
Proprietary
Resource Areas
1

Authentication & Security 1

Better Stack Incidents API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Bearer token. Provide either a Global API Token (account-wide) or a team-scoped Uptime API Token. Issued from Better Stack → API tokens.

Paths & Operations 9

Across 7 paths, the API surfaces 9 operations — 1 DELETE, 3 GET, 5 POST. Each is listed below with its method, path, parameters, and response codes.

Incidents 9
GET
/incidents
List incidents
listIncidents 2 params → 200
POST
/incidents
Create incident
createIncident body → 201
GET
/incidents/{id}
Get incident
getIncident 1 param → 200
DELETE
/incidents/{id}
Remove incident
deleteIncident 1 param → 204
GET
/incidents/{id}/timeline
List incident timeline
getIncidentTimeline 1 param → 200
POST
/incidents/{id}/acknowledge
Acknowledge incident
acknowledgeIncident 1 param → 200
POST
/incidents/{id}/resolve
Resolve incident
resolveIncident 1 param → 200
POST
/incidents/{id}/reopen
Reopen incident
reopenIncident 1 param → 200
POST
/incidents/{id}/escalate
Escalate incident
escalateIncident 1 param → 200

Schemas 1

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

IncidentCreate
object
9 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

betterstack-incidents-api-openapi.yml Raw ↑

Other APIs Better Stack publishes across the network.

Better Stack Heartbeats API
Better Stack Monitors API
Better Stack Status Pages API
Where this information came from

This is an independent, third-party profile of Better Stack Incidents 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.