Skip to main content
Released 27th July 2026

​
New TSP integrations and DriverTech credentials

This release expands the Integrations API with three new telematics service providers — Dreyev, Nexus ELD, and Ozod ELD — and adds support for DriverTech credentials when creating and managing connections.
Backward-compatible release: All changes are additive. Existing integrations continue to work without modification.

​
New TSP providers

The source_name enum has been extended across all relevant endpoints and schemas to include three new providers: These values are now accepted and returned by the following endpoints:
  • GET /v2/integrations/connections
  • POST /v2/integrations/connections
  • GET /v2/integrations/connections/{connection_id}
  • PATCH /v2/integrations/connections/{connection_id}
  • GET /v2/integrations/connections/{connection_id}/resource-operations/{resource_operation_id}
  • GET /v2/integrations/connections/{connection_id}/schedules/{schedule_id}/executions
  • GET /v2/integrations/connections/resource-operations
  • GET /v2/integrations/tsps
  • GET /v2/integrations/tsps/{tsp_id}

​
DriverTech credential support

The credentials field on connection create and update requests now accepts a DriverTechCreds object in addition to all previously supported credential types.Affected endpoints:
  • POST /v2/integrations/connections (request body and response)
  • PATCH /v2/integrations/connections/{connection_id} (request body and response)
Example — create a DriverTech connection:
Connection read responses (ConnectionRead) now include DriverTechCreds as a possible shape for the credentials field.Affected endpoints:
  • GET /v2/integrations/connections
  • GET /v2/integrations/connections/{connection_id}

​
Need help?

Integrations API reference

View complete endpoint documentation for the Integrations API

Contact support

Questions about your integration? Our team is here to help