> ## 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.24.0 - Route One ELD Provider Support

> Route One ELD added as a supported telematics provider across all data types

**Released 15th July 2026**

## Route One ELD Provider Support

This release expands the Catena platform's provider coverage by adding Route One ELD (`route_one_eld`) as a fully supported telematics service provider. The new provider value is available across all data schemas and webhook event types.

<Check>
  **Minor release:** This is a backward-compatible addition. No changes are required to existing integrations.
</Check>

### New provider support

<AccordionGroup>
  <Accordion title="Route One ELD added to TspEnum and all source_name fields" icon="sparkles">
    The value `route_one_eld` has been added to the `TspEnum` enumeration and to the `source_name` field across every data schema in the API. This means you can now filter, identify, and process data originating from Route One ELD devices using the standard `source_name` field.

    **Affected schemas:**

    | Category | Schemas |
    | - | - |
    | Vehicles | `BaseVehicle`, `BaseVehicleLocation`, `VehicleAdded`, `VehicleModified`, `VehicleRemoved`, `VehicleLocationAdded` |
    | Drivers & Users | `BaseUser`, `BaseDriverVehicleAssociation`, `UserAdded`, `UserModified`, `UserRemoved`, `DriverVehicleAssociationAdded`, `DriverVehicleAssociationModified` |
    | Trailers | `BaseTrailer`, `BaseTrailerLocation`, `BaseTrailerStatus`, `BaseTrailerVehicleAssociation`, `TrailerAdded`, `TrailerModified`, `TrailerRemoved`, `TrailerLocationAdded`, `TrailerLocationModified`, `TrailerStatusAdded`, `TrailerStatusModified`, `TrailerVehicleAssociationAdded`, `TrailerVehicleAssociationModified` |
    | HOS | `BaseHosEvent`, `BaseHosAvailability`, `BaseHosDailySnapshot`, `BaseHosViolation`, `HosEventAdded`, `HosEventModified`, `HosEventRemoved`, `HosAvailabilityAdded`, `HosAvailabilityModified`, `HosAvailabilityRemoved`, `HosDailySnapshotAdded`, `HosDailySnapshotModified`, `HosDailySnapshotRemoved`, `HosViolationAdded`, `HosViolationModified`, `HosViolationRemoved` |
    | IFTA | `BaseIftaSummary`, `IftaSummaryAdded`, `IftaSummaryModified`, `IftaSummaryRemoved` |
    | DVIR | `BaseDvirLog`, `DvirLogAdded`, `DvirLogModified`, `DvirLogRemoved` |
    | Engine & Fuel | `BaseEngineLog`, `BaseEngineStatus`, `BaseFuelTransaction`, `EngineLogAdded`, `EngineLogModified`, `EngineStatusAdded`, `EngineStatusModified`, `FuelTransactionAdded`, `FuelTransactionModified` |
    | Messages | `BaseMessage`, `BaseGroupMessage`, `MessageAdded`, `MessageModified`, `GroupMessageAdded`, `GroupMessageModified` |
    | Fleet & Connections | `BaseFleetInfo`, `BaseFleetConnectionEvent`, `BaseConnectionEvent`, `FleetInfoAdded`, `FleetInfoModified`, `FleetInfoRemoved`, `FleetConnectionCreated`, `ConnectionCreated`, `ConnectionStaled` |
    | Workflows & Executions | `BaseWorkflow`, `BaseExecutionEvent`, `WorkflowAdded`, `WorkflowModified`, `WorkflowRemoved`, `ExecutionFailed`, `ExecutionStaled` |
    | Resource Operations | `BaseResourceOperationEvent`, `BaseTelematicsEvent`, `ResourceOperationCreated`, `ResourceOperationFailed`, `ResourceOperationSucceeded` |

    **Example — filtering data by provider:**

    ```bash theme={null}
    GET /v2/telematics/vehicles?source_name=route_one_eld
    ```

    **Example — identifying Route One ELD data in a webhook event:**

    ```json theme={null}
    {
      "event": "vehicle.added",
      "data": [
        {
          "id": "veh_abc123",
          "source_name": "route_one_eld",
          "vin": "1HGBH41JXMN109186"
        }
      ]
    }
    ```
  </Accordion>
</AccordionGroup>

### No action required

This is a purely additive change. Existing integrations continue to work without modification. If you want to start ingesting data from Route One ELD connections, no code changes are needed — data will appear automatically with `source_name: "route_one_eld"` once a Route One ELD connection is established.

***

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