Skip to main content
Released 20th July 2026

​
Chronos Provider Support

This release expands the Integrations API with support for Chronos as a new telematics service provider (TSP). The chronos value is now a valid option for the source_name field across all connections, TSP, resource operation, and execution endpoints.
Backward-compatible addition: Existing integrations are unaffected. The chronos enum value is purely additive — no changes are required unless you want to use Chronos connections.

​
Provider support

The source_name field on ConnectionRead objects now includes chronos as a valid enum value. This affects the following endpoints:
  • GET /v2/integrations/connections
  • POST /v2/integrations/connections
  • GET /v2/integrations/connections/{connection_id}
  • PATCH /v2/integrations/connections/{connection_id}
Example response (source_name field):
The TspEnum schema now includes chronos, meaning Chronos appears in TSP listings and detail responses:
  • GET /v2/integrations/tsps
  • GET /v2/integrations/tsps/{tsp_id}
Example response:
The source_name field on ResourceOperationRead objects now includes chronos:
  • GET /v2/integrations/connections/resource-operations
  • GET /v2/integrations/connections/{connection_id}/resource-operations/{resource_operation_id}
You can also filter resource operations by source_name=chronos using the source_name query parameter on GET /v2/integrations/connections/resource-operations.
The source_name field on ExecutionRead objects now includes chronos:
  • GET /v2/integrations/connections/{connection_id}/schedules
  • GET /v2/integrations/connections/{connection_id}/schedules/{schedule_id}/executions

​
Schema changes

The following schemas have been updated to include chronos in their source_name enum:

​
Need help?

API Reference

View complete endpoint documentation for the Integrations API

Contact Support

Questions about integrating with Chronos? Our team is here to help