Aggregate Incidents

post

https://developer.beta.salussafety.io/v1/incident/aggregate

Aggregate incidents with GROUP BY operations.

Allows grouping by status, severity, site_id, user_id, and is_archived fields with aggregation
functions like COUNT, SUM, AVG, MIN, MAX. Uses the same base filters and company scoping
as the search endpoint for consistent behavior.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

Request model for incident aggregation queries.

query

string | null

Keywords should be space separated and are ANDed together, so all keywords must be present but they can be present in any of the fields specified above.

skip

integer | null

Defaults to 0

Number of records to skip before returning records

limit

integer | null

Defaults to 50

Number of records to return

sort_direction

string

enum

Defaults to desc

Direction to sort the sort_column - ascending or descending

Allowed:

date_start

date-time | null

If sorting on updated_at or created_at, and date_cut_off is provided, return only records that were created or updated (whichever is being sorted on) between date_start and date_cut_off

date_cut_off

date-time | null

If sorting on updated_at or created_at, return only records that were created or updated (whichever is being sorted on) between the initial value (determined by sort order) and the cutoff date.

For example, sorting on created_at ascending with a date_cut_off will return all records from the oldest creation date to the cutoff date. By comparison, sorting on created_at descending with a date_cut_off will return all records from the most recent creation date to the cutoff date.

sort_column

string | null

Column to sort aggregation results by (must be in group_by or an aggregation alias)

group_by

array of strings

required

Column names to group by

Group By*

aggregations

array of objects

required

Aggregation functions to apply

Aggregations*

date_filter_column

string

enum

Defaults to updated_at

Column to apply date_start/date_cut_off filters on. One of 'created_at' (when the row was logged), 'updated_at' (last modification), 'incident_date' (when the incident occurred — usually what users mean by 'incidents on April 22'), or 'back_to_work_date' (return-to-work for lost-time incidents; excludes incidents without an RTW).

Allowed:

is_archived

boolean | null

Defaults to false

Filter by entity archived status. Defaults to False (only active entities). Use True for archived only, None to include all.

project_is_archived

boolean | null

Defaults to false

Filter by parent project's archived status. Defaults to False (only active projects). Use True for archived projects only, None to include all.

site_id

integer | null

Filter to incidents at a specific site.

status

string | null

Filter by incident status: Open, Investigation_In_Progress, Under_Review, Investigation_Approved, Pending_Action, Under_Appeal, or Closed.

severity

string | null

Filter by incident severity.

Responses

200Successful Response

400Invalid aggregation request

403Permission denied

409Integrity Error or Data Conflict

422Validation Error