> ## 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.30.0 - New TSP integrations and DriverTech credentials

> Three new telematics providers and DriverTech credential support across the Integrations API

**Released 27th July 2026**

## New TSP integrations and DriverTech credentials

This release expands the Integrations API with three new telematics service providers — **Dreyev**, **Nexus ELD**, and **Ozod ELD** — and adds support for **DriverTech** credentials when creating and managing connections.

<Check>
  **Backward-compatible release:** All changes are additive. Existing integrations continue to work without modification.
</Check>

### New TSP providers

The `source_name` enum has been extended across all relevant endpoints and schemas to include three new providers:

| Provider | Enum value |
| - | - |
| Dreyev | `dreyev` |
| Nexus ELD | `nexus_eld` |
| Ozod ELD | `ozod_eld` |

These values are now accepted and returned by the following endpoints:

* `GET /v2/integrations/connections`
* `POST /v2/integrations/connections`
* `GET /v2/integrations/connections/{connection_id}`
* `PATCH /v2/integrations/connections/{connection_id}`
* `GET /v2/integrations/connections/{connection_id}/resource-operations/{resource_operation_id}`
* `GET /v2/integrations/connections/{connection_id}/schedules/{schedule_id}/executions`
* `GET /v2/integrations/connections/resource-operations`
* `GET /v2/integrations/tsps`
* `GET /v2/integrations/tsps/{tsp_id}`

### DriverTech credential support

<AccordionGroup>
  <Accordion title="Creating and updating connections" icon="plug">
    The `credentials` field on connection create and update requests now accepts a `DriverTechCreds` object in addition to all previously supported credential types.

    **Affected endpoints:**

    * `POST /v2/integrations/connections` (request body and response)
    * `PATCH /v2/integrations/connections/{connection_id}` (request body and response)

    **Example — create a DriverTech connection:**

    ```bash theme={null}
    POST /v2/integrations/connections
    ```

    ```json theme={null}
    {
      "source_name": "dreyev",
      "credentials": {
        "type": "DriverTechCreds",
        "username": "your-username",
        "password": "your-password"
      }
    }
    ```
  </Accordion>

  <Accordion title="Reading connections" icon="eye">
    Connection read responses (`ConnectionRead`) now include `DriverTechCreds` as a possible shape for the `credentials` field.

    **Affected endpoints:**

    * `GET /v2/integrations/connections`
    * `GET /v2/integrations/connections/{connection_id}`
  </Accordion>
</AccordionGroup>

***

## Need help?

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