v1

latestOpenAPI 3.1.02026-07-2466150275.0 KB

Incidents

Aggregate Incidents

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.

post/v1/incident/aggregate

Request body

querystring nullable

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.

skipinteger nullable

Number of records to skip before returning records

limitinteger nullable

Number of records to return

sort_direction'asc' | 'desc'

Direction to sort the sort_column - ascending or descending.

date_startstring date-time nullable

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_offstring date-time nullable

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_columnstring nullable

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

group_bystring[] required

Column names to group by

date_filter_column'created_at' | 'updated_at' | 'incident_date' | 'back_to_work_date'

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).

is_archivedboolean nullable

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

project_is_archivedboolean nullable

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

site_idinteger nullable

Filter to incidents at a specific site.

statusstring nullable

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

severitystring nullable

Filter by incident severity.

Example request

{
  "aggregations": [
    {
      "alias": "total_incidents",
      "column": "id",
      "operator": "count"
    },
    {
      "alias": "total_lost_time",
      "column": "lost_time",
      "operator": "sum"
    }
  ],
  "date_filter_column": "updated_at",
  "group_by": [
    "status",
    "severity"
  ],
  "is_archived": false,
  "limit": 50,
  "project_is_archived": false,
  "skip": 0,
  "sort_column": "total_incidents",
  "sort_direction": "desc"
}

Response

Successful Response

errorboolean

A boolean error indicator.

messagestring nullable

Optional message.

Example response

{
  "data": {
    "data": [
      {
        "count_by_site": 13,
        "severity": "low",
        "status": "active"
      },
      {
        "count_by_site": 14,
        "severity": "high",
        "status": "closed"
      }
    ],
    "metadata": {
      "aggregations": [
        {
          "alias": "count_by_site",
          "column": "site_id",
          "operator": "count"
        }
      ],
      "group_by_columns": [
        "status",
        "severity"
      ]
    },
    "total_groups": 3
  }
}