v2.15.0

Released 29th June 2026

Daily Metrics Enhancement

This release adds bytes_transferred to the daily metrics response, providing visibility into data transfer volume alongside existing usage metrics.

Backward-compatible addition: Existing integrations continue to work without changes. The new field is additive only.

Response Changes

GET /v2/usage/daily-metrics

The response schema for GET /v2/usage/daily-metrics now includes a bytes_transferred field in each daily metrics record.New required field:

bytes_transferred — Total bytes transferred for the given day

Example response item (after):

{
  "date": "2026-06-29",
  "requests": 1240,
  "bytes_transferred": 524288
}

Migration Checklist

Update response parsing (optional)

If your integration parses daily metrics responses, you may want to consume the new bytes_transferred field. No changes are required for existing functionality.

Intelligence Time Series Analytics

This release adds two new time series analytics endpoints to the Intelligence API, enabling trend analysis of safety events and HOS violations over time.

New Feature: Time series data is now available for both safety events and HOS violations, allowing you to build trend dashboards and historical analysis workflows.

New Endpoints

Safety Events Time Series

A new endpoint provides time series data for driver safety events, enabling trend analysis over configurable time windows.

GET /v2/intelligence/analytics/safety-events/time-series

Use this endpoint to:

Track safety event trends over time
Build dashboards showing improvement or deterioration in driver safety
Identify periods with elevated safety event rates

HOS Violations Time Series

A new endpoint provides time series data for Hours of Service violations, enabling compliance trend analysis.

GET /v2/intelligence/analytics/hos-violations/time-series

Use this endpoint to:

Monitor HOS violation trends over time
Generate compliance trend reports
Identify patterns in violation frequency across your fleet

New Schema

The EventTimeSeriesDataPoint schema has been added to support both new endpoints. It represents a single data point in a time series response, containing a timestamp and associated event count or metric value.

TSP Enrichment for Analytics

This release enriches analytics responses across drivers, vehicles, trailers, and fleets with richer TSP (ELD provider) metadata. Two new TSP providers are now supported, and fleet summaries expose display-ready branding fields.

Backward-compatible: All changes are additive. No existing fields were removed or renamed. No migration is required.

New TSP providers

Two new ELD providers are now recognized across all source_name fields in analytics responses:

Provider key	Description
`drive_hos_v2`	Drive HOS v2 ELD provider
`wizefleet_eld`	WizeFleet ELD provider

These values are valid for the source_name field on DriverSummary, VehicleSummary, TrailerSummary, VehicleLiveLocation, and TrailerLiveLocation objects.

New response fields

Driver, vehicle, and trailer analytics — new tsp field

The following endpoints now include a tsp field on each item in the response, providing the resolved TSP object for that asset:

GET /v2/intelligence/analytics/drivers
GET /v2/intelligence/analytics/vehicles
GET /v2/intelligence/analytics/trailers

Example response item (drivers):

{
  "driver_id": "drv_123",
  "source_name": "samsara",
  "tsp": {
    "name": "Samsara",
    "logo_url": "https://...",
    "logo_dark_url": "https://..."
  }
}

Fleet analytics — enriched TSP metadata

The GET /v2/intelligence/analytics/fleets endpoint now returns enriched TSP metadata on each fleet’s tsps array. Each TSP object now includes:

Field	Description
`name`	Display name of the TSP provider
`logo_url`	URL to the TSP’s logo (light theme)
`logo_dark_url`	URL to the TSP’s logo (dark theme)

Example response item:

{
  "fleet_id": "flt_456",
  "tsps": [
    {
      "name": "Motive",
      "logo_url": "https://...",
      "logo_dark_url": "https://..."
    }
  ]
}

Affected endpoints

Endpoint	Change
`GET /v2/intelligence/analytics/drivers`	New `tsp` field; `source_name` supports `drive_hos_v2`, `wizefleet_eld`
`GET /v2/intelligence/analytics/vehicles`	New `tsp` field; `source_name` supports `drive_hos_v2`, `wizefleet_eld`
`GET /v2/intelligence/analytics/trailers`	New `tsp` field; `source_name` supports `drive_hos_v2`, `wizefleet_eld`
`GET /v2/intelligence/analytics/vehicles/live-locations`	`source_name` supports `drive_hos_v2`, `wizefleet_eld`
`GET /v2/intelligence/analytics/trailers/live-locations`	`source_name` supports `drive_hos_v2`, `wizefleet_eld`
`GET /v2/intelligence/analytics/fleets`	`tsps` items gain `name`, `logo_url`, `logo_dark_url`

WizeFleet ELD Support

This release expands the list of supported telematics service providers by adding WizeFleet ELD (wizefleet_eld) to the TspEnum enumeration. The new provider value is available across all TSP management endpoints.

Backward-compatible addition: Existing integrations are unaffected. The wizefleet_eld value is purely additive to the source_name enum.

New provider support

WizeFleet ELD added to TspEnum

The wizefleet_eld value has been added to the source_name field across all TSP-related schemas and endpoints.Affected endpoints:

Method	Endpoint	Change
`GET`	`/v2/orgs/tsps`	`source_name` filter and response now include `wizefleet_eld`
`POST`	`/v2/orgs/tsps`	`source_name` request body and response now accept `wizefleet_eld`
`GET`	`/v2/orgs/tsps/{tsp_id}`	`source_name` response field now includes `wizefleet_eld`
`PATCH`	`/v2/orgs/tsps/{tsp_id}`	`source_name` request body and response now accept `wizefleet_eld`

Example — list TSPs filtered by WizeFleet ELD:

GET /v2/orgs/tsps?source_name=wizefleet_eld

Example — create a TSP connection for WizeFleet ELD:

POST /v2/orgs/tsps
Content-Type: application/json

{
  "source_name": "wizefleet_eld"
}

Affected schemas

The following OpenAPI schemas have been updated to include wizefleet_eld:

TspEnum — the core enumeration for TSP source names
TspCreate — used when creating a new TSP
TspRead — returned when reading TSP details
TspUpdate — used when updating an existing TSP

Need Help?

API Reference

View complete endpoint documentation with current API structure

Contact Support

Questions about your integration? Our team is here to help

Overview

Authentication

Telematics

Organizations

Integrations

Notifications

Intelligence

Daily Metrics Enhancement

Response Changes

Migration Checklist

Intelligence Time Series Analytics

New Endpoints

New Schema

TSP Enrichment for Analytics

New TSP providers

New response fields

Affected endpoints

WizeFleet ELD Support

New provider support

Affected schemas

Need Help?

API Reference

Contact Support

​Daily Metrics Enhancement

​Response Changes

​Migration Checklist

​Intelligence Time Series Analytics

​New Endpoints

​New Schema

​TSP Enrichment for Analytics

​New TSP providers

​New response fields

​Affected endpoints

​WizeFleet ELD Support

​New provider support

​Affected schemas

​Need Help?

API Reference

Contact Support

Daily Metrics Enhancement

Response Changes

Migration Checklist

Intelligence Time Series Analytics

New Endpoints

New Schema

TSP Enrichment for Analytics

New TSP providers

New response fields

Affected endpoints

WizeFleet ELD Support

New provider support

Affected schemas

Need Help?