Get an incident by ID
Use a user token to access authenticated routes. The token must be specified in the Authorization HTTP header with the following format 'Authorization: Bearer
ID of the incident to show
Success, incident retrieved
1
Parent organization ID
1
Parent project ID
1
Incident title
"Service is not working as expected"
Incident unique slug name
"APP-123"
unknown, operational, degradedPerformance, partialOutage, majorOutage, maintenance unknown, investigating, identified, monitoring, resolved ongoing, recovering, recovered Description of the error that caused the incident
"The server answered with an unexpected status code: 503."
Flag to exclude the incident from downtime calculations
false
Date of incident confirmation
Date of incident recovery
Date of creation for the entity
Date of last update for the entity