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
A project header is required when using an organization-scoped API key.
1
A project header is required when using an organization-scoped API key.
"luminous-guiding-tower"
ID of the incident to show
Success, incident retrieved
1
Parent project ID
1
monitor, manual Incident unique slug name
"APP-123"
unknown, investigating, identified, monitoring, resolved ongoing, recovering, recovered unknown, operational, degradedPerformance, partialOutage, majorOutage, maintenance Incident title
"Service is not working as expected"
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
List of monitors linked to the incident
1 - 100 elements[1, 2, 3]Date of creation for the entity
Date of last update for the entity