Statuspage

Statuspage

This connector works with Atlassian Statuspage through its management REST API (https://api.statuspage.io/v1): your status pages, their components and component groups with uptime, incidents and scheduled maintenances with every update, incident templates, subscribers and system metrics. It can open and update incidents, announce maintenances, change component statuses, manage subscribers and push metric data. The public status API of a page (<page>.statuspage.io/api/v2) is not used.

Setup (2 minutes)

1. Sign in at https://manage.statuspage.io, open your avatar menu (bottom left) and choose API info (https://manage.statuspage.io/login then API info).
2. Copy an existing API key or create one. The key acts with the rights of the user it belongs to and reaches every page of the organization; it cannot be limited to read-only.
3. Paste the key into STATUSPAGE_API_KEY (the key alone; the connector sends Authorization: OAuth <key>) and run statuspage_list_pages to check it. The page id is also shown on the API info page.

Workflow

• Find the page: statuspage_list_pages, then statuspage_get_page. Every other tool needs its page_id.
• What is down right now: statuspage_list_unresolved_incidents, statuspage_list_active_maintenances, statuspage_list_components (component status), then statuspage_get_incident. History and search: statuspage_list_incidents with q.
• Components: statuspage_get_component, statuspage_update_component (change a status without an incident), statuspage_create_component. Groups: statuspage_list_component_groups, statuspage_get_component_group, statuspage_create_component_group, statuspage_update_component_group. Uptime reports: statuspage_get_component_uptime, statuspage_get_component_group_uptime.
• Incident communication: look at statuspage_list_incident_templates for agreed wording, then statuspage_create_incident with the affected components and their status. Post progress with statuspage_update_incident (status identified, monitoring, then resolved, with a body each time, and the components back to operational). Fix a typo in an earlier update with statuspage_edit_incident_update. After the incident: statuspage_get_postmortem. statuspage_delete_incident is switched off by default. New templates: statuspage_create_incident_template.
• Planned work: statuspage_create_scheduled_maintenance with the window and components (with scheduled_auto_in_progress / scheduled_auto_completed it runs by itself), then statuspage_list_upcoming_incidents and statuspage_list_scheduled_incidents; move or close it with statuspage_update_incident (in_progress, verifying, completed).
• Subscribers: statuspage_count_subscribers or statuspage_get_subscriber_histogram for numbers, statuspage_list_subscribers (search with q), statuspage_get_subscriber, statuspage_list_unsubscribed_subscribers, statuspage_list_incident_subscribers. Changes: statuspage_create_subscriber, statuspage_unsubscribe_subscriber.
• Metrics: statuspage_list_metrics, statuspage_get_metric, statuspage_list_metrics_providers; push a point to a self-submitted metric with statuspage_add_metric_data.

Before writing: incidents, maintenances and component statuses are public, and by default every change emails, texts and calls webhooks of all subscribers. Confirm the wording and the components with the user first; pass deliver_notifications: false for a quiet change.

Reading the answers: ids are 12-character strings. Times are ISO 8601 with time zone; uptime dates are YYYY-MM-DD in the page's time zone, outage durations are seconds. Component status is operational, under_maintenance, degraded_performance, partial_outage or major_outage. Incident impact is none, maintenance, minor, major or critical; incident_updates is newest first. Page colours and logo URLs are left out of the page answers.

Paging: lists take page (from 1) and per_page (at most 100); statuspage_list_incidents uses limit instead of per_page. statuspage_list_subscribers counts page from 0 and returns everything without limit. A page shorter than the page size is the last one.

Limits and errors: each key may make about 1 request per second (measured over a minute); 420 or 429 means wait and retry. 401 is a wrong or deleted key, 404 an unknown id or a page the key cannot reach, 422 a validation error naming the field (e.g. a status that does not fit the incident type).