> ## 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.74.0 - Teslemetry Provider Support & Zubie Credential Simplification

> Teslemetry added as a new credentials provider across all connections endpoints, and Zubie credentials no longer require client_id or client_secret

**Released 23rd September 2026**

<Warning>
  **This release includes a breaking change:** `client_id` and `client_secret` have been removed from the Zubie credentials schema. See [Zubie credential changes](#zubie-credential-changes) below.
</Warning>

## Teslemetry provider support

`TeslemetryCreds` is now a valid credentials type across all connections and TMS-connections endpoints. You can create, update, and retrieve connections using Teslemetry credentials in the same way as any other supported provider.

<Check>
  **Backward-compatible addition:** The new `TeslemetryCreds` schema variant is purely additive. Existing connections using other credential types are unaffected.
</Check>

### Affected endpoints

<AccordionGroup>
  <Accordion title="GET /v2/integrations/connections" icon="list">
    The `credentials` field in each item of the response may now contain a `TeslemetryCreds` object.

    ```bash theme={null}
    GET /v2/integrations/connections
    ```
  </Accordion>

  <Accordion title="POST /v2/integrations/connections" icon="plus">
    The `credentials` field in the request body now accepts a `TeslemetryCreds` object.

    ```bash theme={null}
    POST /v2/integrations/connections
    Content-Type: application/json

    {
      "credentials": {
        "provider": "teslemetry",
        "access_token": "<your-teslemetry-access-token>"
      }
    }
    ```
  </Accordion>

  <Accordion title="GET /v2/integrations/connections/{connection_id}" icon="magnifying-glass">
    The `credentials` field in the response may now contain a `TeslemetryCreds` object.

    ```bash theme={null}
    GET /v2/integrations/connections/{connection_id}
    ```
  </Accordion>

  <Accordion title="PATCH /v2/integrations/connections/{connection_id}" icon="pen">
    The `credentials` field in the request body now accepts a `TeslemetryCreds` object.

    ```bash theme={null}
    PATCH /v2/integrations/connections/{connection_id}
    Content-Type: application/json

    {
      "credentials": {
        "provider": "teslemetry",
        "access_token": "<your-teslemetry-access-token>"
      }
    }
    ```
  </Accordion>

  <Accordion title="GET /v2/integrations/tms-connections" icon="list">
    The `credentials` field in each item of the response may now contain a `TeslemetryCreds` object.

    ```bash theme={null}
    GET /v2/integrations/tms-connections
    ```
  </Accordion>

  <Accordion title="POST /v2/integrations/tms-connections" icon="plus">
    The `credentials` field in the request body now accepts a `TeslemetryCreds` object.

    ```bash theme={null}
    POST /v2/integrations/tms-connections
    Content-Type: application/json

    {
      "credentials": {
        "provider": "teslemetry",
        "access_token": "<your-teslemetry-access-token>"
      }
    }
    ```
  </Accordion>

  <Accordion title="GET /v2/integrations/tms-connections/{tms_connection_id}" icon="magnifying-glass">
    The `credentials` field in the response may now contain a `TeslemetryCreds` object.

    ```bash theme={null}
    GET /v2/integrations/tms-connections/{tms_connection_id}
    ```
  </Accordion>

  <Accordion title="PATCH /v2/integrations/tms-connections/{tms_connection_id}" icon="pen">
    The `credentials` field in the request body now accepts a `TeslemetryCreds` object.

    ```bash theme={null}
    PATCH /v2/integrations/tms-connections/{tms_connection_id}
    Content-Type: application/json

    {
      "credentials": {
        "provider": "teslemetry",
        "access_token": "<your-teslemetry-access-token>"
      }
    }
    ```
  </Accordion>
</AccordionGroup>

***

## Zubie credential changes

The `client_id` and `client_secret` fields have been removed from the Zubie credentials schema. These were Catena's own registered Zubie app credentials, managed internally via Secrets Manager. They were never intended to be supplied per connection and are no longer part of the schema.

<Warning>
  **Breaking change:** Any code that sends `client_id` or `client_secret` in a Zubie credentials object will need to be updated. These fields are no longer accepted in requests and will no longer appear in responses.
</Warning>

### Schema changes

| Field | Before | After |
| - | - | - |
| `client_id` | Required string | Removed |
| `client_secret` | Required string | Removed |

### Affected endpoints

All connections and TMS-connections endpoints that accept or return Zubie credentials are affected:

* `GET /v2/integrations/connections`
* `POST /v2/integrations/connections`
* `GET /v2/integrations/connections/{connection_id}`
* `PATCH /v2/integrations/connections/{connection_id}`
* `GET /v2/integrations/tms-connections`
* `POST /v2/integrations/tms-connections`
* `GET /v2/integrations/tms-connections/{tms_connection_id}`
* `PATCH /v2/integrations/tms-connections/{tms_connection_id}`

### Migration

**Before:**

```json theme={null}
{
  "credentials": {
    "provider": "zubie",
    "client_id": "your-client-id",
    "client_secret": "your-client-secret",
    "api_key": "your-api-key"
  }
}
```

**After:**

```json theme={null}
{
  "credentials": {
    "provider": "zubie",
    "api_key": "your-api-key"
  }
}
```

### Migration checklist

<Steps>
  <Step title="Remove client_id and client_secret from Zubie credential payloads">
    Search your codebase for any request bodies that include `client_id` or `client_secret` alongside a Zubie provider credential and remove those fields.
  </Step>

  <Step title="Update response parsing">
    If your code reads or stores `client_id` or `client_secret` from Zubie credential responses, remove that logic — these fields are no longer returned.
  </Step>

  <Step title="Update stored schemas or validation">
    If you validate Zubie credential objects against a local schema or type definition, remove `client_id` and `client_secret` from that definition.
  </Step>
</Steps>

***

## Need help?

<CardGroup cols={2}>
  <Card title="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 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.