Two upcoming changes to the Surfsight® API may impact your use of the service. 

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.