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

> 2 changes across providers and fleet

**Released 4th August 2026**

## STS ELD Provider Support

This release expands Catena's provider coverage by adding **STS ELD** as a supported telematics service provider. The `sts_eld` value is now available in the `source_name` field across all telematics data types and in the `TspEnum` enumeration.

<Check>
  **Backward-compatible addition:** No existing integrations are affected. The `sts_eld` value is purely additive to existing enumerations.
</Check>

### New provider support

<AccordionGroup>
  <Accordion title="STS ELD added to TspEnum and all source_name fields" icon="sparkles">
    The `sts_eld` value has been added to the `TspEnum` schema and to the `source_name` enum field across every telematics data schema. This means data originating from STS ELD devices will now be correctly identified in API responses.

    **Affected schemas:**

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

    **Example response with STS ELD data:**

    ```json theme={null}
    {
      "source_name": "sts_eld",
      "id": "...",
      "vehicle_id": "..."
    }
    ```
  </Accordion>
</AccordionGroup>

### No action required

This is a purely additive change. Your existing integration will continue to work without modification. If you filter or switch on `source_name` values, you may want to add handling for `sts_eld` to process data from this new provider.

```javascript theme={null}
// Example: handling the new sts_eld provider
switch (event.source_name) {
  case "sts_eld":
    // Handle STS ELD data
    break;
  // ... existing cases
}
```

## Vehicle Embedded Data in Location Events

This release enriches vehicle location data by embedding vehicle context directly in location responses and webhook events. Consumers of location data no longer need to make separate requests to look up vehicle details.

<Check>
  **Backward-Compatible:** All new fields are additive. Existing integrations continue to work without modification.
</Check>

### New Features

<AccordionGroup>
  <Accordion title="Vehicle context embedded in location data" icon="map-pin">
    Vehicle location responses now include an embedded `vehicle` object directly in each location record. This applies to both the `BaseVehicleLocation` schema and the `VehicleLocationAdded` webhook event payload.

    Previously, you would receive a location record with a vehicle reference and need to fetch vehicle details separately. Now the vehicle data is included inline.

    **Example response (after):**

    ```json theme={null}
    {
      "latitude": 41.8781,
      "longitude": -87.6298,
      "timestamp": "2026-08-04T12:00:00Z",
      "vehicle": {
        "id": "veh_abc123",
        "name": "Truck 42",
        "vin": "1HGBH41JXMN109186"
      }
    }
    ```
  </Accordion>

  <Accordion title="New VehicleEmbedded schema" icon="code">
    A new `VehicleEmbedded` schema has been added to the API specification. This schema defines the structure of the vehicle object embedded in location records.

    The schema is used in:

    * `BaseVehicleLocation` — base schema for all vehicle location responses
    * `VehicleLocationAdded` — webhook event payload for new location data
  </Accordion>
</AccordionGroup>

### Schema Changes

| Schema | Change | Details |
| - | - | - |
| `BaseVehicleLocation` | New property | `vehicle` — embedded vehicle context object |
| `VehicleLocationAdded` | New property | `data[].vehicle` — embedded vehicle context in each event item |
| `VehicleEmbedded` | New schema | Defines the structure of embedded vehicle data |

***

## Need help?

<CardGroup cols={2}>
  <Card title="API reference" icon="book" href="/api-reference/telematics-api">
    View complete endpoint documentation and current API schemas
  </Card>

  <Card title="Contact support" icon="life-ring" href="mailto:support@catenaclearing.io">
    Questions about this release? Our team is here to help
  </Card>
</CardGroup>


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