What’s included this time around? What’s new? Check it out!

• Audience-Filtered Device Health API

  • This feature enhances the Device Health API by integrating audience-based filtering logic from the Alarms-V2 service. The updated API will now return device health results tailored to specific audiences, which helps partners and users see only the data relevant to their roles and permissions. This change improves data security and relevance, streamlining the user experience and supporting compliance with data access policies.

• Prevent False Alarms from Intentional Auxiliary Camera Unpairing

  • Intentionally unpairing an auxiliary camera used to create a "Paired aux cam disconnected" alarm. The system now recognizes valid unpairing requests and will no longer trigger this alarm. This improves alert accuracy so that alarms are only generated for unexpected disconnections.

• Breaking Changes

  The following breaking changes were announced on May 17, 2025 and have been implemented.

  • AI-12/AI-14 Connection Error Response Update

    • We have changed our system to return a "417 Expectation Failed" status code instead of a "500 Internal Server Error" when connections between the tunnel and an AI-12/AI-14 device are lost due to a 30-second timeout. This change affects the following endpoints:

      • /devices/{imei}/cameras/{cameraId}/snapshot

      • /devices/{imei}/recording-ranges

  • Error Handling for partner-bulk-add-devices

    • We have added validations and specific error messages for device assignment failures. Now, when you try to add a device already belonging to the specified organization, we return a new error code (1007) with the message "Device already assigned to this organization." If the device is assigned elsewhere, we return the existing error code (1001) and message ("Device already assigned".)

  • IMEI Validation for Audit Logs

    • We have implemented IMEI validation. Before this implementation, an "Incorrect 200 OK" response was returned when attempting to retrieve audit logs with an invalid or non-existent IMEI. The system now returns a "404 Not Found" error with an informative message in these cases.
      

      Read all about this release’s new features and enhancements in the Developer portal changelog.

This notice was delivered to Lytx partners.

For more information, speak with us here.