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

Zubie credential changes

The ZubieCreds schema has been updated to reflect how Zubie’s token exchange actually works. Zubie’s own API does not use a redirect_uri in its token exchange flow, so that field has been removed. In its place, client_id and client_secret are now required fields.

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 redirect_uri from Zubie credential payloads

Search your codebase for any request bodies that include redirect_uri alongside a Zubie provider credential and remove that field.
2

Add client_id and client_secret to Zubie credential payloads

Update your Zubie credential objects to include the required client_id and client_secret fields.
3

Update response parsing

If your code reads or stores redirect_uri from Zubie credential responses, remove that logic. Update any code that reads credentials to handle client_id and client_secret instead.
4

Update stored schemas or validation

If you validate Zubie credential objects against a local schema or type definition, remove redirect_uri and add client_id and client_secret as required fields.

Need help?

API reference

View complete endpoint documentation for the Integrations API

Contact support

Questions about this release? Our team is here to help