> ## 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.29.0 - RigBot Provider Support

> New telematics service provider integration: RigBot

**Released 24th July 2026**

## RigBot Provider Support

This release adds RigBot as a supported telematics service provider (TSP) across the Catena API. All data schemas that include a `source_name` field now recognize `rigbot` as a valid value.

<Check>
  **New integration:** RigBot is now available as a data source across all telematics, HOS, DVIR, fleet, and webhook event schemas.
</Check>

### New provider support

<AccordionGroup>
  <Accordion title="RigBot added to source_name enum" icon="sparkles">
    The `rigbot` value has been added to the `source_name` field across all resource schemas and webhook event payloads. This includes:

    * Vehicles, trailers, and locations
    * Drivers and driver-vehicle associations
    * HOS events, daily snapshots, availability, and violations
    * DVIR logs
    * Engine logs and engine status
    * IFTA summaries
    * Fuel transactions
    * Messages and group messages
    * Fleet info and fleet connections
    * Workflows and execution events
    * Resource operation events
    * Users

    The `TspEnum` schema has also been updated to include `rigbot` as a valid enum value.

    **Example response with RigBot as source:**

    ```json theme={null}
    {
      "id": "veh_abc123",
      "source_name": "rigbot",
      "vin": "1HGBH41JXMN109186"
    }
    ```

    **Filtering by RigBot source:**

    ```bash theme={null}
    GET /v2/telematics/vehicles?source_name=rigbot
    ```
  </Accordion>
</AccordionGroup>

### Affected schemas

The following schemas now include `rigbot` as a valid `source_name` value:

| Schema category | Schemas updated |
| - | - |
| Vehicles | `BaseVehicle`, `VehicleAdded`, `VehicleModified`, `VehicleRemoved` |
| Vehicle locations | `BaseVehicleLocation`, `VehicleLocationAdded` |
| Trailers | `BaseTrailer`, `TrailerAdded`, `TrailerModified`, `TrailerRemoved` |
| Trailer locations | `BaseTrailerLocation`, `TrailerLocationAdded`, `TrailerLocationModified` |
| Trailer status | `BaseTrailerStatus`, `TrailerStatusAdded`, `TrailerStatusModified` |
| Trailer associations | `BaseTrailerVehicleAssociation`, `TrailerVehicleAssociationAdded`, `TrailerVehicleAssociationModified` |
| Driver associations | `BaseDriverVehicleAssociation`, `DriverVehicleAssociationAdded`, `DriverVehicleAssociationModified` |
| HOS | `BaseHosEvent`, `BaseHosAvailability`, `BaseHosDailySnapshot`, `BaseHosViolation` and related event schemas |
| DVIR | `BaseDvirLog`, `DvirLogAdded`, `DvirLogModified`, `DvirLogRemoved` |
| Engine | `BaseEngineLog`, `BaseEngineStatus` and related event schemas |
| IFTA | `BaseIftaSummary`, `IftaSummaryAdded`, `IftaSummaryModified`, `IftaSummaryRemoved` |
| Fuel | `BaseFuelTransaction`, `FuelTransactionAdded`, `FuelTransactionModified` |
| Messages | `BaseMessage`, `BaseGroupMessage` and related event schemas |
| Fleet | `BaseFleetInfo`, `BaseFleetConnectionEvent`, `FleetInfoAdded`, `FleetInfoModified`, `FleetInfoRemoved`, `FleetConnectionCreated` |
| Connections | `BaseConnectionEvent`, `ConnectionCreated`, `ConnectionStaled` |
| Workflows | `BaseWorkflow`, `WorkflowAdded`, `WorkflowModified`, `WorkflowRemoved` |
| Executions | `BaseExecutionEvent`, `ExecutionFailed`, `ExecutionStaled` |
| Resource operations | `BaseResourceOperationEvent`, `ResourceOperationCreated`, `ResourceOperationFailed`, `ResourceOperationSucceeded` |
| Users | `BaseUser`, `UserAdded`, `UserModified`, `UserRemoved` |
| TSP enum | `TspEnum` |

***

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