1. Certain events can only accept none for the data type using the dataType parameter. Previously, attempting to set up these events with a snapshot or video type didn't trigger an error. However, moving forward, an incorrect dataType will trigger an error with a 400 code and the following message: "dataType should be equal to one of the allowed values." These changes impact the following events within the PUT /devices/event-config, PUT /devices/{imei}/event-config, and POST /organizations/{orgId}/event-settings API calls:

   • accOff

   • accOn

   • geoFence

   • speedLimit

   • standbyEnter

   • standbyExit

2. Previously, when a GET request was made to /devices/{imei}/cameras while the dash cam was offline, it resulted in an error with a 500 code along with an internal server error message. However, moving forward, if the dash cam is offline, a 417 error code will be returned, accompanied by a message indicating that the device is currently offline.

These updates to the Surfsight API aim to enhance error clarity and specificity, enabling you to swiftly identify and rectify issues, thus streamlining your integration process.

These changes will be implemented in the release scheduled for November 12. 

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 following parameters were previously optional and will now be required in the PUT /devices/{imei}/event-config, POST /organizations/{orgId}/event-settings, and PUT devices/event-config API calls: 

• speedLimit, when configuring speedLimit events 

• drivingDuration, when configuring possibleFatigue events 

• headwayAlertDayThreshold, headwayAlertNightThreshold, and headwayAlertTime, when configuring tailgating events 

• LaneWeavingTimes and laneWeavingDurationSeconds, when configuring laneWeaving events 

These changes will be implemented in the release scheduled for May 28^th. 

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 password parameter in the recordingEncryption object returned in our GET /organizations/{orgId}/default-settings API call will be removed. Integration partners who use the password value in their code will be affected. 

2. The period for which mobile provider data is returned in the GET /devices/{imei}/data-usage API call will be the current month instead of the last thirty days. The twilioFleet response object will be renamed mobileProvider. Additionally, some data that is currently included in the response object will be removed. The following parameters will still be included in the response: 

   • uniqueName

   • dataLimit

   • dataUsage.period

   • dataUsage.dataUpload

   • dataUsage.dataDownload

   • dataUsage.dataTotal

3. When a user attempts to create a virtual event with the POST /devices/{imei}/virtual-event API call for a dashcam to which they don’t have access, a 404 not found error will be returned regardless of the dashcam status. 

These changes will be implemented in the release scheduled for April 2^nd. 

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.