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

> 2 changes across providers, fleet and analytics

**Released 24th June 2026**

## Fleet Connection Source Enrichment

This release enriches fleet connection webhook events with a new `source_name` field, giving you direct visibility into which telematics provider sourced each fleet connection event.

<Check>
  **Backward-Compatible Addition:** The `source_name` field is additive. No changes to existing fields or endpoint behavior are required.
</Check>

### Schema Changes

<AccordionGroup>
  <Accordion title="Fleet Connection Events" icon="webhook">
    The `BaseFleetConnectionEvent` schema and the `FleetConnectionCreated` event payload now include a new required field:

    | Field | Type | Description |
    | - | - | - |
    | `source_name` | `string` | The name of the telematics provider that is the source of the fleet connection event. |

    **Affected schemas:**

    * `BaseFleetConnectionEvent`
    * `FleetConnectionCreated` (within each item in the `data` array)

    **Example `fleet_connection.created` event payload (updated):**

    ```json theme={null}
    {
      "event": "fleet_connection.created",
      "data": [
        {
          "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
          "source_name": "Samsara",
          "status": "active",
          "created_at": "2026-06-24T10:00:00Z"
        }
      ]
    }
    ```
  </Accordion>
</AccordionGroup>

### What You Need to Do

No migration is required. The `source_name` field is a new addition to the response schema. Existing webhook consumers will continue to work without changes.

If you want to take advantage of the new field, update your webhook handler to read `source_name` from fleet connection event payloads.

## Vehicle Utilization Insights

This release adds a new vehicle utilization summary endpoint to the Intelligence API, enabling you to retrieve aggregated utilization metrics across your fleet.

<Check>
  **Backward-compatible release:** No existing endpoints or parameters were changed. You can adopt the new endpoint at your own pace.
</Check>

### New features

<AccordionGroup>
  <Accordion title="Vehicle utilization summary" icon="sparkles">
    A new endpoint is available under the Intelligence Insights group that returns aggregated vehicle utilization data for a given time range.

    ```bash theme={null}
    GET /v2/intelligence/insight/vehicle-utilization
    ```

    The response is a cursor-paginated list of `VehicleUtilizationSummary` objects, consistent with the pagination model used across other Intelligence endpoints.

    **Use cases:**

    * Identify underutilized vehicles to right-size your fleet
    * Track utilization trends over time for performance reporting
    * Feed utilization data into dispatch and asset management workflows
  </Accordion>
</AccordionGroup>

***

## Need Help?

<CardGroup cols={2}>
  <Card title="Notifications API Reference" icon="book" href="/api-reference/notifications-api">
    View complete webhook endpoint documentation and event schemas.
  </Card>

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


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