Version 1.1.29

Release Date: 2025-06-03

[AEMP Standard APIs]: Beta Release
- AEMP stands for the Association of Equipment Management Professionals, a trade association representing professionals who manage and maintain heavy equipment fleets in sectors such as construction, mining, and agriculture.
- The API follows the ISO 15143‑3 standard (commonly known as AEMP 2.0), which defines how OEMs expose telematics data through a standardized RESTful interface. This improves interoperability, simplifies integration with third-party systems, and reduces development overhead for mixed-brand fleets.
- This service is currently in beta. If you have feedback, please email fleet-api@cartrack.com.
[Vision AI / Videos APIs]: AI Events
- Improved access to AI event alerts and related video footage.
[Tachograph APIs]: Download Vehicle Tachograph Files
- A tachograph is a device used in commercial vehicles—especially in Europe—to record driving time, speed, and rest periods for regulatory compliance and driver safety monitoring.
- It is now possible to retrieve tachograph files through the Fleet API.

[Drivers]: New Property Added
- Introduced employee_number in driver data.
[Delivery Drivers]: Synchronization with Fleet Drivers
- Ensures consistent activation and deactivation statuses between delivery drivers and fleet client drivers.
[Alert Management]: Limit Handling
- Fixed issues with incorrect maximum alert limits and error codes during alert creation.
[Delivery Jobs]: Schedule Types
- Supports only schedule_type_id values 2 (Scheduled) and 3 (Unscheduled).
  - 2: Scheduled
  - 3: Unscheduled
- Requests using schedule_type_id value 1 (ASAP) will be converted to 2 (Scheduled), with scheduled_delivery_ts set to the request timestamp.

[Geofences API]: Filtering Issue
- Fixed incomplete visit data when the end time filter is omitted.
[Trips API]: Missing Trips
- Ensured unique trip identification and ordered data retrieval to resolve missing and duplicate trip records.
[AEMP API]: Initialization
- Fixed an issue where the required initialization of vehicle data on the first API call triggered unexpected behavior.