Skip to main content
Released 14th October 2026

​
Teslemetry PKCE support

The TeslemetryCreds schema now includes an optional code_verifier field. This field supports PKCE (Proof Key for Code Exchange) flows where a code verifier is required as part of the Teslemetry OAuth token exchange. The field is optional and backward-compatible — existing Teslemetry integrations that do not supply it are unaffected.

​
Schema changes

​
Affected endpoints

All connections and TMS-connections endpoints that accept or return Teslemetry 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 Teslemetry application uses a PKCE flow, include the code_verifier in the credentials object:

​
Need help?

API reference

View complete endpoint documentation for the Integrations API

Contact support

Questions about this release? Our team is here to help