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

Breaking Changes

The following breaking changes were announced on August 4th, 2025 and have been implemented.

Get Organization Devices' Endpoint (SUR-9254)

To improve performance and prevent timeouts, the Get Organization Devices endpoint now has a default limit on how many devices it returns. This means if your organization has more devices than the new limit, your API response will be partial, even if you do not set a limit yourself. If you need a complete list of devices for a large organization, you will need to implement pagination.

Affected endpoint:

• get/organizations/{orgId}/devices

Device Settings API Validation Changes (SUR-9257)

Our Device Settings APIs (Single, Bulk, and Org settings) now enforce new, stricter validations. This breaking change means that attempts to set or update device configurations with unexpected parameters or to apply AI-14 specific settings to AI-12 devices will result in a 400 Bad Request error. For requests targeting both supported and unsupported devices, the API will still return HTTP 200 OK for the overall request, but it will only apply changes to the devices that support the configuration.

Affected endpoints:

• put/devices/{imei}/device-config

• put/devices/device-config

• post/organizations/{orgId}/device settings

Virtual Event cameraId Validation (SUR-9204)

We made updates to the API used for creating virtual events, focusing on the cameraId field. Before the change, our "Create Virtual Event" API endpoint let you include cameraId values that are not actually supported by our system (for example, 42). Even though the API accepts these and returns a 200 success code, these events do not connect to real camera streams. We have implemented strict validation for the cameraId field. If you try to create a virtual event with an unsupported cameraId, the API will reject the request. You will receive a 400 status code and a specific error message explaining the issue. Valid cameraId values are 1, 2, or 51 and higher, corresponding to specific camera types, such as road-facing, in-cabin, or AUX.

Affected endpoint:

• post/devices/{imei}/virtual-event

Driver PIN Code Validation (SUR-9198)

We are now enforcing strict validation for the driverCode field. With this implementation, attempts to update a driver with a PIN code that does not meet the required 5-digit numeric format
will be rejected with a validation error.

Affected endpoint:

• Patch/driver

Audit Log API Offset Parameter (VIK-516)

We updated the "Retrieve organization audit logs" API. Previous to this update, an offset of 'n' mistakenly returned data beginning at position 'n-1'. With this change, an offset of 'n' will properly return data starting at position 'n'. If no offset is specified, it will default to '0' (all records), aligning with the behavior of our other APIs.

Affected endpoint:

• get/audit-logs

Stricter Validations for Event Settings APIs (SUR-9256)

We are now enforcing stricter validations for our Event settings APIs (Single, Bulk, and Org settings). After this change, these APIs will not accept unexpected parameters or configurations that are incompatible with specific device types (such as AI-12 vs. AI-14) or firmware versions. Invalid requests will result in an HTTP 400 Bad Request error, and your changes will not be saved. If your request targets both supported and unsupported devices, the API will still return HTTP 200 OK, but it will only apply changes to the devices that support the configuration.

Affected endpoints:

• put/devices/{imei}/event-config

• put/devices/event-config

• post/organizations/{orgId}/event-settings

Read more about this release in the Developer portal changelog.

This notice was delivered to Lytx partners.

For more information, speak with us here.