Empowerly Incidents API
Incident history and currently unresolved incidents.
Incident history and currently unresolved incidents.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
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.curl "https://apis.io/api/v1/apis/empowerly-incidents-api"
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
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: 3.2.0
info:
title: Empowerly Status Incidents API
version: v2
summary: Read-only status, component, incident and maintenance data for the Empowerly platform.
description: Unauthenticated JSON API served from Empowerly's own status subdomain (status.empowerly.com) by Atlassian Statuspage. Empowerly does not publish an API reference for this surface; every path, status code and response shape in this document was DERIVED from live unauthenticated probes of https://status.empowerly.com on 2026-08-12 (see x-evidence). Nothing here is invented — schemas describe the fields actually returned by those probes. Fields Statuspage may return but that were not observed on this page (for example populated incident objects, since Empowerly's incident history was empty at probe time) are documented as nullable/optional and marked accordingly.
contact:
name: Empowerly
url: https://empowerly.com/
x-provenance:
generated: '2026-08-12'
method: derived
source: live unauthenticated probes of https://status.empowerly.com/api/v2/* on 2026-08-12; response schemas modeled from the observed bodies
hosted_by: Atlassian Statuspage
first_party: false
x-evidence:
fetched: '2026-08-12'
probes:
- url: https://status.empowerly.com/api/v2/summary.json
http_status: 200
content_type: application/json; charset=utf-8
- url: https://status.empowerly.com/api/v2/status.json
http_status: 200
content_type: application/json; charset=utf-8
- url: https://status.empowerly.com/api/v2/components.json
http_status: 200
content_type: application/json; charset=utf-8
- url: https://status.empowerly.com/api/v2/incidents.json
http_status: 200
content_type: application/json; charset=utf-8
- url: https://status.empowerly.com/api/v2/incidents/unresolved.json
http_status: 200
content_type: application/json; charset=utf-8
- url: https://status.empowerly.com/api/v2/scheduled-maintenances.json
http_status: 200
content_type: application/json; charset=utf-8
- url: https://status.empowerly.com/api/v2/scheduled-maintenances/upcoming.json
http_status: 200
content_type: application/json; charset=utf-8
- url: https://status.empowerly.com/api/v2/scheduled-maintenances/active.json
http_status: 200
content_type: application/json; charset=utf-8
- url: https://status.empowerly.com/api/v2/bogus.json
http_status: 404
note: negative control — unknown paths under /api/v2 return 404
servers:
- url: https://status.empowerly.com/api/v2
description: Empowerly public status page API (Atlassian Statuspage)
security: []
tags:
- name: Incidents
description: Incident history and currently unresolved incidents.
paths:
/incidents.json:
get:
tags:
- Incidents
operationId: listIncidents
summary: List incidents
description: Incident history for the page. Empowerly's incident array was empty at probe time, so the Incident schema below documents the Statuspage incident shape as optional/nullable rather than asserting fields observed on this page.
security: []
responses:
'200':
description: Incident list
content:
application/json:
schema:
$ref: '#/components/schemas/IncidentsResponse'
'404':
$ref: '#/components/responses/NotFound'
/incidents/unresolved.json:
get:
tags:
- Incidents
operationId: listUnresolvedIncidents
summary: List unresolved incidents
security: []
responses:
'200':
description: Unresolved incident list
content:
application/json:
schema:
$ref: '#/components/schemas/IncidentsResponse'
'404':
$ref: '#/components/responses/NotFound'
components:
schemas:
Page:
type: object
description: Identity of the status page itself. Present on every response.
properties:
id:
type: string
description: Statuspage page identifier.
examples:
- thhkhnjsm4jy
name:
type: string
examples:
- Empowerly
url:
type: string
format: uri
examples:
- https://status.empowerly.com
time_zone:
type: string
examples:
- America/Los_Angeles
updated_at:
type: string
format: date-time
required:
- id
- name
- url
- updated_at
IncidentsResponse:
type: object
properties:
page:
$ref: '#/components/schemas/Page'
incidents:
type: array
items:
$ref: '#/components/schemas/Incident'
required:
- page
- incidents
Component:
type: object
properties:
id:
type: string
examples:
- h2qv5hy8rsbp
name:
type: string
examples:
- Empowerly Web Portal
status:
type: string
enum:
- operational
- degraded_performance
- partial_outage
- major_outage
- under_maintenance
examples:
- operational
created_at:
type: string
format: date-time
updated_at:
type: string
format: date-time
position:
type: integer
description:
type:
- string
- 'null'
showcase:
type: boolean
start_date:
type:
- string
- 'null'
format: date
group_id:
type:
- string
- 'null'
page_id:
type: string
group:
type: boolean
only_show_if_degraded:
type: boolean
required:
- id
- name
- status
- page_id
Incident:
type: object
description: Statuspage incident object. Empowerly published zero incidents at probe time, so no field here was directly observed on this page; the shape is documented as optional.
properties:
id:
type: string
name:
type: string
status:
type: string
enum:
- investigating
- identified
- monitoring
- resolved
- postmortem
impact:
type: string
enum:
- none
- minor
- major
- critical
shortlink:
type: string
format: uri
created_at:
type: string
format: date-time
updated_at:
type: string
format: date-time
monitoring_at:
type:
- string
- 'null'
format: date-time
resolved_at:
type:
- string
- 'null'
format: date-time
page_id:
type: string
incident_updates:
type: array
items:
type: object
components:
type: array
items:
$ref: '#/components/schemas/Component'
responses:
NotFound:
description: Unknown path under /api/v2. Observed as an HTML error document, not a JSON problem object — this API does not implement RFC 9457.
content:
text/html:
schema:
type: string