Vera Public API (1.0.0)
Public REST API for fleet tracking data (vehicles, live locations, reports, and history). Replaces the legacy SOAP web service; the modernized JSON field names below fully replace the legacy SOAP fields for all API consumers.
All endpoints require an API key sent as an HTTP Bearer token: Authorization: Bearer <key>. Keys are issued per firm; each key is scoped to that firm's vehicles only.
Successful responses always use the shape { "data": ..., "meta": { "count": N } }. Failures use { "error": { "code": "...", "message": "..." } } with a machine-readable code and a human-readable English message.
If a requested deviceId does not belong to the caller's account (per the key's vehicle scope), the API does not return 404/403 — it returns HTTP 200 with an empty result: { "data": [], "meta": { "count": 0 } }. This matches the legacy service's "no result set" behavior for unauthorized/unknown devices.
Report and history endpoints that accept date1/date2 enforce a server-side maximum range:
/v1/history/tracking: 300 days- all other date-ranged endpoints (
/v1/reports/mileage,/v1/reports/working-hours,/v1/reports/heat,/v1/history/alarms): 32 days
Exceeding the cap, or sending date1 after date2, or an unparseable date, returns HTTP 422 with {"error":{"code":"INVALID_DATE_RANGE", ...}}.