> ## Documentation Index
> Fetch the complete documentation index at: https://docs.catenatelematics.com/llms.txt
> Use this file to discover all available pages before exploring further.

# v2.15.0

> 4 changes across providers, compliance, safety and fleet

**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.

<Check>
  **Backward-compatible addition:** Existing integrations continue to work without changes. The new field is additive only.
</Check>

### Response Changes

<AccordionGroup>
  <Accordion title="GET /v2/usage/daily-metrics" icon="chart-bar">
    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):**

    ```json theme={null}
    {
      "date": "2026-06-29",
      "requests": 1240,
      "bytes_transferred": 524288
    }
    ```
  </Accordion>
</AccordionGroup>

### Migration Checklist

<Steps>
  <Step title="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.
  </Step>
</Steps>

## 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.

<Check>
  **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.
</Check>

### New Endpoints

<AccordionGroup>
  <Accordion title="Safety Events Time Series" icon="chart-line">
    A new endpoint provides time series data for driver safety events, enabling trend analysis over configurable time windows.

    ```bash theme={null}
    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
  </Accordion>

  <Accordion title="HOS Violations Time Series" icon="clock">
    A new endpoint provides time series data for Hours of Service violations, enabling compliance trend analysis.

    ```bash theme={null}
    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
  </Accordion>
</AccordionGroup>

### 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.

<Check>
  **Backward-compatible:** All changes are additive. No existing fields were removed or renamed. No migration is required.
</Check>

### 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

<AccordionGroup>
  <Accordion title="Driver, vehicle, and trailer analytics — new tsp field" icon="list">
    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):**

    ```json theme={null}
    {
      "driver_id": "drv_123",
      "source_name": "samsara",
      "tsp": {
        "name": "Samsara",
        "logo_url": "https://...",
        "logo_dark_url": "https://..."
      }
    }
    ```
  </Accordion>

  <Accordion title="Fleet analytics — enriched TSP metadata" icon="building">
    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:**

    ```json theme={null}
    {
      "fleet_id": "flt_456",
      "tsps": [
        {
          "name": "Motive",
          "logo_url": "https://...",
          "logo_dark_url": "https://..."
        }
      ]
    }
    ```
  </Accordion>
</AccordionGroup>

### 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.

<Check>
  **Backward-compatible addition:** Existing integrations are unaffected. The `wizefleet_eld` value is purely additive to the `source_name` enum.
</Check>

### New provider support

<AccordionGroup>
  <Accordion title="WizeFleet ELD added to TspEnum" icon="sparkles">
    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:**

    ```bash theme={null}
    GET /v2/orgs/tsps?source_name=wizefleet_eld
    ```

    **Example — create a TSP connection for WizeFleet ELD:**

    ```bash theme={null}
    POST /v2/orgs/tsps
    Content-Type: application/json

    {
      "source_name": "wizefleet_eld"
    }
    ```
  </Accordion>
</AccordionGroup>

### 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?

<CardGroup cols={2}>
  <Card title="API Reference" icon="book" href="/api-reference/telematics-api">
    View complete endpoint documentation with current API structure
  </Card>

  <Card title="Contact Support" icon="life-ring" href="mailto:support@catenaclearing.io">
    Questions about your integration? Our team is here to help
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.