> ## 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.65.0 - Omnitracs One Telematics Provider

> omnitracs_one added as a new source_name value across all telematics and webhook event schemas

**Released 9th September 2026**

## Omnitracs One telematics provider

This release adds `omnitracs_one` as a new valid value for the `source_name` field across all telematics data schemas and webhook event payloads. The change is additive and backward-compatible.

<Check>
  **Backward-compatible addition:** The new `omnitracs_one` enum value is purely additive. No existing integrations are affected.
</Check>

### New TSP source name

The following `source_name` value is now valid across all telematics and webhook event schemas:

| New `source_name` value | Provider |
| - | - |
| `omnitracs_one` | Omnitracs One |

### Affected schemas

`omnitracs_one` has been added to the `source_name` enum on all base telematics schemas and their corresponding webhook event payloads. This covers every data type returned by the Telematics API and delivered via webhooks.

<AccordionGroup>
  <Accordion title="Fleet & connections" icon="truck">
    * `BaseFleetInfo` / `FleetInfoAdded`, `FleetInfoModified`, `FleetInfoRemoved`
    * `BaseFleetConnectionEvent` / `FleetConnectionCreated`
    * `BaseConnectionEvent` / `ConnectionCreated`, `ConnectionStaled`
  </Accordion>

  <Accordion title="Vehicles & locations" icon="location-dot">
    * `BaseVehicle` / `VehicleAdded`, `VehicleModified`, `VehicleRemoved`
    * `BaseVehicleLocation` / `VehicleLocationAdded`
    * `BaseTrailer` / `TrailerAdded`, `TrailerModified`, `TrailerRemoved`
    * `BaseTrailerLocation` / `TrailerLocationAdded`, `TrailerLocationModified`
    * `BaseTrailerStatus` / `TrailerStatusAdded`, `TrailerStatusModified`
    * `BaseTrailerVehicleAssociation` / `TrailerVehicleAssociationAdded`, `TrailerVehicleAssociationModified`
  </Accordion>

  <Accordion title="Drivers & associations" icon="id-card">
    * `BaseUser` / `UserAdded`, `UserModified`, `UserRemoved`
    * `BaseDriverVehicleAssociation` / `DriverVehicleAssociationAdded`, `DriverVehicleAssociationModified`
  </Accordion>

  <Accordion title="Compliance & HOS" icon="clipboard-check">
    * `BaseHosEvent` / `HosEventAdded`, `HosEventModified`, `HosEventRemoved`
    * `BaseHosDailyLog` / `HosDailyLogAdded`, `HosDailyLogModified`
    * `BaseHosDailySnapshot` / `HosDailySnapshotAdded`, `HosDailySnapshotModified`, `HosDailySnapshotRemoved`
    * `BaseHosAvailability` / `HosAvailabilityAdded`, `HosAvailabilityModified`, `HosAvailabilityRemoved`
    * `BaseHosViolation` / `HosViolationAdded`, `HosViolationModified`, `HosViolationRemoved`
    * `BaseDvirLog` / `DvirLogAdded`, `DvirLogModified`, `DvirLogRemoved`
    * `BaseIftaSummary` / `IftaSummaryAdded`, `IftaSummaryModified`, `IftaSummaryRemoved`
  </Accordion>

  <Accordion title="Engine & telematics events" icon="gauge">
    * `BaseEngineLog` / `EngineLogAdded`, `EngineLogModified`
    * `BaseEngineStatus` / `EngineStatusAdded`, `EngineStatusModified`
    * `BaseTelematicsEvent`
  </Accordion>

  <Accordion title="Safety" icon="shield">
    * `BaseDriverSafetyEvent` / `DriverSafetyEventAdded`, `DriverSafetyEventModified`, `DriverSafetyEventRemoved`
  </Accordion>

  <Accordion title="Messaging & workflows" icon="message">
    * `BaseMessage` / `MessageAdded`, `MessageModified`
    * `BaseGroupMessage` / `GroupMessageAdded`, `GroupMessageModified`
    * `BaseWorkflow` / `WorkflowAdded`, `WorkflowModified`, `WorkflowRemoved`
  </Accordion>

  <Accordion title="Fuel & transactions" icon="gas-pump">
    * `BaseFuelTransaction` / `FuelTransactionAdded`, `FuelTransactionModified`
  </Accordion>

  <Accordion title="Resource operations & executions" icon="gear">
    * `BaseResourceOperationEvent` / `ResourceOperationCreated`, `ResourceOperationFailed`, `ResourceOperationSucceeded`
    * `BaseExecutionEvent` / `ExecutionFailed`, `ExecutionStaled`
  </Accordion>
</AccordionGroup>

### TspEnum

`omnitracs_one` has also been added to the top-level `TspEnum`, making it a valid value wherever that enum is referenced across the API.

***

## Need help?

<CardGroup cols={2}>
  <Card title="API reference" icon="book" href="/api-reference/telematics-api">
    View complete endpoint documentation for the Telematics API
  </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.