API 2.0.0: active contract required
POST /incidents requires a contract with status active. Status approved is insufficient. Without an active contract, the request fails with HTTP 422 and EMPLOYEE_HAS_NO_ACTIVE_CONTRACT, including when dryRun=true; no incident is created. Resolve the contract state through the responsible business process before submitting a new request with a new X-Request-ID.
Existing incidents remain editable under their existing lifecycle and field restrictions. This new prerequisite applies to creation. The employee activation prerequisite remains documented separately; no precedence between validation errors is specified.
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.