Teslemetry & Zubie connection types for Organizations API
This release addsteslemetry and zubie as new valid values for the conn_type field across all Organizations API TMS and TSP endpoints. The change is additive and backward-compatible.
Backward-compatible addition: The new
conn_type enum values are purely additive. No existing integrations are affected.New conn_type values
Affected TMS endpoints
GET /v2/orgs/tms
GET /v2/orgs/tms
The
conn_type field in each item of the response may now return teslemetry or zubie.POST /v2/orgs/tms
POST /v2/orgs/tms
The
conn_type field in the request body and the 201 response now accepts teslemetry and zubie.GET /v2/orgs/tms/{tms_id}
GET /v2/orgs/tms/{tms_id}
The
conn_type field in the response may now return teslemetry or zubie.PATCH /v2/orgs/tms/{tms_id}
PATCH /v2/orgs/tms/{tms_id}
The
conn_type field in the request body and the 200 response now accepts teslemetry and zubie.Affected TSP endpoints
GET /v2/orgs/tsps
GET /v2/orgs/tsps
The
conn_type field in each item of the response may now return teslemetry or zubie.POST /v2/orgs/tsps
POST /v2/orgs/tsps
The
conn_type field in the request body and the 201 response now accepts teslemetry and zubie.GET /v2/orgs/tsps/{tsp_id}
GET /v2/orgs/tsps/{tsp_id}
The
conn_type field in the response may now return teslemetry or zubie.PATCH /v2/orgs/tsps/{tsp_id}
PATCH /v2/orgs/tsps/{tsp_id}
The
conn_type field in the request body and the 200 response now accepts teslemetry and zubie.Need help?
API reference
View complete endpoint documentation for the Organizations API
Contact support
Questions about your integration? Our team is here to help