Aller au contenu principal

Version 1.26.0112.2

New

  • GET /tachographs/driving-times: Added an endpoint to retrieve driving/rest time data for one or more drivers within a date range.

Improvements

  • GET /vehicles/events: Reduced query complexity for heavy event requests, preventing timeouts on large result sets and improving response times for all-vehicles queries — expect ~16–24% faster responses.
  • GET /vehicles/{registration}/events: Same improvement for per-vehicle event requests — avoids timeouts and delivers faster responses for large queries.

Bug Fixes

  • GET /tachographs: No longer throws errors when listing files with date filters; created_at timestamps are parsed consistently.
  • GET /tachographs/driving-times: Fixed an issue where subuser access to this endpoint was incorrectly rejected.
  • POST /geofences: Improved validation for circular geofences so decimal latitude/longitude values are accepted and malformed requests no longer cause server errors when creating circular geofences.
  • POST /vision/videos/requests: Strengthened validation to prevent overlapping or invalid video requests, reducing failures when creating video requests.
  • GET /fitments: Added validation for start_date and end_date parameters to reject invalid dates and avoid incorrect queries.
  • GET /vehicles: Fixed validation for the filter[vehicle_id] parameter so inputs with special characters are handled safely and no longer trigger HTTP 500 errors.
  • GET /vehicles/{registration}/odometer: Enforces the YYYY-MM-DD HH:MM:SS timestamp format and returns a clear 422 error for invalid dates, preventing confusing failures when querying odometer history.