IncidentPerson
Manage incident persons, which represent people involved in incidents.
You can create, update, delete, and search for incident persons with advanced filtering and pagination.
- Version
- 2.0.0
- OpenAPI version
- 3.0.0
Operations
Section titled “Operations” POST /v2/incident-person/index
Returns a paginated and filterable list of incident persons.
Use POST to allow complex filters via JSON payload.
Request Body
Section titled “Request Body ”Parameters for searching incident persons
object
object
Primary key for office incident person
ID of the related office incident
ID of the person involved in the office incident
ID of the tenant
ID of the subtenant
ID of the person involved
The field of the model to sort the list for, use a minus to revert the sort. Es -name is to require the sort in reverse order
The field establishes whether to also include historized elements that are no longer active in the results. If you leave this parameter empty the response returns only actual entries.
Example
{ "filter": { "office_incident_id": "inc-1" }, "per-page": 10, "page": 1, "sort": "office_incident_person_id"}
Responses
Section titled “ Responses ”List of incident persons
object
Primary key for office incident person
ID of the related office incident
ID of the person involved in the office incident
ID of the tenant
ID of the subtenant
ID of the person involved
Example
{ "office_incident_person_id": "ip-1", "office_incident_id": "inc-1", "person_office_id": "po-1", "code": "P001", "description": "Injured person", "days": 2, "tenant_id": "ten-1", "subtenant_id": "sub-1"}
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-person/create
Create a new incident person by providing the required details.
Request Body required
Section titled “Request Body required ”Incident person object to be created
object
Primary key for office incident person
ID of the related office incident
ID of the person involved in the office incident
ID of the tenant
ID of the subtenant
Example
{ "office_incident_id": "inc-1", "person_office_id": "po-1", "code": "P002", "description": "Witness", "days": 0, "tenant_id": "ten-1", "subtenant_id": "sub-1"}
Responses
Section titled “ Responses ”Incident person created successfully
object
Primary key for office incident person
ID of the related office incident
ID of the person involved in the office incident
ID of the tenant
ID of the subtenant
Example
{ "office_incident_person_id": "ip-2", "office_incident_id": "inc-1", "person_office_id": "po-1", "code": "P002", "description": "Witness", "days": 0, "tenant_id": "ten-1", "subtenant_id": "sub-1"}
GET /v2/incident-person/view/{id}
Retrieve an incident person by its unique ID.
Path Parameters
Section titled “Path Parameters ”ID of the incident person to retrieve
Responses
Section titled “ Responses ”Incident person found
object
Primary key for office incident person
ID of the related office incident
ID of the person involved in the office incident
ID of the tenant
ID of the subtenant
ID of the person involved
Example
{ "office_incident_person_id": "ip-1", "office_incident_id": "inc-1", "person_office_id": "po-1", "code": "P001", "description": "Injured person", "days": 2, "tenant_id": "ten-1", "subtenant_id": "sub-1"}
Incident person not found
delete
Section titled “delete” DELETE /v2/incident-person/delete/{id}
Delete an incident person by its unique ID.
If force=true, all related entities will also be deleted.
Path Parameters
Section titled “Path Parameters ”ID of the incident person to delete
Query Parameters
Section titled “Query Parameters ”Force the deletion of the entity and all related entities
Responses
Section titled “ Responses ”Incident person deleted successfully
If force=false, the operation is interrupted and the list of connected entities that will be deleted in case of confirmation (force=true) is returned
update
Section titled “update” PUT /v2/incident-person/update/{id}
Update an existing incident person by its unique ID.
Path Parameters
Section titled “Path Parameters ”ID of the incident person to update
Request Body required
Section titled “Request Body required ”Incident person object with updated data
object
Primary key for office incident person
ID of the related office incident
ID of the person involved in the office incident
ID of the tenant
ID of the subtenant
Example
{ "description": "Updated description", "days": 3}
Responses
Section titled “ Responses ”Incident person updated successfully
object
Primary key for office incident person
ID of the related office incident
ID of the person involved in the office incident
ID of the tenant
ID of the subtenant
Example
{ "office_incident_person_id": "ip-1", "description": "Updated description", "days": 3}
Incident person not found