Skip to main content
Released 23rd September 2026
This release includes a breaking change: client_id and client_secret have been removed from the Zubie credentials schema. See Zubie credential changes below.

​
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.
Backward-compatible addition: The new TeslemetryCreds schema variant is purely additive. Existing connections using other credential types are unaffected.

​
Affected endpoints

The credentials field in each item of the response may now contain a TeslemetryCreds object.
The credentials field in the request body now accepts a TeslemetryCreds object.
The credentials field in the response may now contain a TeslemetryCreds object.
The credentials field in the request body now accepts a TeslemetryCreds object.
The credentials field in each item of the response may now contain a TeslemetryCreds object.
The credentials field in the request body now accepts a TeslemetryCreds object.
The credentials field in the response may now contain a TeslemetryCreds object.
The credentials field in the request body now accepts a TeslemetryCreds object.

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

​
Schema changes

​
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:
After:

​
Migration checklist

1

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

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

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.

​
Need help?

API reference

View complete endpoint documentation for the Integrations API

Contact support

Questions about this release? Our team is here to help