New TSP providers & connection type
This release expands theTspEnum with five new telematics service providers and adds webfleet_slc as a new connection type across TMS and TSP endpoints.
Backward-compatible addition: All new enum values are additive. No existing integrations are affected.
New TSP source names
The followingsource_name values are now valid across GET /v2/orgs/tsps, POST /v2/orgs/tsps, GET /v2/orgs/tsps/{tsp_id}, and PATCH /v2/orgs/tsps/{tsp_id}:
New connection type
webfleet_slc has been added to the ConnectionTypeEnum (conn_type field) across all TMS and TSP endpoints.
Affected endpoints
GET /v2/orgs/tsps
GET /v2/orgs/tsps
The
source_name query parameter and response field now accept all five new values. The conn_type response field now includes webfleet_slc.POST /v2/orgs/tsps
POST /v2/orgs/tsps
The
source_name and conn_type fields in the request body and 201 response now accept the new values.GET /v2/orgs/tsps/{tsp_id}
GET /v2/orgs/tsps/{tsp_id}
The
source_name and conn_type fields in the response may now return any of the new values.PATCH /v2/orgs/tsps/{tsp_id}
PATCH /v2/orgs/tsps/{tsp_id}
The
source_name and conn_type fields in the request body and response now accept the new values.GET /v2/orgs/tms
GET /v2/orgs/tms
The
conn_type response field now includes webfleet_slc.POST /v2/orgs/tms
POST /v2/orgs/tms
The
conn_type field in the request body and 201 response now accepts webfleet_slc.GET /v2/orgs/tms/{tms_id}
GET /v2/orgs/tms/{tms_id}
The
conn_type field in the response may now return webfleet_slc.PATCH /v2/orgs/tms/{tms_id}
PATCH /v2/orgs/tms/{tms_id}
The
conn_type field in the request body and response now accepts webfleet_slc.Need help?
API reference
View complete TSP and TMS endpoint documentation
Contact support
Questions about your integration? Our team is here to help.