GET
/
uptime
/
incidents
/
{incidentId}
curl --request GET \
  --url https://api.phare.io/uptime/incidents/{incidentId} \
  --header 'Authorization: Bearer <token>'
{
  "id": 1,
  "organization_id": 1,
  "project_id": 1,
  "uptime_monitor_id": 1,
  "title": "Service is not working as expected",
  "slug": "APP-123",
  "impact": "unknown",
  "state": "unknown",
  "status": "ongoing",
  "description": "The server answered with an unexpected status code: 503.",
  "exclude_from_downtime": false,
  "incident_at": "2023-11-07T05:31:56Z",
  "recovery_at": "2023-11-07T05:31:56Z",
  "created_at": "2023-11-07T05:31:56Z",
  "updated_at": "2023-11-07T05:31:56Z"
}
Please be aware that the Phare API is currently in beta and is subject to change.

Authorizations

Authorization
string
header
required

Use a user token to access authenticated routes. The token must be specified in the Authorization HTTP header with the following format 'Authorization: Bearer <token>'.

Path Parameters

incidentId
integer
required

ID of the incident to show

Response

200
application/json
Success, incident retrieved
id
number
organization_id
number

Parent organization ID

project_id
number

Parent project ID

uptime_monitor_id
number

Parent uptime monitor ID

title
string

Incident title

slug
string

Incident unique slug name

impact
enum<string>
Available options:
unknown,
operational,
degradedPerformance,
partialOutage,
majorOutage,
maintenance
state
enum<string>
Available options:
unknown,
investigating,
identified,
monitoring,
resolved
status
enum<string>
Available options:
ongoing,
recovering,
recovered
description
string

Description of the error that caused the incident

exclude_from_downtime
boolean

Flag to exclude the incident from downtime calculations

incident_at
string | null

Date of incident confirmation

recovery_at
string | null

Date of incident recovery

created_at
string

Date of creation for the entity

updated_at
string

Date of last update for the entity