What authentication does the Lytx DriveCam API use?

The API uses HTTP bearer authentication. Call POST /auth/user with your Lytx credentials to obtain a bearer token, then send it on every subsequent request. Through Jentic, Lytx credentials live in your Jentic One instance - the agent never sees the raw username, password, or token.

Can I retrieve dashcam video clips with the Lytx DriveCam API?

Yes. The /video endpoint returns clip metadata and URLs associated with safety events. Look up the event in /safety first to get its event ID, then call /video to retrieve the clip.

What are the rate limits for the Lytx DriveCam API?

Lytx does not publish a public rate limit policy. Limits are tied to your account contract - your Lytx implementation manager can confirm the per-second and per-day caps.

How do I build a driver safety scorecard with the Lytx DriveCam API through Jentic?

Run pip install jentic, then search for 'list safety events'. Jentic returns the /safety operation schema. Execute it for the relevant time window and join the results to /driverassignments and /distances to compute per-driver scores.

Does the Lytx DriveCam API expose Hours of Service data?

Yes. GET /hos returns Hours of Service status and duty changes for drivers. Pair it with /dvir for a complete FMCSA-style compliance feed for nightly reporting.

Can I limit what my agent is allowed to do with the Lytx DriveCam API?

Yes. Because Jentic One is self-hosted, you decide which Lytx operations and which credential the agent may use, and it can only call what you grant. The Lytx DriveCam data endpoints are read-only, so you can restrict the agent to just the reads it needs, such as vehicles/all, safety, or trips, and withhold the rest. Since Lytx query filters travel as request parameters rather than path ids, every operation the agent can reach is one you have explicitly allowed.