v2.77.0 - Zubie redirect_uri Field - Catena Telematics API

Released 25th September 2026

Zubie redirect_uri field

The ZubieCreds schema now includes an optional redirect_uri field. This field can be supplied when your Zubie OAuth application requires a redirect URI as part of its token exchange flow. The field is optional and backward-compatible — existing integrations that do not supply it are unaffected.

Schema changes

Field	Before	After
`redirect_uri`	Not present	Optional string

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}

Usage

If your Zubie application requires a redirect URI, include it in the credentials object:

{
  "credentials": {
    "provider": "zubie",
    "client_id": "your-client-id",
    "client_secret": "your-client-secret",
    "redirect_uri": "https://your-app.example.com/callback"
  }
}

Overview

Authentication

Telematics

Organizations

Integrations

Notifications

Intelligence

v2.77.0 - Zubie redirect_uri Field

Zubie redirect_uri field

Schema changes

Affected endpoints

Usage

Need help?

API reference

Contact support

​Zubie redirect_uri field

​Schema changes

​Affected endpoints

​Usage

​Need help?

API reference

Contact support

Zubie redirect_uri field

Schema changes

Affected endpoints

Usage

Need help?