Skip to main content
NopeCHA

Developer documentation

Status API

Programmatic access to the current status of NopeCHA, public incidents, scheduled maintenance, and notification feeds.

GET https://status.nopecha.com/api/v2/summary.json Recommended starting point

Getting started

Basics

All endpoints are public, read-only, and require no authentication. Requests use GET and return either JSON or a standard syndication feed.

Use the API for automated access instead of scraping the status page. Timestamps in JSON responses are returned in UTC.

Public status pages also support an agent-friendly Markdown representation. Send Accept: text/markdown to the page URL to receive a concise, text-only snapshot.

Public endpoints

Page status

4 endpoints

Use these endpoints to understand the current state of the status page and its services.

GET

Summary (legacy)

JSON

The original summary endpoint. New integrations should use the versioned JSON endpoint below.

https://status.nopecha.com/api/v1/summary Open response
Example request
curl --request GET 'https://status.nopecha.com/api/v1/summary'
GET

Summary

JSON

A complete snapshot of the page, including the overall status, components, unresolved incidents, and scheduled maintenance.

https://status.nopecha.com/api/v2/summary.json Open response
Example request
curl --request GET 'https://status.nopecha.com/api/v2/summary.json'
GET

Status

JSON

The overall status indicator and a human-readable description for the page.

https://status.nopecha.com/api/v2/status.json Open response
Example request
curl --request GET 'https://status.nopecha.com/api/v2/status.json'
GET

Components

JSON

Every public service and site, including its current status, position, group, and location.

https://status.nopecha.com/api/v2/components.json Open response
Example request
curl --request GET 'https://status.nopecha.com/api/v2/components.json'

Public endpoints

Incidents

2 endpoints

Read current or historical incident information in a machine-readable format.

GET

Unresolved incidents

JSON

Incidents that are currently investigating, identified, or monitoring.

https://status.nopecha.com/api/v2/incidents/unresolved.json Open response
Example request
curl --request GET 'https://status.nopecha.com/api/v2/incidents/unresolved.json'
GET

All incidents

JSON

The 50 most recent incidents, including resolved incidents and their public updates.

https://status.nopecha.com/api/v2/incidents.json Open response
Example request
curl --request GET 'https://status.nopecha.com/api/v2/incidents.json'

Public endpoints

Scheduled maintenance

3 endpoints

Track upcoming, active, and recently completed maintenance windows.

GET

Upcoming

JSON

Maintenance events that are still in the scheduled state.

https://status.nopecha.com/api/v2/scheduled-maintenances/upcoming.json Open response
Example request
curl --request GET 'https://status.nopecha.com/api/v2/scheduled-maintenances/upcoming.json'
GET

Active

JSON

Maintenance events currently in progress or being verified.

https://status.nopecha.com/api/v2/scheduled-maintenances/active.json Open response
Example request
curl --request GET 'https://status.nopecha.com/api/v2/scheduled-maintenances/active.json'
GET

All maintenance

JSON

The 50 most recent maintenance events, including completed events.

https://status.nopecha.com/api/v2/scheduled-maintenances.json Open response
Example request
curl --request GET 'https://status.nopecha.com/api/v2/scheduled-maintenances.json'

Public endpoints

Feeds

5 endpoints

Subscribe to incident and maintenance updates with the feed reader of your choice.

GET

Status history RSS

RSS 2.0

Recent public incident updates, with links back to their incident pages.

https://status.nopecha.com/history.rss Open response
Example request
curl --request GET 'https://status.nopecha.com/history.rss'
GET

Incidents RSS

RSS 2.0

The 50 most recent incidents, with links to their public incident pages.

https://status.nopecha.com/api/v3/incidents.rss Open response
Example request
curl --request GET 'https://status.nopecha.com/api/v3/incidents.rss'
GET

Incidents Atom

Atom 1.0

The 50 most recent incidents in Atom format.

https://status.nopecha.com/api/v3/incidents.atom Open response
Example request
curl --request GET 'https://status.nopecha.com/api/v3/incidents.atom'
GET

Maintenance RSS

RSS 2.0

The 50 most recent scheduled maintenance events, including maintenance window end dates.

https://status.nopecha.com/api/v3/maintenance.rss Open response
Example request
curl --request GET 'https://status.nopecha.com/api/v3/maintenance.rss'
GET

Maintenance Atom

Atom 1.0

The 50 most recent scheduled maintenance events in Atom format.

https://status.nopecha.com/api/v3/maintenance.atom Open response
Example request
curl --request GET 'https://status.nopecha.com/api/v3/maintenance.atom'

Reference

Common status values

ValueMeaning
noneThe overall page is operating normally.
minorThe page has a minor service issue.
majorThe page has a partial service outage.
criticalThe page has a major service outage.
maintenanceOne or more services are under maintenance.
operationalA component is operating normally.
degraded_performanceA component is available with reduced performance.
partial_outageA portion of a component is unavailable.
major_outageA component is substantially or completely unavailable.