Incident summary counts
Get aggregated incident counts by type hierarchy.
Returns counts grouped by incident_type → event_type → event_subtype. Supports the same filters as the list endpoint (type, status, severity, spatial, time range) but without pagination — the response is a single summary object. Both type and status accept comma-separated values (e.g. ?status=active,upcoming).
The response includes two top-level keys:
- types — filtered counts matching the current query parameters.
- catalog — an unfiltered list of every incident_type / event_type / event_subtype combination that exists in the database. This is always the full set regardless of filters, so UIs can render complete filter menus (including categories with a zero count in the current view).
Request
- Base URL: https://api.mapulus.com
- URL: https://api.mapulus.com/v1/data/incidents/summary
- Auth: HTTP bearer
Query parameters
Filter by incident type (traffic, fire, power, weather). Comma-separated for multiple.
Filter by event type (e.g. roadworks, crash, flood, fire_vegetation).
Filter by event subtype (e.g. flash_flood, planned_roadworks, multi_vehicle).
Filter by status (active, upcoming, resolved, expired). Comma-separated for multiple.
Filter by state (QLD, NSW, etc.).
Filter by severity (minor, moderate, major, extreme).
Filter by source_id.
Incidents intersecting this boundary (e.g. lga:17200).
Latitude for radius search.
Longitude for radius search.
Search radius in km (requires lat, lng).
Incidents started after this ISO datetime.
Incidents started before this ISO datetime.
Incidents with expected_end_at after this ISO datetime.
Incidents with expected_end_at before this ISO datetime.
Response
Aggregated counts by incident_type, event_type, and event_subtype.
Changes
No recorded changes to this operation across all 1 revision of this API.