C2-2026 is out! 🚀

New Features and Enhancements

OAuth Login

We’ve introduced OAuth 2.0 Client Credentials Grant support in the Surfsight platform, using Keycloak as the authorization server. Partner backend systems can now more securely obtain access tokens and call Surfsight public APIs using a standard, modern M2M authentication flow. This enables partners to more securely generate and manage ClientIDs and secrets through the Partner Portal.​

AI-12 Auto-Calibration Self-Serve

We’re making AI‑12 auto-calibration generally available as a fully self-serve capability through production Partner APIs(V2), eliminating the need for Surfsight/Lytx support to trigger internal APIs and enabling calibration at device, organization, or partner level. Auto-calibration is now decoupled from ADAS configuration, so running auto-calibration no longer modifies or triggers ADAS events and existing event settings remain unchanged. The APIs return clear success/failure responses and support configurable mute periods (when ADAS is already configured) to temporarily suppress ADAS events and alerts during calibration without altering configurations, improving both driver experience and large‑scale rollout workflows. Calibration status and type are surfaced in the Partner Portal, and lane weaving is automatically disabled after successful auto-calibration or recalibration via the portal to help prevent low accuracy‑ issues.​​​

Partners and customers gain full, production-grade control over calibration workflows for AI-12 devices on firmware 3.12+, improving scalability, reducing support and Technical Account Managers dependency, and increasing the reliability of ADAS deployments via V2 APIs and the Partner Portal.​

Auto calibration mute period V2 API streamlines tailgating event management. When a mute period is configured, events are automatically suppressed based on those settings. This mute configuration is only for tailgating events.

Fixes

Webhooks not sent for AI-12

This release fixes an issue where organization webhook settings were only applied to the first 1,500 devices, leaving additional devices without the correct callback URLs. Now, when you configure or update organization-level webhook settings using the POST or PATCH webhook settings APIs, those settings are applied to all devices in the organization, regardless of size. The enables events, GPS data, alarms, and system messages to be delivered consistently across your entire fleet, without manual rework. This is especially important for larger organizations, where missed webhooks can impact downstream integrations, alerting, and reporting. ​

The ‘Alarm Report’ contains more affected cameras than the Partner Portal ‘Device Alarms’ section

This release fixes an issue where Alarm report download could show more devices with alarms than appeared in the Device Alarms screen for the same organization. The Alarm report export is now aligned with the Device Alarms UI when you filter by organization, so the same devices/IMEIs and counts are shown in both places. You get consistent, trustworthy alarm data across UI and CSV exports. This reduces confusion when reconciling alarms, simplifies reporting, and helps you make faster, more confident operation decisions.

Menu element jumps to bottom and appears detached when opened for User or Sub-Partner

This release fixes an issue in the Partner Portal UI where the action menu for Users and Sub‑Partners sometimes appeared at the bottom of the window, instead of next to the selected row. Now, when you open the context menu for any User or Sub‑Partner:​

The menu opens anchored to the correct row, right next to the action you selected.​

The menu stays visually connected to the correct user or sub‑partner, even when you open multiple menus in sequence.​

This fix reduces the chance of selected actions on the wrong account due to a “floating” menu and makes it clear which user or sub‑partner you are managing, improving accuracy and confidence when performing actions like edits, resets, or role changes.

Breaking Changes

The following breaking changes were announced on March 1, 2026 and will be implemented on June 1, 2026.

Shift speed limit and geofence events to GPS Tracking in privacy settings

What's changing ​

We’ve updated how speedLimit and geofence events are categorized in privacy settings:​

Previously, these events were grouped under otherEvents.​

They are now grouped under gpsTracking​.

As part of this change:​

Enabling or disabling allEvents no longer affects speedLimit and geofence events.​

Enabling or disabling gpsTracking does control speedLimit and geofence events.​

Why it Matters ​

Your location-related controls are now more accurate and predictable: Speed Limit and Geofence events follow the GPS Tracking setting, as users expect. This makes it clearer for drivers and admins which privacy toggle impacts which event types, improving transparency and trust in how location data is handled.

Revamped V2 Alarms

What's changing ​

We’ve enhanced our Alarm Services to provide clearer, more reliable insight into device health across AI‑12 and AI‑14 device cameras.​ These updates are part of our broader Alarms Realignment initiative.​

As Part of this change:​

1. Realtime device health alarms for AI-12 and AI-14​
Alarm Services now raises alarms when key recording and device health issues occur, including:​

Device camera not recording.​

Device resets / frequent reboots.​

Recording unavailable or failing.​

Auxiliary camera pairing or recording issues (AI‑14).​

2. Improved alarm logic and consistency​

A standardized alarm hierarchy and creation logic makes it easier to understand what’s wrong and why an alarm was raised.

Alarms remain active until the underlying issue is resolved (for example, when an aux camera reconnects or resumes recording).

Historical occurrences are logged so you can see how often a device is impacted.​

3. Expanded coverage for AI‑14 auxiliary cameras​

For AI‑14 devices with aux cameras, Alarm Services can detect and raise alarms when:​

A paired auxiliary camera becomes disconnected from the device.

​A connected auxiliary camera is not recording as expected.​

4. Foundation for scalable, reliable alerting​

These changes are part of a phased rollout to deliver a scalable, high volume alarm system:​

Built to handle timely alarm creation via Kafka with production grade performance.

​Designed so partners can tailor alarm consumption and integrate into their own tools and workflows over time.​

Why it Matters: ​

Faster detection of device issues – alarms surface problems like non‑recording lenses or frequent resets quickly.​

Higher confidence in video coverage – especially for multi‑camera (AI‑14 + aux) installations.​

Clearer guidance – alarms are designed to be more actionable, with consistent behavior and improved visibility across portals and APIs.

Disable video overlay if user switches off GPS

What’s changing​

We’ve updated how GPS privacy settings interact with the video overlay (the location data shown on video).​

As part of this change: ​

When a user turns GPS OFF:​

The video overlay is now automatically disabled on the device, so location, time stamp, and speed are not uploaded with video events.​

When a user turns GPS back ON:​

The device restores the user’s previous video overlay setting (ON or OFF), instead of forcing a default.​

Why it matters​

Stronger privacy controls: If GPS is OFF, your videos will no longer contain location data via the overlay.​

Respects user preferences: When GPS is turned back ON, the system brings back the exact overlay choice the user had set previously, reducing surprises and extra configuration work.​

If you are changing GPS settings as part of your compliance policies, this behavior helps to ensure your video content and location policies stay aligned automatically.

GPS Cloud Control for Dynamic Adjust

What’s changing​

We’re updating how GPS is handled so devices stay location-aware for core system features while honoring your privacy settings.​

As Part of this change: ​

Device always location-aware​

The device still receives GPS data even if GPS tracking is turned off (device or Privacy mode) so geofence-based features (e.g., Dynamic Adjust) keep working.​

Stronger GPS privacy controls​

When GPS is disabled in Privacy mode:​

Location and speed are not stored on media or events.​

Location and speed are not returned by APIs, including:​

GET /devices/{imei}/gps​

Event data and any other GPS/speed fields.​

GPS‑dependent events are not created.​

Geofence behavior​

Surfsight system geofence in/out events are always created so Dynamic Adjust can work.​ These system geofence events:​

Are always written to the audit log.​

Are only exposed externally (API, webhooks) according to your privacy configuration.​

Configuration behavior​

speedLimit and geofence events are now controlled by gpsTracking, not by otherEvents.​

Privacy mode behavior is updated so GPS is still sent from the device when disabled but not saved and not exposed via APIs.​

Why it Matters:​

Integrations must not rely on GPS/speed data when GPS is disabled.​

Any workflows tied to geofence or speedLimit events via otherEvents must be updated to use gpsTracking.

Read about new features:

In the Knowledge Base

In the Partner portal

This notice was delivered to Lytx partners. This notice was delivered to Lytx partners. The terms "partner" or "partnership" refers to a collaborative relationship and does not imply a legal partnership or joint venture.