How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Lytx Geofences (DriveCam) API

The Geofences (DriveCam) API from Lytx — 4 operation(s) for geofences (drivecam).

Lytx Geofences (DriveCam) API is one of 37 APIs that Lytx publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Geofences (DriveCam). The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 6 operations across 4 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.lytx.com.

6 operations 4 paths 5 schemas 1 DELETE3 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.lytx.com/consent-management
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Lytx Geofences (DriveCam) API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

Paths & Operations 6

Across 4 paths, the API surfaces 6 operations — 1 DELETE, 3 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Geofences (DriveCam) 6
POST
/v1/geofences
Create Geofence
body → 200400401403404500
GET
/v1/geofences
Retrieve Geofences
11 params → 200204400401403404500
DELETE
/v1/geofences/{geofenceIdentifier}
Delete Specified Geofence by ID
1 param → 204400401403404500
PUT
/v1/geofences/{geofenceIdentifier}
Update Specified Geofence
1 param body → 200400401403404500
GET
/v1/geofence/activations
Get Geofence Activations
13 params → 200204400401403404500
GET
/v1/geofence/activations/endreason
Get Activation End Reasons
→ 200400401403404500

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are SingleGeofenceResponse (18 properties), AddGeofenceRequest (7 properties), ActivationEndReasonResponse (2 properties), ListGeofenceResponse (2 properties). Each schema is shown below with its type and property counts.

SingleGeofenceResponse
object
18 properties
ActivationsResponse
object
2 properties
AddGeofenceRequest
object
7 properties 6 required
ListGeofenceResponse
object
2 properties
ActivationEndReasonResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lytx-geofences-drivecam-api-openapi.yml Raw ↑

Other APIs Lytx publishes across the network.

Lytx Consent API
Lytx Devices (DriveCam) API
Lytx Devices (GO9) API
Lytx DeviceStatusInfo (GO9) API
Lytx Diagnostics (GO9) API
Lytx Distances (DriveCam) API
Lytx Driver Assignments (DriveCam) API
Lytx Driver ID (DriveCam) API
Lytx Drivers (GO9) API
Lytx DVIR (DriveCam) API
Lytx DVIR (GO9) API
Lytx ECM API
Where this information came from

This is an independent, third-party profile of Lytx Geofences (DriveCam) API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.