> ## 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.3.0 - Fleet Filtering & Connection References

> New fleet filtering parameters for connections endpoint and fleet_ref field added to Connection schema

**Released 16th January 2026**

This minor release adds fleet-based filtering capabilities to the connections endpoint and extends the Connection schema with partner system reference tracking.

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

## New Query Parameters

<AccordionGroup>
  <Accordion title="Fleet Filtering for Connections" icon="filter">
    The `GET /connections` endpoint now supports filtering by fleet identifiers using two new optional query parameters.

    **New Parameters:**

    * `fleet_ids` - Filter by Catena's internal fleet IDs (array of UUIDs, max 100 items)
    * `fleet_refs` - Filter by your organization's fleet reference identifiers (array of strings, max 100 items)

    **Use Cases:**

    * Retrieve connections for specific fleets in your organization
    * Use `fleet_ids` when working with Catena's fleet identifiers
    * Use `fleet_refs` when working with your own fleet reference system

    **Example Requests:**

    ```bash theme={null}
    # Filter by Catena fleet IDs
    GET /connections?fleet_ids=550e8400-e29b-41d4-a716-446655440000&fleet_ids=660e8400-e29b-41d4-a716-446655440001

    # Filter by your organization's fleet references
    GET /connections?fleet_refs=FLEET_ABC&fleet_refs=FLEET_XYZ

    # Combine with other filters
    GET /connections?fleet_refs=FLEET_ABC&status=active
    ```

    <Tip>
      Use `fleet_refs` to filter connections using your own fleet identifiers without needing to map to Catena's internal IDs first.
    </Tip>
  </Accordion>
</AccordionGroup>

## New Response Fields

<AccordionGroup>
  <Accordion title="Connection Fleet Reference" icon="link">
    A new `fleet_ref` field has been added to the Connection schema to support partner system reference tracking.

    **Field Details:**

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

    **Example Response:**

    ```json theme={null}
    {
      "id": "conn_123",
      "fleet_id": "550e8400-e29b-41d4-a716-446655440000",
      "fleet_ref": "PARTNER_FLEET_ABC",
      "status": "active",
      "source_name": "samsara",
      "created_at": "2026-01-16T10:00:00Z"
    }
    ```

    <Tip>
      Use `fleet_ref` to maintain bidirectional references between Catena connections 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 query parameters:** Optional parameters added to `/connections` endpoint. Existing API calls without these parameters continue to work unchanged.
    * **New field `fleet_ref`:** Nullable field added to Connection response schema. Existing API consumers can safely ignore this field.
    * **No endpoint changes:** All existing endpoints maintain the same paths 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.