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

Checkly Status Page Incidents API

The Status Page Incidents API from Checkly — 10 operation(s) for status page incidents.

Checkly Status Page Incidents API is one of 42 APIs that Checkly publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Status Page Incidents. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 10 operations across 4 paths, and defines 25 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://api.checklyhq.com.

10 operations 4 paths 25 schemas 2 DELETE4 GET2 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.checklyhq.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Checkly Status Page Incidents API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (Bearer) (Bearer). By default, every request must be authenticated.

  • Bearer — The Checkly Public API uses API keys to authenticate requests. You can get the API Key here . Your API key is like a password: keep it secure! Authentication t…

Paths & Operations 10

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

Status Page Incidents 10
GET
/v1/status-pages/incidentsdeprecated
Retrieve the latest incidents with pagination.
getV1StatuspagesIncidents 3 params → 200401403404429
POST
/v1/status-pages/incidentsdeprecated
Create a new incident.
postV1StatuspagesIncidents 1 param body → 201401403404429
DELETE
/v1/status-pages/incidents/{incidentId}deprecated
Delete an incident.
deleteV1StatuspagesIncidentsIncidentid 2 params → 204401403404429
GET
/v1/status-pages/incidents/{incidentId}deprecated
Retrieve an incident by id.
getV1StatuspagesIncidentsIncidentid 2 params → 200401403404429
PUT
/v1/status-pages/incidents/{incidentId}deprecated
Update an existing incident.
putV1StatuspagesIncidentsIncidentid 2 params body → 200401403404429
GET
/v1/status-pages/incidents/{incidentId}/incident-updatesdeprecated
Retrieve the 100 latest incident updates of a specific incident.
getV1StatuspagesIncidentsIncidentidIncidentupdates 2 params → 200401403404429
POST
/v1/status-pages/incidents/{incidentId}/incident-updatesdeprecated
Add a new incident update to a specific incident.
postV1StatuspagesIncidentsIncidentidIncidentupdates 2 params body → 200401403404429
DELETE
/v1/status-pages/incidents/{incidentId}/incident-updates/{incidentUpdateId}deprecated
Delete an incident update.
deleteV1StatuspagesIncidentsIncidentidIncidentupdatesIncidentupdateid 3 params → 204401403404429
GET
/v1/status-pages/incidents/{incidentId}/incident-updates/{incidentUpdateId}deprecated
Retrieve an incident update by id.
getV1StatuspagesIncidentsIncidentidIncidentupdatesIncidentupdateid 3 params → 200401403404429
PUT
/v1/status-pages/incidents/{incidentId}/incident-updates/{incidentUpdateId}deprecated
Update an existing incident update.
putV1StatuspagesIncidentsIncidentidIncidentupdatesIncidentupdateid 3 params body → 200401403404429

Schemas 25

The contract defines 25 schemas that model the data the API accepts and returns. The most detailed are CreateStatusPageV2Incident (9 properties), StatusPageV2Incident (9 properties), StatusPageV2IncidentCommon (8 properties), StatusPageV2IncidentUpdate (6 properties). Each schema is shown below with its type and property counts.

attributes
object
StatusPageV2IncidentUpdate
object
6 properties 1 required
IncidentUpdates
array
Model2
string
UnauthorizedError
object
4 properties 2 required
Model76
array
TooManyRequestsError
object
4 properties 2 required
StatusPageV2IncidentCommon
object
8 properties 3 required
StatusPageV2Incident
object
9 properties 7 required
IncidentsPaginatedResponse
object
3 properties 2 required
IncidentsPaginatedEntries
array
ForbiddenError
object
3 properties 2 required
StatusPageV2IncidentUpdateWithId
object
6 properties 3 required
CreateIncidentUpdates
array
StatusPageV2Service
object
5 properties 4 required
NotFoundError
object
3 properties 2 required
error
string
IncidentSeverity
string
Model4
string
IncidentService
object
5 properties 3 required
Model1
string
IncidentCommonServices
array
IncidentServices
array
StatusPageIncidentStatus
string
CreateStatusPageV2Incident
object
9 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

checkly-status-page-incidents-api-openapi.yml Raw ↑

Other APIs Checkly publishes across the network.

Checkly Accounts API
Checkly Alert Channels API
Checkly Analytics API
Checkly Check Alerts API
Checkly Check Groups API
Checkly Check Results API
Checkly Checks API
Checkly Dashboards API
Checkly Heartbeats API
Checkly Incidents API
Checkly Maintenance Windows API
Where this information came from

This is an independent, third-party profile of Checkly Status Page 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.