A new randomized Wifi password is automatically generated when a hotspot is enabled for the first time on a device. A new API call,​​ POST /devices/wifi-password​​ has been created to retrieve this password. Only ​partners​ are able to use this call to retrieve the new password.
​​Device ​​and ​event ​​configuration changes made through the Surfsight Portal,​ and device billings status changes initiated in the Partner Portal are now available in the audit log​​.
And more!!
Read all about this release’s new features, enhancements, and the bugs we fixed in the Developer portal changelog.
This notice was delivered to Lytx partners.
For more information, speak with us here.
A new randomized Wifi password is automatically generated when a hotspot is enabled for the first time on a device. A new API call,​​ POST /devices/wifi-password​​ has been created to retrieve this password. Only ​partners​ are able to use this call to retrieve the new password.
​​Device ​​and ​event ​​configuration changes made through the Surfsight Portal,​ and device billings status changes initiated in the Partner Portal are now available in the audit log​​.
And more!!
Read all about this release’s new features, enhancements, and the bugs we fixed in the Developer portal changelog.
This notice was delivered to Lytx partners.
For more information, speak with us here.
The latest firmware update, 3.12.108, for the AI-12 dash cam is now Generally Available (GA).
What’s included:
Auxiliary camera connectivity and recording enhancements
Improved recording stability of the dash cam during high-impact events
General fixes and improvements
Availability:
This update is rolling out automatically to all connected devices. Most devices which were previously updated to the limited release version 3.12.105 have been updated to the new 3.12.108 version.
Read more about 3.12.108 firmware version enhancements and bug fixes in the knowledge base  or  the Developer Portal changelog. 
For more information, please contact your Partner Success Manager or Technical Account Manager.
Sincerely,
Lytx Surfsight Team
This notice was delivered to Lytx partners.
For more information, speak with us here
The latest firmware update, 3.12.108, for the AI-12 dash cam is now Generally Available (GA).
What’s included:
Auxiliary camera connectivity and recording enhancements
Improved recording stability of the dash cam during high-impact events
General fixes and improvements
Availability:
This update is rolling out automatically to all connected devices. Most devices which were previously updated to the limited release version 3.12.105 have been updated to the new 3.12.108 version.
Read more about 3.12.108 firmware version enhancements and bug fixes in the knowledge base  or  the Developer Portal changelog. 
For more information, please contact your Partner Success Manager or Technical Account Manager.
Sincerely,
Lytx Surfsight Team
This notice was delivered to Lytx partners.
For more information, speak with us here
Two upcoming changes to the Surfsight API may impact your use of the service.
1. The DELETE/organization/{orgId} API call will change to DELETE/organizations/{orgId} to be consistent with other Organizations endpoints.
2. The event type activated is invalid and will no longer be accepted in the following API calls: PUT/devices/{imei}/event-config, PUT/devices/event-config, POST/organizations/{orgId}/event-settings, and POST/organizations/{orgId}/events. Using the event type activated will return an error message. The correct event type to use is deviceActivation.
​​Partners​ can set and retrieve device billing status with new API endpoints, and subscribe to a new system message webhook, ​deviceBillingStatusChange​​, for notification of a change to a ​device​​'s billing status.
And more!
Read all about this release’s new features, enhancements, and the bugs we fixed in the Developer portal changelog.
This notice was delivered to Lytx partners.
For more information, speak with us here.
Two upcoming changes to the Surfsight API may impact your use of the service.
1. The DELETE/organization/{orgId} API call will change to DELETE/organizations/{orgId} to be consistent with other Organizations endpoints.
2. The event type activated is invalid and will no longer be accepted in the following API calls: PUT/devices/{imei}/event-config, PUT/devices/event-config, POST/organizations/{orgId}/event-settings, and POST/organizations/{orgId}/events. Using the event type activated will return an error message. The correct event type to use is deviceActivation.
​​Partners​ can set and retrieve device billing status with new API endpoints, and subscribe to a new system message webhook, ​deviceBillingStatusChange​​, for notification of a change to a ​device​​'s billing status.
And more!
Read all about this release’s new features, enhancements, and the bugs we fixed in the Developer portal changelog.
This notice was delivered to Lytx partners.
For more information, speak with us here.
1. A JWT token is now required for both setting purge days and updating purge days in the PATCH /organizations/orgID API call. This is available only to users with partner-level permissions.
2. The same PIN number cannot be assigned to both a driver and an admin PIN in an organization. Until now trying to configure the same PIN number was rejected and a 200 code was returned. Now, if the same PIN number is assigned to both a driver and an admin PIN, the operation fails, and an error code is returned. This applies whether the request to assign the same number is made in one or multiple API calls using the following API endpoints:
PUT /devices/{imei}/device-config
PUT /devices/device-config
POST /organizations/{orgId}/device-settings
These changes will be implemented in the release scheduled for May 26.
We understand that these changes may cause some disruption to your workflow, and we apologize for any inconvenience. If you have any questions or concerns, please reach out to your Technical Account Manager.
Thank you for your understanding and continued support.
]]>1. A JWT token is now required for both setting purge days and updating purge days in the PATCH /organizations/orgID API call. This is available only to users with partner-level permissions.
2. The same PIN number cannot be assigned to both a driver and an admin PIN in an organization. Until now trying to configure the same PIN number was rejected and a 200 code was returned. Now, if the same PIN number is assigned to both a driver and an admin PIN, the operation fails, and an error code is returned. This applies whether the request to assign the same number is made in one or multiple API calls using the following API endpoints:
PUT /devices/{imei}/device-config
PUT /devices/device-config
POST /organizations/{orgId}/device-settings
These changes will be implemented in the release scheduled for May 26.
We understand that these changes may cause some disruption to your workflow, and we apologize for any inconvenience. If you have any questions or concerns, please reach out to your Technical Account Manager.
Thank you for your understanding and continued support.
]]>The API call ​DELETE /organizations/{orgId}​ was added to the ​Developer Portal​ because the API call ​DELETE /organization/{orgId}​​, is being deprecated. The ​DELETE /organization/{orgId}​ will be removed with the deployment on March 4, 2024. Users should use the ​DELETE /organizations/{orgId}​​ API call to avoid problems with their integration.
Auxiliary camera telemetry information has been added to the ​GET /devices/{imei}/telemetry​ API response in the new ​auxCameras​ parameter. Information is retrieved for all connected ​auxiliary camera​​s.
When requesting organization webhooks with the ​GET /organizations/{orgId}/webhooks​ API, ​Surfsight partners​ can use the new optional parameter,​ imei​​, to filter by device IMEI number and retrieve only the webhooks for that device.
and more!
Read all about this release’s new features, enhancements, and the bugs we fixed in the Developer portal changelog.
This notice was delivered to Lytx partners.
For more information, speak with us here.
The API call ​DELETE /organizations/{orgId}​ was added to the ​Developer Portal​ because the API call ​DELETE /organization/{orgId}​​, is being deprecated. The ​DELETE /organization/{orgId}​ will be removed with the deployment on March 4, 2024. Users should use the ​DELETE /organizations/{orgId}​​ API call to avoid problems with their integration.
Auxiliary camera telemetry information has been added to the ​GET /devices/{imei}/telemetry​ API response in the new ​auxCameras​ parameter. Information is retrieved for all connected ​auxiliary camera​​s.
When requesting organization webhooks with the ​GET /organizations/{orgId}/webhooks​ API, ​Surfsight partners​ can use the new optional parameter,​ imei​​, to filter by device IMEI number and retrieve only the webhooks for that device.
and more!
Read all about this release’s new features, enhancements, and the bugs we fixed in the Developer portal changelog.
This notice was delivered to Lytx partners.
For more information, speak with us here.
When retrieving media files from either the ​GET/devices/{imei}/event-file-link​ or ​GET/devices/{imei}/cameras/{cameraId}/snapshot​ API calls, users can now request all the media files, or multiple media files, associated with an event with one API call.
Partners can opt-in to receive additional webhook notifications for alarm status when they enable the ​subscribeForAlarmUpdates​ parameter in the following calls: ​POST/organizations/{orgId}/webhook-settings​​, ​POST/organizations/{orgId}/webhooks​​, and ​PUT/organizations/{orgId}/webhooks​​. By default, partners​ are opted out and continue to receive webhook notifications for alarm creation only. By opting in, partners​​ receive additional alarm webhook notifications when alarms are closed.
When retrieving information from the ​GET/partners/operational-statistics​ call, partners​ can now retrieve device counts for the parameters ​pendingActivation​ and ​locked​​, in addition to ​activated​ and ​deactivated​ currently available. The count for ​deactivated ​​devices is a combination of the devices that are pending activation and locked.
And more!
Read all about this release’s new features, enhancements, and the bugs we fixed in the Developer portal changelog.
This notice was delivered to Lytx partners.
For more information, speak with us here.
When retrieving media files from either the ​GET/devices/{imei}/event-file-link​ or ​GET/devices/{imei}/cameras/{cameraId}/snapshot​ API calls, users can now request all the media files, or multiple media files, associated with an event with one API call.
Partners can opt-in to receive additional webhook notifications for alarm status when they enable the ​subscribeForAlarmUpdates​ parameter in the following calls: ​POST/organizations/{orgId}/webhook-settings​​, ​POST/organizations/{orgId}/webhooks​​, and ​PUT/organizations/{orgId}/webhooks​​. By default, partners​ are opted out and continue to receive webhook notifications for alarm creation only. By opting in, partners​​ receive additional alarm webhook notifications when alarms are closed.
When retrieving information from the ​GET/partners/operational-statistics​ call, partners​ can now retrieve device counts for the parameters ​pendingActivation​ and ​locked​​, in addition to ​activated​ and ​deactivated​ currently available. The count for ​deactivated ​​devices is a combination of the devices that are pending activation and locked.
And more!
Read all about this release’s new features, enhancements, and the bugs we fixed in the Developer portal changelog.
This notice was delivered to Lytx partners.
For more information, speak with us here.
Lytx Conceal Service blurs license plates, as well as faces of drivers, passengers, and passersby on event media files that are stored in the cloud. This service is available through API to reseller partners connected to the EU cloud.
New ​POST /devices/{imei}/alarm-simulator​​ API call allows users to create simulated alarms and thoroughly assess and optimize their integration, ensuring accurate detection and response to actual alarms.
Partners can choose to opt out of the ​mediaAvailable​​ webhook notification. This removes the ​mediaAvailable​ parameter from the ​Event ​​webhook notification, and produces only one webhook per event.
And more!
Read all about this release’s new features, enhancements, and the bugs we fixed in the Developer portal changelog.
This notice was delivered to Lytx partners.
For more information, speak with us here.
Lytx Conceal Service blurs license plates, as well as faces of drivers, passengers, and passersby on event media files that are stored in the cloud. This service is available through API to reseller partners connected to the EU cloud.
New ​POST /devices/{imei}/alarm-simulator​​ API call allows users to create simulated alarms and thoroughly assess and optimize their integration, ensuring accurate detection and response to actual alarms.
Partners can choose to opt out of the ​mediaAvailable​​ webhook notification. This removes the ​mediaAvailable​ parameter from the ​Event ​​webhook notification, and produces only one webhook per event.
And more!
Read all about this release’s new features, enhancements, and the bugs we fixed in the Developer portal changelog.
This notice was delivered to Lytx partners.
For more information, speak with us here.
1. The DELETE/organization/{orgId} API call will change to DELETE/organizations/{orgId} to be consistent with other Organizations endpoints.
2. The event type activated is invalid and will no longer be accepted in the following API calls: PUT/devices/{imei}/event-config, PUT/devices/event-config, POST/organizations/{orgId}/event-settings, and POST/organizations/{orgId}/events. Using the event type activated will return an error message. The correct event type to use is deviceActivation.
These changes will be implemented in the release scheduled for March 3, 2024.
We understand that these changes may cause some disruption to your workflow, and we apologize for any inconvenience. If you have any questions or concerns, please reach out to your Technical Account Manager.
Thank you for your understanding and continued support.
]]>1. The DELETE/organization/{orgId} API call will change to DELETE/organizations/{orgId} to be consistent with other Organizations endpoints.
2. The event type activated is invalid and will no longer be accepted in the following API calls: PUT/devices/{imei}/event-config, PUT/devices/event-config, POST/organizations/{orgId}/event-settings, and POST/organizations/{orgId}/events. Using the event type activated will return an error message. The correct event type to use is deviceActivation.
These changes will be implemented in the release scheduled for March 3, 2024.
We understand that these changes may cause some disruption to your workflow, and we apologize for any inconvenience. If you have any questions or concerns, please reach out to your Technical Account Manager.
Thank you for your understanding and continued support.
]]>Two upcoming changes to the Surfsight API may impact your use of the service.
Specific events only allow text for data type, the dataType parameter ‘none’. Until now trying to configure these events to snapshot or video was ignored and did not return an error. From now on, the wrong dataType will result in an error code 400 and message.
If the ​GET /devices/{imei}/cameras​​ API call was sent while the camera was offline, an error code 500 was returned with an internal server error message. Now if the camera is offline, the 417 error code will return with a message that the device is offline.
And more!
Read all about this release’s new features, enhancements, and the bugs we fixed in the Developer portal changelog.
This notice was delivered to Lytx partners.
For more information, speak with us here.
Two upcoming changes to the Surfsight API may impact your use of the service.
Specific events only allow text for data type, the dataType parameter ‘none’. Until now trying to configure these events to snapshot or video was ignored and did not return an error. From now on, the wrong dataType will result in an error code 400 and message.
If the ​GET /devices/{imei}/cameras​​ API call was sent while the camera was offline, an error code 500 was returned with an internal server error message. Now if the camera is offline, the 417 error code will return with a message that the device is offline.
And more!
Read all about this release’s new features, enhancements, and the bugs we fixed in the Developer portal changelog.
This notice was delivered to Lytx partners.
For more information, speak with us here.
The mediaFileAvailability parameter has been added to responses in​ GET/devices/{imei}/events​​, ​GET/devices/{imei}/events/{eventId}​​, and ​POST/organizations/{orgId}/events​ API calls to determine if media is available.
Virtual events can now be created without media using the new ​mediaType​ option, ​none​, in the ​POST/devices/{imei}/virtual-event​ API call.
Read all about this release’s new features, enhancements, and the bugs we fixed in the Developer portal changelog.
This notice was delivered to Lytx partners.
For more information, speak with us here.
The mediaFileAvailability parameter has been added to responses in​ GET/devices/{imei}/events​​, ​GET/devices/{imei}/events/{eventId}​​, and ​POST/organizations/{orgId}/events​ API calls to determine if media is available.
Virtual events can now be created without media using the new ​mediaType​ option, ​none​, in the ​POST/devices/{imei}/virtual-event​ API call.
Read all about this release’s new features, enhancements, and the bugs we fixed in the Developer portal changelog.
This notice was delivered to Lytx partners.
For more information, speak with us here.