Alert configurations (V2)
Companies & fleet
Alert configurations
Paginated list of alert definitions for the company and its sub-companies.
GET
Alert configurations (V2)
Overview
Returns alert configuration records (definitions, not triggered events) for the company and its sub-companies. Each record includes the human-readableAlertType string, the vehicles or tags the alert monitors, and whether it applies to the whole fleet.
This is a new V2-only endpoint with no V1 equivalent.
Rate limit: 20 requests per 60 seconds per token.
Endpoint
GET /api/v2/companies/{id}/alerts
Path parameters
Company ID.
Query parameters
Page number (1-based).
Records per page.
Response
200 OK —PagedListResult<AlertConfigDto>
| Field | Type | Description |
|---|---|---|
| alertId | integer | Alert definition ID — use this when linking to webhooks |
| alertType | string | Human-readable alert type label (e.g. "Speeding", "Geofence") |
| companyId | integer | Company the alert belongs to |
| alertName | string | Alert name from the latest snapshot |
| alertDescription | string | Alert description from the latest snapshot |
| isAllFleet | boolean | true if the alert applies to all vehicles in the company |
| isAllTags | boolean | true if the alert applies to all tags in the company |
| units | array | Vehicles explicitly monitored (see below) — empty when isAllFleet is true |
| tags | string[] | Tags monitored — empty when isAllTags is true |
Units items:
| Field | Type | Description |
|---|---|---|
| vehicleId | integer | null | Legacy vehicle ID |
| name | string | Vehicle display name |
| imei | string | null | Device IMEI |
| vin | string | null | Vehicle VIN |
Example response
Error responses
| Status | Meaning |
|---|---|
| 401 | Token not scoped to this company |
| 403 | Company not in caller’s accessible hierarchy |
| 404 | Company not found |
Authorizations
JWT Bearer token obtained from POST /api/v2/authentication/token/api-key.
Lifetime: ~24 hours (86,399 seconds). Cache the token and reuse it. Re-authenticate 5 minutes before expiry.
Scoping: API key tokens are scoped to the company the key belongs to and may restrict access to a vehicle allowlist and/or action set (see token claims).
No refresh endpoint — re-authenticate with your API key when the token expires.
Path Parameters
Response
Successful response