Reference · built on requestConnectorFleet & telematics

Lytx

Video safety events, inspections, hours of service, GPS, and trips from Lytx DriveCam and Lytx+ fleets.

Request accessPricing ↗

About

Lytx runs the DriveCam video safety program and a telematics line it calls Lytx+ with Geotab GO9 devices. Its developer portal publishes REST APIs in OpenAPI form under Admin, Safety, Fleet Tracking, and Fleet Telematics: devices, drivers, vehicles, groups, safety events, video, DVIR, ECM, geofences, GPS, HOS, and trips. Calls go to https://api.lytx.com with a bearer token.

Through Fibric, an operator reads safety events, inspection defects, and hours of service, then proposes a video clip request, a geofence, or a planned driver dispatch schedule for your approval. Each approved change is applied once and leaves a receipt.

This is a reference listing. It documents what Fibric would read from Lytx and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Safety events with triggers, behaviors, statuses, and dynamic risks through GET /events and GET /eventsWithMetadata in the Safety API
  • Event video and snapshots through the Video API: vehicle timelines, event view media, and device view snapshots
  • Driver-vehicle inspection reports, inspection lists, and inspection schedules through GET /v1/dvir
  • HOS logs for all users or one user through GET /v1/hos
  • GPS points, trips, and geofence activations through GET /v1/gps, GET /v1/trips, and GET /v1/geofence/activations
  • Actual driver-to-vehicle assignments through GET /v1/driver-assignments
  • DTC and GPS webhooks posted every 5 seconds or every 500 records, set up with Lytx Technical Support

Proposed actions

  • Target capability: propose a video clip or tag request for a vehicle and time window through POST /events in the Video API
  • Target capability: propose a new or updated geofence through POST /v1/geofences and PUT /v1/geofences/{geofenceIdentifier}
  • Target capability: propose a planned driver-to-vehicle dispatch schedule through POST /v1/driver-assignments/dispatch
  • Target capability: propose a vehicle record change through PATCH /{id} in the Vehicles API

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Triage a risky driving event

    New safety events arrive with trigger, behavior, and status. The operator groups them by driver and vehicle, pulls the event file, and proposes which ones a safety manager reviews first.

    With Near-Miss Triage

  • Close inspection defects before the next trip

    DVIRs list defects found and defects resolved per asset. When a schedule shows a missed or failed inspection, the operator proposes a hold and a repair ticket for approval.

    With Inspection Gap

  • Match trips to drivers

    Driver assignments show who actually drove. The operator compares them with trips and proposes a corrected assignment or a dispatch schedule where a vehicle moved with no driver on record.

    With Unassigned Driving

  • Watch hours of service

    HOS logs come back per user. The operator flags drivers close to their limit and proposes a reassignment before dispatch.

    With Driver Hours

Requirements

  • A Lytx account with a username and password; SSO or MFA accounts must register a public key through the Advanced flow
  • A user with Full Access at the highest group level; Groups API write endpoints also need the Group Manager role
  • A Fleet Tracking subscription for GPS and ECM data
  • An HTTPS endpoint, contact email, and credentials handed to Lytx Technical Support for DTC or GPS webhooks
Authentication
A bearer token from POST https://login.lytx.com/api/auth/user using a Lytx account username and password, valid for 1 hour; accounts with SSO or MFA use the Advanced registration flow with an RS256-signed JWT.

Limits

  • Webhooks cover only DTC and GPS; safety events are polled, not pushed
  • Failed webhook deliveries are retried for up to 24 hours, then delivery pauses
  • Token Authentication does not work for companies with SSO or MFA configured
  • Lytx publishes no rate limit figures in its developer portal, and the Legacy APIs use an obsolete X-APIKey scheme

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Lytx ↗

Questions and answers

Does Lytx push safety events by webhook?
No. The documented webhooks carry DTC and GPS data only, posted every 5 seconds or every 500 records, and are set up with Lytx Technical Support. Safety events are read from the Safety API, which lists events, triggers, behaviors, statuses, and event files.
How does authentication work?
Token Authentication posts a username and password to https://login.lytx.com/api/auth/user and returns a bearer token valid for 1 hour. Companies with SSO or MFA use Advanced authentication: a Full Access user registers a public key through the Postman collection and signs an RS256 JWT.
What is the difference between DriveCam and GO9 endpoints?
DriveCam endpoints sit under /v0 and /v1 and cover the video safety program. Lytx+ endpoints for Geotab GO9 devices sit under /plus/v1, such as /plus/v1/faultdata and /plus/v1/zones, and carry the Plus suffix in the portal.
Ask about Lytx

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Lytx through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy