> ## 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.31.0 - Trimac Provider Support

> New telematics service provider added across all data types

**Released 29th July 2026**

## Trimac Provider Support

This release adds Trimac as a supported telematics service provider (TSP) across the entire Catena API. All data types that carry a `source_name` field now recognize `trimac` as a valid value.

<Check>
  **Backward-compatible addition:** Existing integrations are unaffected. The `trimac` value is additive — no existing enum values were removed or renamed.
</Check>

### New provider support

<AccordionGroup>
  <Accordion title="Trimac added to TspEnum and all source_name fields" icon="sparkles">
    The `trimac` value has been added to the `TspEnum` schema and to the `source_name` enum on every data model in the API. This means you can now:

    * Filter requests by `source_name=trimac` to retrieve data originating from Trimac-connected fleets
    * Expect `"source_name": "trimac"` in webhook event payloads for Trimac fleets
    * Use Trimac connections through the standard Catena Connect flow

    **Affected data types include:**

    | Category | Models |
    | - | - |
    | Fleet & Vehicles | `BaseVehicle`, `BaseVehicleLocation`, `BaseFleetInfo`, `BaseTrailer`, `BaseTrailerLocation`, `BaseTrailerStatus`, `BaseTrailerVehicleAssociation` |
    | Drivers & Users | `BaseUser`, `BaseDriverVehicleAssociation` |
    | Compliance | `BaseHosEvent`, `BaseHosDailySnapshot`, `BaseHosAvailability`, `BaseHosViolation`, `BaseIftaSummary`, `BaseDvirLog` |
    | Engine & Telematics | `BaseEngineLog`, `BaseEngineStatus`, `BaseTelematicsEvent` |
    | Messaging | `BaseMessage`, `BaseGroupMessage` |
    | Connections & Workflows | `BaseConnectionEvent`, `BaseFleetConnectionEvent`, `BaseExecutionEvent`, `BaseResourceOperationEvent`, `BaseWorkflow` |
    | Fuel | `BaseFuelTransaction` |

    All corresponding webhook event schemas (e.g. `VehicleAdded`, `HosEventModified`, `EngineLogAdded`, etc.) are also updated.
  </Accordion>
</AccordionGroup>

### Using the new provider

Once a Trimac fleet is connected via Catena Connect, data flows through the standard API with `source_name` set to `trimac`. No changes to your existing API calls are required.

```bash theme={null}
# Filter telematics data by Trimac source
GET /v2/telematics/vehicles?source_name=trimac
```

```json theme={null}
// Example vehicle response from a Trimac-connected fleet
{
  "id": "veh_abc123",
  "source_name": "trimac",
  "vin": "1HGBH41JXMN109186",
  "make": "Freightliner",
  "model": "Cascadia"
}
```

***

## 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 integrating with Trimac or other providers? Our team is here to help.
  </Card>
</CardGroup>


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