What’s included this time around? What’s new? Check it out!

• Improved Device Management with Default Organization Data Profiles

  • Partners currently require extra API calls to assign data profiles to new devices. This feature introduces a default organization data profile setting, automating the process and reducing API calls for more efficient device administration.

• Enhanced the Retrieve Organization Events API Endpoint

  • The Retrieve Organization Events API Endpoint now returns Beep Events. Beep Events are returned when specified in the request or when all event types are requested. The current functionality is maintained for other event types.

• Updated API Documentation for Organization Default Event Settings

  • The developer portal documentation for the POST / organizations/{orgId}/event-settings endpoint was updated to clarify its interaction with the "Organization Profile" setting. Previously, the documentation described updating default event settings, but now explicitly states that when the "Organization Profile" is enabled, this endpoint completely replaces the event settings on all devices within the organization with the provided values.

• Documented the pairing of auxiliary cameras via an API

  • In the Webhook article overview, we added a note informing partners that they can pair auxiliary cameras via an API to an AI-12.

• Flexible Driving Duration Settings

  • This update expands the valid range for drivingDuration in event settings (single, bulk, and organization defaults) to 0-20 hours, assisting with compliance and providing flexibility for users. Possible fatigue events can be created even when the driver begins the trip.

• Introduced Reusable Component Access Control with Scoped Tokens

  • A new /scoped-token API authenticates users via bearer token and generates a scoped JWT, limiting the access of content to specified entities (device, devices in a group, and all devices in an organization) for a duration of 24 hours. This token, included in the Authorization header of subsequent API calls, functions as a bearer token, and grants access only to APIs within the defined scope. This allows partners and sub-partners to restrict user access to reusable components like Event Media, Live Streaming, and Recording Timeline

• Improved Organization Creation documentation: Default Values

  • This implementation addresses the organization creation endpoint. When an organization is created, several organization parameters are assigned default values implicitly. We updated the API documentation with an explanation of these default values, so that integrators know what to expect when creating a new organization and which values will be assigned by default.

• Improved the Organization Update API documentation

  • The default values were removed from the Update Organization page on the Developer Portal. You will now have a better idea of what to expect when updating a new organization.

• Updated the isOrganizationProfileEnabled Endpoint

  • This update enhances the developer portal documentation for the

    isOrganizationProfileEnabled endpoint, clarifying its behavior within the "Update Organization" and "Update Default Event Settings" sections.

  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.