Mark Alert as Read
Alerts
Mark alert read
Mark one alert record as read.
POST
Mark Alert as Read
Overview
Marks a specific alert record (alert id + exact UTC timestamp) as read.⚠️ Note: The implementation always setsMarkedAsReadDatetoDateTime.UtcNowand does not branch onisRead—the query parameter is effectively ignored.
A V2 version of this endpoint is available: Update alert read status. New integrations should prefer V2.
Endpoint
POST /api/SetAlertAsRead
Query parameters
Alert id.
Exact UTC timestamp of the alert occurrence row.
Intended read flag (not applied in current code).
Response
200 OK empty body.Error responses
| Status | Meaning |
|---|---|
| 404 | Alert not found or no access |
Authorizations
JWT Bearer token obtained from POST /api/authentication/token/user or POST /api/authentication/token/api-key.
Lifetime: ~24 hours (86,399 seconds). Cache the token and reuse it. Re-authenticate 5 minutes before expiry.
Scoping:
- User tokens are scoped to a single company.
- API key tokens may restrict access to a vehicle allowlist and/or action set (see token claims).
No refresh endpoint — re-authenticate with your credentials when the token expires.
Headers
Standard and must keep as it is.
Bearer your_token
Response
Successful response
The response is of type object.