C1-2026 is out! 🚀
1768203000000

What’s included this time around? What’s new? Check it out!
Unfamiliar Driver Detection
BIOMETRIC NOTICE:When Driver Change Detection is enabled, the Lytx solution collects, uses, stores and discloses Biometric Information for the purpose of providing and improving the Driver Change Detection functionality. For more information, see Lytx’s Biometric Information Privacy Policy available at https://www.lytx.com/legal/biometric-information-privacy-policy . As a reseller or user of the Lytx solution, you have agreed to comply with any applicable data protection and privacy laws, such as laws requiring notice and consent. Prior to enabling this feature, Lytx requires execution of an acknowledgment of your commitment to comply with any applicable data protection and privacy laws, such as laws requiring notice and consent for the processing of biometric information by service providers.
This feature enhances fleet security by automatically identifying and alerting administrators when a driver who is not recognized in the fleet's approved list drives a vehicle. The following table outlines the Driver Album Workflow, mapping specific API endpoints and automated services to the lifecycle of image collection, driver classification, and data retention.
Driver Album Workflow
Workflow | Endpoint | Endpoint Function |
Feature Activation | POST /organization-album/{orgId}/album/ config | Enable/Disable: Sets the global toggle to start or stop automatic image collection. |
Status Verification | GET /organization-album/{orgId}/album/config | Retrieve Config: Checks if the album feature is currently active for the organization. |
Image Collection | Automated Background Process | Daily Sync: Captures trip images and populates the pendingReview queue once every 24 hours. |
Driver Review | GET /organization-album/{orgId}/album | Retrieve Images: Fetches the list of driver images to be reviewed by the fleet manager. |
Driver Classification | POST /organization-album/{orgId}/album/ status | Set Recognition: Tags a specific image as Familiar (authorized) or Unfamiliar (unauthorized). |
Data Maintenance | System-Level Maintenance | Auto-Deletion: Removes images after one year of inactivity or immediately upon album deletion. |
Optimized API Performance: Optional Telemetry Control for AI-12 Devices
We have enhanced the getOrganizationDevices API by adding a new optional query parameter, getTelemetryData, to the GET /organizations/{orgId}/devices endpoint. This update gives developers greater control over payload size and processing speed by allowing you to include or exclude real-time telemetry—specifically latitude, longitude, altitude, and speed—for AI-12 devices. By setting this parameter to FALSE, you can significantly reduce data overhead when only core device information is required, while the default TRUE setting ensures backward compatibility with your existing workflows.
Note: This optimization is specific to the AI-12; AI-14 devices will continue to provide high-frequency updates (every 5 seconds) regardless of this parameter setting.
API Stability Enhancement: Resolved 500 Errors for Large Organizations
We have implemented a critical fix for the getOrganizationDevices API (GET /v2/ organizations/{orgId}/devices) to ensure stability when retrieving data for large -scale organizations. Previously, requests for organizations with a high volume of devices could trigger a 500 Internal Server Error due to data processing timeouts. This update optimizes the internal handling of large datasets, designed to improve response reliability and seamless integration for our enterprise-level partners.
Documentation Change
We added these notes to this Dev Portal article. https://developer.surfsight.net/ developerportal/webhooks/#webhooks
• Note: The speed field in event notifications is reported in kilometers per hour (km/h)
• Note: The speed field in GPS is reported in meters per second (m/s).
Read more about this release in the Developer portal changelog.
This notice was delivered to Lytx partners.
For more information, speak with us here.
Did you like this update?
![]()
![]()
![]()
Leave your name and email so that we can reply to you (both fields are optional):
