> ## Documentation Index
> Fetch the complete documentation index at: https://docs.catenatelematics.com/llms.txt
> Use this file to discover all available pages before exploring further.

# v2.26.0 - Chronos Provider Support

> Chronos added as a new telematics service provider across all Integrations API endpoints

**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.

<Check>
  **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.
</Check>

### Provider support

<AccordionGroup>
  <Accordion title="Connections" icon="plug">
    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):**

    ```json theme={null}
    {
      "source_name": "chronos"
    }
    ```
  </Accordion>

  <Accordion title="TSPs" icon="building">
    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:**

    ```json theme={null}
    {
      "source_name": "chronos"
    }
    ```
  </Accordion>

  <Accordion title="Resource operations" icon="list">
    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`.
  </Accordion>

  <Accordion title="Schedules and executions" icon="calendar-day">
    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`
  </Accordion>
</AccordionGroup>

### Schema changes

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

| Schema | Change |
| - | - |
| `TspEnum` | `chronos` added as a valid enum value |
| `ConnectionRead` | `source_name` enum extended with `chronos` |
| `ResourceOperationRead` | `source_name` enum extended with `chronos` |
| `ExecutionRead` | `source_name` enum extended with `chronos` |
| `TspIntegrationsRead` | `source_name` enum extended with `chronos` |

***

## Need help?

<CardGroup cols={2}>
  <Card title="API Reference" icon="book" href="/api-reference/integrations-api">
    View complete endpoint documentation for the Integrations API
  </Card>

  <Card title="Contact Support" icon="life-ring" href="mailto:support@catenaclearing.io">
    Questions about integrating with Chronos? Our team is here to help
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.