1. Create Drivers and Update Drivers APIs - (Validate the  “organizationId ” parameter) 

   • When creating a new driver persona in the Organization,  (POST/drivers and PATCH/drivers), we will add a validation that the organizationId exists and belongs to the partner who is performing the operation.  This will allow you to only create a driver persona who is in your organization.   

2. Virtual event - Validate Parameters 

   • We will be implementing more stringent parameter validation on the virtual-event endpoint. By ensuring that all input data adheres to pre-defined criteria, we will only create events with valid parameters. You will receive an error message when attempting to enter invalid parameters.   

3. Create/Update organization - (post/organizations): Change the default for isOrganizationProfileEnabled to FALSE 

   • At the present time, newly created organizations are automatically enabled for the “Organization Profile” feature.  

     To provide greater user autonomy, we will change the default setting of isOrganizationProfileEnabled to FALSE. This will allow users to opt-in to the Organization Profile feature if they choose. 

These changes will be implemented in the release scheduled for January 12, 2025. 

We understand that these changes may cause some disruption to your workflow. We apologize for any inconvenience you might experience. If you have any questions or concerns, please reach out to your Technical Account Manager. 

Thank you for your understanding and continued support. 

1. Due to a more stringent validation process, the viewer role, which can be assigned to users in the Partner Portal, will only have access to limited functions across all platforms.  

   • Requests to update, edit, create, or delete information under accessType: viewer, will not be allowed, and will return a 403 error.  

   Please note that API endpoints that require a partner token are not affected by these changes. 

   Furthermore, changes made by a user with viewer access are recorded in the audit log for review. 

2. The events accOff and accOn are available as text only, without snapshot or video. This is configured as dataType parameter none. However, previously the dataType parameter could be configured as a media event: snapshot or video.  

   • Due to a more stringent validation process, these events will not accept configurations as snapshot or video.  

   • For devices that have this event configured as a media event, the configuration will be changed to text only. 

   This change impacts the PUT /devices/event-config, PUT /devices/{imei}/event-config, and POST /organizations/{orgId}/event-settings API calls. 

   This only affects integrations associated with the AI-12 dashcam. 

These changes will be implemented in the release scheduled for August 25. 

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. 

Resolution notes:

We suspect the issue reported is related to Geotab local plugin’s or/and our cloud’s cache. We’ve invalidated our cache at AWS CloudFront. Our recommendation is to use the browser’s incognito mode with Geotab's plugin, so we will eliminate the local cache too.

Thank you for your patience.

This notice was delivered to <employees only>.

 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. 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. 

1. The lens field of view has been corrected to reflect the accurate horizontal field of view.

2. We have switched to a new SD card, addressing the previous failure.

3. The certifications have been updated to ensure the latest compliance standards.

4. The power consumption has been retested by the Engineering team, leading to a recommended change in the specification.

5. The operating temperature has also been retested by Engineering, resulting in an updated recommendation.

6. As our teams have not tested the AI-12 dash cam with SD cards larger than 128 GB, therefore we have decided to omit any claims regarding support for higher capacities.

7. Product and Product Marketing have aligned on the messaging regarding stand-by mode and modified the previous one.

8. There have been updates to the cables used with the AI-12.

9. The resolution of the in-cab lens of the AI-12 has been clarified to be up to 720.

The updated spec sheet can be found on Seismic (external link). Please reach out to the Product or the Product Marketing teams if you have any additional questions.

Thank you,
The Product Marketing Team

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.