> ## 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.2.0 - Fleet References & TSP Expansion

> New fleet_ref field for partner system references and 50+ additional telematics service providers

**Released 14th January 2026**

This minor release adds partner system reference tracking across all telematics resources and significantly expands supported telematics service provider (TSP) integrations.

<Check>
  **Minor Release:** This release includes backward-compatible additions to response schemas and enum expansions. No breaking changes to existing integrations.
</Check>

## New Response Fields

<AccordionGroup>
  <Accordion title="Fleet Reference Field" icon="link">
    A new `fleet_ref` field has been added to all major telematics resource schemas to support partner system reference tracking.

    **Schemas Updated:**

    * `hos_availability`
    * `hos_event`
    * `hos_violation`
    * `ifta_summary`
    * `user`
    * `vehicle`
    * `vehicle_location`

    **Field Details:**

    * **Type:** `string | null`
    * **Description:** The reference of the fleet in the partner system
    * **Required:** Yes (nullable)

    **Example Response:**

    ```json theme={null}
    {
      "id": "550e8400-e29b-41d4-a716-446655440000",
      "fleet_id": "fleet_123",
      "fleet_ref": "PARTNER_FLEET_ABC",
      "source_name": "samsara",
      "connection_id": "conn_456",
      "source_id": "vehicle_789"
    }
    ```

    <Tip>
      Use `fleet_ref` to maintain bidirectional references between Catena resources and your internal fleet management system identifiers.
    </Tip>
  </Accordion>
</AccordionGroup>

## Backward Compatibility

<AccordionGroup>
  <Accordion title="No Breaking Changes" icon="check">
    All changes in this release are backward-compatible:

    * **New field `fleet_ref`:** Nullable field added to response schemas. Existing API consumers can safely ignore this field.
    * **No endpoint changes:** All existing endpoints maintain the same paths, parameters, and behavior.

    **No migration required** for existing integrations.
  </Accordion>
</AccordionGroup>

***

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