Skip to main content
Incidents are linked to an employee in the API-key scope. The referenced employee must be activated before an incident can be created. The server assigns reporter metadata and lifecycle status.

Domain values

Status is server-managed; the public patch operation exposes documented editable fields rather than an arbitrary status update.

Endpoints

List incidents

Filter and sort incidents by number, type, status, employee, reporter, and dates.

Create an incident

Report a temporary or permanent incident for an authorized, activated employee.

Get an incident

Read current server-managed status and dates.

Update an incident

Patch supported type and date fields; incidents cannot be reopened.

Upload attachments

Upload permitted image or PDF evidence to an editable completed incident.

Attachment limits

Incident integration guide

Review lifecycle ownership, supported updates, file validation, and data-minimization controls.
Last modified on September 2, 2026