urn:noticeable:projects:noRULxACpF77fVJjBD9eDevelopers Updatesdeveloper.surfsight.net2024-08-22T11:45:54.937ZCopyright © DevelopersNoticeable#023048urn:noticeable:publications:N2gPxp579Dta7XmYxLms2024-08-22T12:08:00Z2024-08-22T11:45:54.937ZImportant notice: changes to the Surfsight APIUpcoming changes to the Surfsight® API may impact the use of your service.
We will be changing the GPS data webhook "ID" field type from numeric to alphanumeric.
After the change, the GPS coordinate data “ID” parameter type will be...<p><span style="color: windowtext;">Upcoming changes to the Surfsight® API may impact the use of your service. </span></p><ul><li><p><span style="color: windowtext;">We will be changing the GPS data webhook "ID" field type from numeric to alphanumeric. </span></p></li></ul><p><span style="color: windowtext;">After the change, the </span><span style="color: rgb(23, 43, 77);">GPS coordinate data “ID” parameter type will be expressed in alphanumeric format. If your service does not accept letters in the GPS data webhook "ID" field type, please make the necessary adjustments. </span></p><ul><li><p><span style="color: windowtext;">The patch update device webhooks will be changed to full patch behavior. </span></p></li></ul><p><span style="color: windowtext;"> You will be able to </span><span style="color: rgb(23, 43, 77);">update webhooks settings without deleting the current settings. When making a new API call from </span><em><span style="color: rgb(23, 43, 77);">PATCH/organizations/{orgId}/webhook-settings</span></em><span style="color: rgb(23, 43, 77);">, the call will no longer override the entire object in the configuration. <br></span><span style="color: windowtext;"> <br></span><span style="color: rgb(23, 43, 77);">With this change, the new call will be combined with the existing object. The configuration will allow up to 3 URLs. If the combined configuration contains more than 3 unique URLs, it will return an error. </span></p><ul><li><p><span style="color: rgb(23, 43, 77);"> </span><span style="color: windowtext;">API GET device event enhancements </span></p></li></ul><p><span style="color: rgb(23, 43, 77);">In order to prevent an excessive load on the database, we will be enforcing the </span><em><span style="color: rgb(23, 43, 77);">start</span></em><span style="color: rgb(23, 43, 77);"> and </span><em><span style="color: rgb(23, 43, 77);">end</span></em><span style="color: rgb(23, 43, 77);"> query string parameters on the </span><em><span style="color: rgb(0, 0, 0);">GET /devices/{imei}/events</span></em><span style="color: rgb(0, 0, 0);"> endpoint to include up to 31 days of activity. This will result in a significant reduction in the number of 500 error codes. </span></p><p><span style="color: rgb(0, 0, 0);">If more than 31 days of activity are requested, you will receive a </span><span style="color: rgb(23, 43, 77);">return status code 400 “bad request”. </span></p><ul><li><p><span style="color: rgb(66, 66, 66);"> </span><span style="color: windowtext;">API POST organization events enhancements </span></p></li></ul><p><span style="color: rgb(23, 43, 77);">In order to prevent an excessive load on the database, we will be enforcing the </span><em><span style="color: rgb(23, 43, 77);">start</span></em><span style="color: rgb(23, 43, 77);"> and </span><em><span style="color: rgb(23, 43, 77);">end</span></em><span style="color: rgb(23, 43, 77);"> query string parameters on the </span><em><span style="color: rgb(23, 43, 77);">POST</span><span style="color: rgb(0, 0, 0);"> </span><span style="color: rgb(23, 43, 77);">/organizations/{orgId}/events </span></em><span style="color: rgb(23, 43, 77);">endpoint to </span><span style="color: rgb(0, 0, 0);">include up to 31 days of activity. This will result in a significant reduction in the number of 500 error codes. <br></span><span style="color: rgb(23, 43, 77);"> </span></p><ul><li><p><em><span style="color: rgb(23, 43, 77);">POST</span><span style="color: windowtext;"> /</span></em><span style="color: windowtext;">organizations/{orgId}</span><em><span style="color: windowtext;">)/events </span></em><span style="color: windowtext;">will be set to </span><strong><span style="color: windowtext;">Mandatory</span></strong><span style="color: windowtext;">.</span><strong><span style="color: windowtext;"> </span></strong><span style="color: windowtext;"> </span></p></li></ul><ul><li><p><span style="color: windowtext;">The </span><em><span style="color: windowtext;">begin</span></em><span style="color: windowtext;"> and </span><em><span style="color: windowtext;">end</span></em><span style="color: windowtext;"> query string parameters must be set to a maximum of a 31- day time period. </span></p></li></ul><p><span style="color: rgb(0, 0, 0);">If more than 31 days of activity are requested, you will receive a </span><span style="color: rgb(23, 43, 77);">return status code 400 “bad request”. </span></p><p></p><p><span style="color: windowtext;">These changes will be implemented in the release scheduled for December 1, 2024. </span></p><p><span style="color: windowtext;">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. </span></p><p><span style="color: windowtext;">Thank you for your understanding and continued support. </span></p><p><span style="color: windowtext;"> </span></p>Ben Goldfarb[email protected]urn:noticeable:publications:Pzl3PYsYyYYnvE5B4XmC2024-06-06T08:45:00Z2024-06-06T08:31:06.524ZFirmware 3.12.206 is rolling out!Firmware Update 3.12.206 is rolling out.
The latest firmware update, 3.12.206, for the AI-12 dash cam is rolling out.
What’s included:
New NOM label in the Certification screen
An issue that caused repeated rebooting of the device was...<p><strong>Firmware Update 3.12.206 is rolling out.</strong></p><p><span style="color: black;">The latest firmware update, 3.12.206, for the AI-12 dash cam is rolling out.</span></p><p> <strong>What’s included</strong>:</p><ul><li><p><span style="color: black;">New NOM label in the Certification screen</span></p></li><li><p>An issue that caused repeated rebooting of the device was resolved in this update<span style="color: black;">.</span></p></li><li><p><span style="color: black;">Enhanced Wi-Fi security when connecting auxiliary cameras via hotspot</span></p></li></ul><p>The limited-release phase of the rollout started on June 3rd and will be gradually carried out throughout the next few weeks. The rollout is beginning with devices connected to the US cloud.</p><p>As we progress with the rollout, we will upgrade larger batches of devices. Devices will be randomly picked, including devices connected to the EU cloud. We expect to push 3.12.206 as GA to all connected devices by the end of June or early July.</p><p>The timing and pace are approximate and subject to change according to the deployment performance.</p><p>We value transparency and will notify you as the rollout progresses.</p><p><span style="color: black;">Read more about 3.12.206 firmware update enhancements and bug fixes in the </span><a href="https://kb.surfsight.net/hc/en-us/articles/13943793918108-3-12-206-June-2024?utm_source=noticeable&utm_campaign=developers.firmware-3-12-206-is-rolling-out&utm_content=publication+link&utm_id=noRULxACpF77fVJjBD9e.bKl2tQxTwT9mCkM7GlY7.Pzl3PYsYyYYnvE5B4XmC&utm_medium=newspage" rel="noopener nofollow" target="_blank">Knowledge base</a>,<span style="color: #414141;"> </span><span style="color: black;">or the </span><a href="https://developer.surfsight.net/developer-portal/changelog/changelog_firmware/?utm_source=noticeable&utm_campaign=developers.firmware-3-12-206-is-rolling-out&utm_content=publication+link&utm_id=noRULxACpF77fVJjBD9e.bKl2tQxTwT9mCkM7GlY7.Pzl3PYsYyYYnvE5B4XmC&utm_medium=newspage" rel="noopener nofollow" target="_blank">Developer Portal changelog</a><span style="color: #414141;">. </span></p><p><span style="color: black;">For more information, please contact your Partner Success Manager or Technical Account Manager.</span></p><p><strong>Sincerely,</strong> </p><p><strong>Lytx Surfsight Team</strong> </p><p></p><hr><p><em>This notice was delivered to Lytx partners.</em></p><p><em>For more information, speak with us <code><a href="mailto:[email protected]" rel="noopener nofollow" target="_blank"><span style="text-decoration: underline">here</span></a></code></em></p>Sharon Schnee[email protected]urn:noticeable:publications:CFLruK7vWmWtvrU3odFE2024-05-23T14:41:09.482Z2024-05-23T14:41:21.314ZImportant notice: changes to the Surfsight APITwo upcoming change to the Surfsight API may impact your use of the service.
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...<p>Two upcoming change to the Surfsight API may impact your use of the service. </p><ol><li><p><span style="color: windowtext;">Due to a more stringent validation process, the </span><strong><span style="color: windowtext;">viewer</span></strong><span style="color: windowtext;"> role, which can be assigned to users in the Partner Portal, will only have access to limited functions across all platforms. </span></p><ul><li><p><span style="color: windowtext;">Requests to update, edit, create, or delete information under </span><strong><span style="color: windowtext;">accessType:</span></strong><span style="color: windowtext;"> </span><strong><span style="color: windowtext;">viewer</span></strong><span style="color: windowtext;">, will not be allowed, and will return a 403 error. </span></p></li></ul><p><span style="color: windowtext;">Please note that API endpoints that require a partner token are not affected by these changes. </span></p><p><span style="color: windowtext;">Furthermore, changes made by a user with </span><strong><span style="color: windowtext;">viewer</span></strong><span style="color: windowtext;"> access are recorded in the audit log for review. </span></p><p></p></li><li><p><span style="color: windowtext;">The events </span><strong><span style="color: windowtext;">accOff</span></strong><span style="color: windowtext;"> and </span><strong><span style="color: windowtext;">accOn</span></strong><span style="color: windowtext;"> are available as text only, without snapshot or video</span><span style="color: rgb(66, 66, 66);">. This is configured as </span><strong><span style="color: rgb(66, 66, 66);">dataType</span></strong><span style="color: rgb(66, 66, 66);"> parameter </span><strong><span style="color: rgb(66, 66, 66);">none</span></strong><span style="color: rgb(66, 66, 66);">.</span> However, previously the <strong>dataType</strong> parameter could be configured as a media event: <strong>snapshot</strong> or <strong>video</strong>. </p><ul><li><p><span style="color: windowtext;">Due to a more stringent validation process, these events will not accept configurations as </span><strong><span style="color: windowtext;">snapshot</span></strong><span style="color: windowtext;"> or </span><strong><span style="color: windowtext;">video</span></strong><span style="color: windowtext;">. </span></p></li><li><p><span style="color: windowtext;">For devices that have this event configured as a media event, the configuration will be changed to text only. </span></p></li></ul><p><span style="color: rgb(65, 65, 65);">This change impacts the </span><strong><span style="color: rgb(65, 65, 65);">PUT /devices/event-config</span></strong><span style="color: rgb(65, 65, 65);">, </span><strong><span style="color: rgb(65, 65, 65);">PUT /devices/{imei}/event-config</span></strong><span style="color: rgb(65, 65, 65);">, and </span><strong><span style="color: rgb(65, 65, 65);">POST /organizations/{orgId}/event-settings</span></strong><span style="color: rgb(65, 65, 65);"> API calls. </span></p><p><span style="color: rgb(65, 65, 65);">This only affects integrations associated with the AI-12 dashcam. </span></p></li></ol><p>These changes will be implemented in the release scheduled for August 25. </p><p>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. </p><p>Thank you for your understanding and continued support.</p>Sharon Schnee[email protected]urn:noticeable:publications:4joCAJkMKzbHWg7djSyg2024-03-27T15:00:00Z2024-03-27T14:36:32.339ZFirmware Update 3.12.108 Now Available Firmware Update 3.12.108 Now Available
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...<p><strong><span style="color: rgb(0, 0, 0);">Firmware Update 3.12.108 Now Available</span></strong><span style="color: rgb(0, 0, 0);"> </span></p><p><span style="color: rgb(0, 0, 0);">The latest firmware update, 3.12.108, for the AI-12 dash cam is now Generally Available (GA). </span></p><p><span style="color: rgb(0, 0, 0);"> </span><strong><span style="color: windowtext;">What’s included</span></strong><span style="color: windowtext;">: </span></p><ul><li><p><span style="color: rgb(0, 0, 0);">Auxiliary camera connectivity and recording enhancements </span></p></li><li><p><span style="color: rgb(0, 0, 0);">Improved recording stability of the dash cam during high-impact events </span></p></li><li><p><span style="color: rgb(0, 0, 0);">General fixes and improvements </span></p></li></ul><p><span style="color: rgb(0, 0, 0);"> </span><strong><span style="color: rgb(0, 0, 0);">Availability: </span></strong><span style="color: rgb(0, 0, 0);"> </span></p><p><span style="color: rgb(0, 0, 0);">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. </span></p><p><span style="color: rgb(0, 0, 0);">Read more about 3.12.108 firmware version enhancements and bug fixes in the </span><a href="https://kb.surfsight.net/hc/en-us/articles/12850156081564-3-12-108-March-2024?utm_source=noticeable&utm_campaign=developers.firmware-update-3-12-108-now-available&utm_content=publication+link&utm_id=noRULxACpF77fVJjBD9e.bKl2tQxTwT9mCkM7GlY7.4joCAJkMKzbHWg7djSyg&utm_medium=newspage" rel="noreferrer noopener" target="_blank"><span style="color: rgb(0, 0, 255);"><span style="text-decoration: underline">knowledge base</span></span></a><span style="color: rgb(65, 65, 65);"> </span><span style="color: rgb(0, 0, 0);">or the </span><a href="https://developer.surfsight.net/developer-portal/changelog/changelog_firmware/?utm_source=noticeable&utm_campaign=developers.firmware-update-3-12-108-now-available&utm_content=publication+link&utm_id=noRULxACpF77fVJjBD9e.bKl2tQxTwT9mCkM7GlY7.4joCAJkMKzbHWg7djSyg&utm_medium=newspage" rel="noreferrer noopener" target="_blank"><span style="color: rgb(0, 0, 255);"><span style="text-decoration: underline">Developer Portal changelog</span></span></a><span style="color: rgb(65, 65, 65);">. </span></p><p><span style="color: rgb(0, 0, 0);"> For more information, please contact your Partner Success Manager or Technical Account Manager.</span></p><p></p><p><strong>Sincerely,</strong> </p><p><strong>Lytx Surfsight Team</strong> </p><p></p><hr><p><em>This notice was delivered to Lytx partners.</em></p><p><em>For more information, speak with us <code><a href="mailto:[email protected]" rel="noopener nofollow" target="_blank"><span style="text-decoration: underline">here</span></a></code></em></p>Sharon Schnee[email protected]urn:noticeable:publications:rF5Ic6PKGvJfreFwznNx2024-02-22T11:00:00Z2024-02-22T10:26:30.830ZImportant notice: changes to the Surfsight APITwo upcoming changes to the Surfsight API may impact your use of the service.
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...<p>Two upcoming changes to the Surfsight API may impact your use of the service. </p><p>1. A JWT token is now required for both setting purge days and updating purge days in the <strong>PATCH /organizations/orgID</strong> API call. This is available only to users with partner-level permissions.</p><p>2. The same PIN number cannot be assigned to both a driver and an admin PIN in an organization. <span style="color: #424242;">Until now trying to configure the same PIN number was rejected and a 200 code was returned. Now, i</span>f 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:</p><ul><li><p><strong>PUT /devices/{imei}/device-config</strong></p></li><li><p><strong>PUT /devices/device-config</strong></p></li><li><p><strong>POST /organizations/{orgId}/device-settings</strong></p></li></ul><p>These changes will be implemented in the release scheduled for May 26. </p><p>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. </p><p>Thank you for your understanding and continued support. </p>Sharon Schnee[email protected]urn:noticeable:publications:wV71zVqct286cxHDEQv52023-11-20T12:00:00Z2023-11-20T11:18:53.062ZImportant notice: changes to the Surfsight APITwo upcoming changes to the Surfisght 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. ...<p>Two upcoming changes to the Surfisght API may impact your use of the service. </p><p> 1. The <strong>DELETE/organization/{orgId}</strong> API call will change to <strong><span style="color: #172B4D;">DELETE/organizations/{orgId}</span></strong><span style="color: #172B4D;"> to be consistent with other </span><strong><span style="color: #172B4D;">Organizations</span></strong><span style="color: #172B4D;"> endpoints.</span></p><p><strong> </strong>2. The event type <strong>activated</strong> is invalid and will no longer be accepted in the following API calls: <strong>PUT/devices/{imei}/event-config</strong>, <strong>PUT/devices/event-config</strong>, <strong>POST/organizations/{orgId}/event-settings</strong>, and<strong> POST/organizations/{orgId}/events</strong>. Using the event type <strong>activated</strong> will return an error message. The correct event type to use is <strong>deviceActivation</strong>.</p><p>These changes will be implemented in the release scheduled for March 3, 2024. </p><p>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. </p><p>Thank you for your understanding and continued support. </p>Sharon Schnee[email protected]urn:noticeable:publications:bikSbkwUY6oGHGXU87hZ2023-08-17T10:30:00Z2023-08-20T08:15:19.992ZImportant notice: changes to the Surfsight APITwo upcoming changes to the Surfsight® API may impact your use of the service.
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...<p>Two upcoming changes to the Surfsight® API may impact your use of the service. </p><ol><li><p>Certain events can only accept <strong>none</strong> for the data type using the <strong>dataType</strong> parameter. Previously, attempting to set up these events with a snapshot or video type didn't trigger an error. However, moving forward, an incorrect <strong>dataType</strong> 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 <strong>PUT /devices/event-config</strong>, <strong>PUT /devices/{imei}/event-config</strong>, and <strong>POST /organizations/{orgId}/event-settings</strong> API calls:</p><ul><li><p><strong>accOff</strong></p></li><li><p><strong>accOn</strong></p></li><li><p><strong>geoFence</strong></p></li><li><p><strong>speedLimit</strong></p></li><li><p><strong>standbyEnter</strong></p></li><li><p><strong>standbyExit</strong></p></li></ul></li><li><p>Previously, when a <strong>GET</strong> request was made to <strong>/devices/{imei}/cameras</strong> 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.</p></li></ol><p>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.</p><p>These changes will be implemented in the release scheduled for November 12. </p><p>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. </p><p>Thank you for your understanding and continued support. </p>Sharon Schnee[email protected]urn:noticeable:publications:P2TUwjNNBRD8LYyhAZ1A2023-07-18T14:00:00Z2023-07-18T13:03:52.947Z3.12 Firmware is in rollout! 🚀 We are excited to share that the rollout of the 3.12 firmware version for the AI-12 dash cam has begun and is now in limited release. This firmware version includes new features to enrich your offerings including Driver ID, Passenger...<p>We are excited to share that the rollout of the 3.12 firmware version for the AI-12 dash cam has begun and is now in limited release. This firmware version includes new features to enrich your offerings including Driver ID, Passenger Unbelted event, as well as additional enhancements and bug fixes. </p><p> <br><strong>WHAT’S NEXT?</strong> </p><p><strong>JUL-SEP:</strong> The limited-release phase of the rollout started on July 11<sup>th</sup> and will be gradually carried out throughout the next few weeks. The rollout begins with devices connected to the US cloud. </p><p>As we progress with the rollout, we will upgrade larger batches of devices. Devices will be randomly picked, including devices connected to the EU cloud. We expect to push 3.12 as GA to all devices by the end of September. </p><p> All devices are configured to turn off any new features so as to not alter the experience of the end-user. </p><p><strong>JUL 26<sup>th</sup></strong> : A product release webinar and training will be held dedicated to the firmware's features and enhancements (<a href="https://lytx.zoom.us/webinar/register/WN_F8RPnB5RSEWaJcCeGUtA3g?utm_source=noticeable&utm_campaign=developers.3-12-firmware-is-in-rollout&utm_content=publication+link&utm_id=noRULxACpF77fVJjBD9e.bKl2tQxTwT9mCkM7GlY7.P2TUwjNNBRD8LYyhAZ1A&utm_medium=newspage#/registration" rel="noreferrer noopener" target="_blank"><span style="text-decoration: underline">register here</span></a>). </p><p>The timing and pace of the rollout are approximate and subject to change according to the deployment performance. </p><p>We value transparency and will notify you as the rollout progresses. </p><p>More information about the 3.12 firmware version can be found in the <a href="https://kb.surfsight.net/hc/en-us/articles/9639095164316-3-12-July-2023?utm_source=noticeable&utm_campaign=developers.3-12-firmware-is-in-rollout&utm_content=publication+link&utm_id=noRULxACpF77fVJjBD9e.bKl2tQxTwT9mCkM7GlY7.P2TUwjNNBRD8LYyhAZ1A&utm_medium=newspage#UUID-2b01af5c-ce54-60f6-eae4-9d165427914f_section-idm4550278072872033760562663824" rel="noopener nofollow" target="_blank">knowledge base</a> or <a href="https://developer.surfsight.net/developer-portal/changelog/changelog_firmware/?utm_source=noticeable&utm_campaign=developers.3-12-firmware-is-in-rollout&utm_content=publication+link&utm_id=noRULxACpF77fVJjBD9e.bKl2tQxTwT9mCkM7GlY7.P2TUwjNNBRD8LYyhAZ1A&utm_medium=newspage" rel="noopener nofollow" target="_blank">Developer Portal changelog</a>. </p><p> </p><p><strong>Sincerely,</strong> </p><p><strong>Lytx Surfsight Team</strong> </p><p></p><hr><p><em>This notice was delivered to Lytx partners.</em></p><p><em>For more information, speak with us <code><a href="mailto:[email protected]" rel="noopener nofollow" target="_blank"><span style="text-decoration: underline">here</span></a></code>.</em></p>Sharon Schnee[email protected]urn:noticeable:publications:odv75vBt6dcxpWMd3OVv2023-03-03T06:24:49.880Z2023-03-03T06:25:25.352ZUpcoming release announcementWe would like to inform you that the E3/4 sprint release scheduled for March 5th has been cancelled. This decision was made after careful consideration and we understand that this may cause some changes to your work plans. We apologize for...<p>We would like to inform you that the E3/4 sprint release scheduled for March 5th has been cancelled. This decision was made after careful consideration and we understand that this may cause some changes to your work plans. We apologize for any inconvenience.</p><p>For more information, please contact your Partner Success Manager.</p><p>Sincerely,</p><p>Surfsight Product Group</p>Rachel Gottesman[email protected]urn:noticeable:publications:Y1q5m2cKih7gPuyhMn7G2023-02-15T15:00:00Z2023-02-15T09:40:46.981ZImportant notice: changes to the Surfsight API An upcoming change to the Surfisght API may impact your use of the service.
The following parameters were previously optional and will now be required in the PUT /devices/{imei}/event-config, POST /organizations/{orgId}/event-settings,...<p>An upcoming change to the Surfisght API may impact your use of the service. </p><p>The following parameters were previously optional and <span style="text-decoration: underline">will now be required</span> in the <strong>PUT /devices/{imei}/event-config</strong>, <strong>POST /organizations/{orgId}/event-settings</strong>, and <strong>PUT devices/event-config</strong> API calls: </p><ul><li><p><strong>speedLimit</strong>,<strong> </strong>when configuring speedLimit events </p></li></ul><ul><li><p><strong>drivingDuration</strong>, when configuring possibleFatigue events </p></li><li><p><strong>headwayAlertDayThreshold</strong>,<strong> headwayAlertNightThreshold</strong>,<strong> </strong>and<strong> headwayAlertTime</strong>,<strong> </strong>when configuring tailgating events </p></li><li><p><strong>LaneWeavingTimes </strong>and<strong> laneWeavingDurationSeconds</strong>,<strong> </strong>when configuring laneWeaving events </p></li></ul><p>These changes will be implemented in the release scheduled for May 28<sup>th</sup>. </p><p>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. </p><p>Thank you for your understanding and continued support. </p>Rachel Gottesman[email protected]