Incident
An Incident represents an event or report registered in an office: an accident, a near-miss, a non-compliance, a malfunction report, or an intervention request.
Belongs to an office (via subtenant_id = office_id) and has a workflow status:
new: just reportedopen: being handledclosed: resolved (with closing date)
An incident can have:
- Involved people (IncidentPerson)
- Involved resources (IncidentResource): equipment, environments, substances, work groups, materials
- Linked corrective actions (IncidentAction)
Use this API to:
- Report a new incident in an office
- Browse incidents for an office (filter by
subtenant_id) - Filter by category or status
- Manage the incident lifecycle (new → open → closed)
- Version
- 2.0.0
- OpenAPI version
- 3.0.0
Authentication
Section titled “ Authentication ”OAuth2
Section titled “OAuth2 ”Security scheme type: oauth2
Flow type: password
Token URL: https://auth.4hse.com/realms/4hse/protocol/openid-connect/token
AccessToken
Section titled “AccessToken ”Security scheme type: apiKey
Query parameter name: access-token
Operations
Section titled “Operations” POST /v2/incident/index
Returns a paginated list of incidents.
Most useful filters:
subtenant_id(office_id): all incidents in an officestatus: filter by workflow status (new,open,closed)category: filter by incident typetenant_id(project_id): all incidents in a company
Authorizations
Section titled “Authorizations ”Request Body
Section titled “Request Body ”Parameters for searching incidents
object
object
object
Name of the office.
Name of the project.
Total number of people involved in the incident.
Total sickness days across all involved people.
Example
{ "filter": { "subtenant_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890", "status": "open" }, "per-page": 20, "page": 1, "sort": "-date_incident"}Responses
Section titled “ Responses ”List of incidents
object
object
Name of the office.
Name of the project.
Total number of people involved in the incident.
Total sickness days across all involved people.
Headers
Section titled “Headers ”Current page
Total number of pages
Number of items per page
Total number of items
create
Section titled “create” POST /v2/incident/create
Reports a new incident.
Requires name, date_incident, subtenant_id (office_id), and tenant_id (project_id).
The office_incident_id is auto-generated if not provided.
After creation, add involved people via IncidentPerson, involved resources via IncidentResource, and corrective actions via IncidentAction.
Authorizations
Section titled “Authorizations ”Request Body required
Section titled “Request Body required ”Incident to report
object
Unique identifier. Auto-generated if not provided.
Identifier code.
Title/name of the incident.
Date when the incident occurred.
Incident category:
NON_COMPLIANCE: non-complianceACCIDENTS: accidentACCIDENTS_AND_MISSED_INJURIES: accident and near-missREPORT_MALFUNCTION: malfunction reportREPORT_FAILURE: failure reportREQUEST_INSPECTION: inspection requestREQUEST_MAINTENANCE: maintenance requestREQUEST_REPLACEMENT: replacement requestREQUEST_INTERVENTION: intervention request
Description of what happened.
Description of actions taken.
Name of the person who reported the incident.
Incident managers (JSON).
Incident assignees (JSON).
Incident watchers (JSON).
Notification recipients (JSON).
object
Workflow status:
new: just reportedopen: being handledclosed: resolved (requiresdate_closed)
External reference number (e.g. INAIL, OSHA, CPAM case number).
Closing date. Required when status is closed.
Username of the person who created the incident. Auto-set on creation.
Creation timestamp. Auto-set on creation.
The project (company). Pass the project_id.
The office where the incident occurred. Pass the office_id.
Responses
Section titled “ Responses ”Incident reported successfully
object
Unique identifier. Auto-generated if not provided.
Identifier code.
Title/name of the incident.
Date when the incident occurred.
Incident category:
NON_COMPLIANCE: non-complianceACCIDENTS: accidentACCIDENTS_AND_MISSED_INJURIES: accident and near-missREPORT_MALFUNCTION: malfunction reportREPORT_FAILURE: failure reportREQUEST_INSPECTION: inspection requestREQUEST_MAINTENANCE: maintenance requestREQUEST_REPLACEMENT: replacement requestREQUEST_INTERVENTION: intervention request
Description of what happened.
Description of actions taken.
Name of the person who reported the incident.
Incident managers (JSON).
Incident assignees (JSON).
Incident watchers (JSON).
Notification recipients (JSON).
object
Workflow status:
new: just reportedopen: being handledclosed: resolved (requiresdate_closed)
External reference number (e.g. INAIL, OSHA, CPAM case number).
Closing date. Required when status is closed.
Username of the person who created the incident. Auto-set on creation.
Creation timestamp. Auto-set on creation.
The project (company). Pass the project_id.
The office where the incident occurred. Pass the office_id.
GET /v2/incident/view/{id}
Retrieves a single incident by its ID.
Authorizations
Section titled “Authorizations ”Path Parameters
Section titled “Path Parameters ”The office_incident_id to retrieve.
Responses
Section titled “ Responses ”Incident found
object
object
Name of the office.
Name of the project.
Total number of people involved in the incident.
Total sickness days across all involved people.
Incident not found
update
Section titled “update” PUT /v2/incident/update/{id}
Updates an existing incident.
Common use case: changing status to open (being handled) or closed (resolved).
When setting status to closed, the date_closed field is required.
Authorizations
Section titled “Authorizations ”Path Parameters
Section titled “Path Parameters ”The office_incident_id to update.
Request Body required
Section titled “Request Body required ”Fields to update
object
Unique identifier. Auto-generated if not provided.
Identifier code.
Title/name of the incident.
Date when the incident occurred.
Incident category:
NON_COMPLIANCE: non-complianceACCIDENTS: accidentACCIDENTS_AND_MISSED_INJURIES: accident and near-missREPORT_MALFUNCTION: malfunction reportREPORT_FAILURE: failure reportREQUEST_INSPECTION: inspection requestREQUEST_MAINTENANCE: maintenance requestREQUEST_REPLACEMENT: replacement requestREQUEST_INTERVENTION: intervention request
Description of what happened.
Description of actions taken.
Name of the person who reported the incident.
Incident managers (JSON).
Incident assignees (JSON).
Incident watchers (JSON).
Notification recipients (JSON).
object
Workflow status:
new: just reportedopen: being handledclosed: resolved (requiresdate_closed)
External reference number (e.g. INAIL, OSHA, CPAM case number).
Closing date. Required when status is closed.
Username of the person who created the incident. Auto-set on creation.
Creation timestamp. Auto-set on creation.
The project (company). Pass the project_id.
The office where the incident occurred. Pass the office_id.
Responses
Section titled “ Responses ”Incident updated successfully
object
Unique identifier. Auto-generated if not provided.
Identifier code.
Title/name of the incident.
Date when the incident occurred.
Incident category:
NON_COMPLIANCE: non-complianceACCIDENTS: accidentACCIDENTS_AND_MISSED_INJURIES: accident and near-missREPORT_MALFUNCTION: malfunction reportREPORT_FAILURE: failure reportREQUEST_INSPECTION: inspection requestREQUEST_MAINTENANCE: maintenance requestREQUEST_REPLACEMENT: replacement requestREQUEST_INTERVENTION: intervention request
Description of what happened.
Description of actions taken.
Name of the person who reported the incident.
Incident managers (JSON).
Incident assignees (JSON).
Incident watchers (JSON).
Notification recipients (JSON).
object
Workflow status:
new: just reportedopen: being handledclosed: resolved (requiresdate_closed)
External reference number (e.g. INAIL, OSHA, CPAM case number).
Closing date. Required when status is closed.
Username of the person who created the incident. Auto-set on creation.
Creation timestamp. Auto-set on creation.
The project (company). Pass the project_id.
The office where the incident occurred. Pass the office_id.
Incident not found
delete
Section titled “delete” DELETE /v2/incident/delete/{id}
Deletes an incident.
If force=false (default), the response lists child entities (people, resources, actions).
If force=true, the incident and all related entities are deleted.
Authorizations
Section titled “Authorizations ”Path Parameters
Section titled “Path Parameters ”The office_incident_id to delete.
Query Parameters
Section titled “Query Parameters ”If true, deletes the incident and all child entities.
Responses
Section titled “ Responses ”Incident deleted successfully
Preview of entities that would be deleted (returned when force=false)