Checkly Status Pages V3 Incidents API

The Status Pages V3 Incidents API from Checkly — 11 operation(s) for status pages v3 incidents.

Operations 11

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /v3/status-pages/{statusPageId}/incidents List incidents on a status page · List the incidents of a v3 status page #
Ask an LLM
“Which incidents are on my status page, most recently updated first?”
“Can I page through a status page's incident history?”
Tell an agent
List incidents on status page {statusPageId}.
Show the next {limit} incidents on status page {statusPageId} after {nextId}.
POST /v3/status-pages/{statusPageId}/incidents Open an incident on a status page · Open an incident on a v3 status page #
Ask an LLM
“How do I declare an outage on my status page?”
“Can a new incident mark specific components as impacted right away?”
Tell an agent
Open incident {name} on status page {statusPageId} with first update {incidentUpdates}.
Declare incident {name} on status page {statusPageId} impacting {componentImpacts}, starting with {incidentUpdates}.
DELETE /v3/status-pages/{statusPageId}/incidents/{incidentId} Delete an incident from a status page · Delete an incident of a v3 status page #
Ask an LLM
“How do I remove an incident posted by mistake from my status page?”
“Does deleting an incident also delete all of its updates?”
Tell an agent destructive · confirm first
Delete incident {incidentId} from status page {statusPageId}.
Permanently remove incident {incidentId} and its updates from page {statusPageId}.
GET /v3/status-pages/{statusPageId}/incidents/{incidentId} Get an incident on a status page · Retrieve an incident of a v3 status page #
Ask an LLM
“What updates and component impacts does a specific incident have?”
“Can I see the full detail of one incident on my status page?”
Tell an agent
Show incident {incidentId} on status page {statusPageId}.
Get the details and impacts of incident {incidentId} from status page {statusPageId}.
PUT /v3/status-pages/{statusPageId}/incidents/{incidentId} Rename an incident or set component status · Update an incident of a v3 status page #
Ask an LLM
“Can I rename an incident that's already open on my status page?”
“How can I change which components an open incident currently affects?”
Tell an agent
Rename incident {incidentId} on status page {statusPageId} to {name}.
Set incident {incidentId} on page {statusPageId} to name {name} with current impacts {componentImpacts}.
PUT /v3/status-pages/{statusPageId}/incidents/{incidentId}/component-impacts Rewrite an incident's component impact timeline · Replace an incident's component impact timeline #
Ask an LLM
“Can I retroactively correct when each component was impacted during an incident?”
“Is there a way to replace an incident's whole per-component impact history?”
Tell an agent
Replace the impact timeline of incident {incidentId} on page {statusPageId} with {componentImpacts}.
Retroactively set the component windows for incident {incidentId} on status page {statusPageId} to {componentImpacts}.
GET /v3/status-pages/{statusPageId}/incidents/{incidentId}/incident-updates List the updates posted to an incident · List the updates of an incident #
Ask an LLM
“What progress updates have been posted on an incident so far?”
“How many updates does the incident update list return at most?”
Tell an agent
List updates for incident {incidentId} on status page {statusPageId}.
Show the newest-first update history of incident {incidentId} on page {statusPageId}.
POST /v3/status-pages/{statusPageId}/incidents/{incidentId}/incident-updates Post a progress update to an incident · Post an update to an incident #
Ask an LLM
“How do I post a status update to an ongoing incident?”
“Does posting a RESOLVED update close the incident?”
Tell an agent
Post update {description} with status {status} to incident {incidentId} on page {statusPageId}.
Resolve incident {incidentId} on status page {statusPageId} with the note {description} and status {status}.
DELETE /v3/status-pages/{statusPageId}/incidents/{incidentId}/incident-updates/{incidentUpdateId} Delete an incident update · Delete an incident update #
Ask an LLM
“Can I delete one update from an incident's history?”
“Why can't I delete the last remaining update on an incident?”
Tell an agent destructive · confirm first
Delete update {incidentUpdateId} from incident {incidentId} on status page {statusPageId}.
Remove the incident update {incidentUpdateId} posted on incident {incidentId}, page {statusPageId}.
GET /v3/status-pages/{statusPageId}/incidents/{incidentId}/incident-updates/{incidentUpdateId} Get a single incident update · Retrieve an incident update #
Ask an LLM
“What did one specific incident update say?”
“Can I read back a single update I posted to an incident?”
Tell an agent
Show update {incidentUpdateId} of incident {incidentId} on status page {statusPageId}.
Get incident update {incidentUpdateId} from incident {incidentId} on page {statusPageId}.
PUT /v3/status-pages/{statusPageId}/incidents/{incidentId}/incident-updates/{incidentUpdateId} Edit an incident update already posted · Edit an incident update #
Ask an LLM
“Can I fix a typo in an update I already posted to an incident?”
“Is it possible to change the status or public date on an existing incident update?”
Tell an agent
Edit update {incidentUpdateId} on incident {incidentId} (page {statusPageId}) to say {description} with status {status}.
Correct the text of incident update {incidentUpdateId} for incident {incidentId} on {statusPageId} to {description}, keeping status {status}.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/checkly:checkly-status-pages-v3-incidents-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

checkly-status-pages-v3-incidents-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Checkly Public Status Pages V3 Incidents API
  version: v1
  description: 'These are the docs for the newly released Checkly Public API.

    If you have any questions, please do not hesitate to get in touch with us.'
servers:
- url: https://api.checklyhq.com
security:
- Bearer: []
tags:


# --- truncated at 32 KB (32 KB total) ---
# Full source: https://artifacts.apis.io/checkly/openapi/checkly-status-pages-v3-incidents-api-openapi.yml