> ## 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.37.0

> 2 changes across providers and compliance

**Released 11th August 2026**

## CoGo ELD & HOS Daily Log Support

This release expands the Integrations API with support for a new telematics service provider and a new resource type, broadening the range of data you can sync through Catena.

<Check>
  **Backward-compatible release:** All existing integrations continue to work without any changes. New enum values are purely additive.
</Check>

### New TSP: CoGo ELD

`cogo_eld` has been added to the `source_name` enum across all connection and resource operation endpoints. You can now create and manage connections for fleets using CoGo ELD.

**Affected 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}`

**Example — create a CoGo ELD connection:**

```bash theme={null}
POST /v2/integrations/connections
Content-Type: application/json

{
  "source_name": "cogo_eld",
  "credentials": { ... }
}
```

### New resource type: HOS daily log

`hos_daily_log` has been added to the `resource` enum. You can now schedule syncs and backfills for HOS daily log data.

**Affected endpoints:**

* `GET /v2/integrations/connections/{connection_id}/schedules`
* `POST /v2/integrations/connections/{connection_id}/schedules`
* `GET /v2/integrations/connections/{connection_id}/schedules/{schedule_id}`
* `PATCH /v2/integrations/connections/{connection_id}/schedules/{schedule_id}`
* `POST /v2/integrations/connections/{connection_id}/schedules/{schedule_id}/activate`
* `POST /v2/integrations/connections/{connection_id}/schedules/activate-schedules`
* `GET /v2/integrations/connections/{connection_id}/schedules/{schedule_id}/executions`
* `GET /v2/integrations/connections/{connection_id}/resource-operations/{resource_operation_id}`
* `GET /v2/integrations/connections/resource-operations`
* `GET /v2/integrations/connections/data-freshness`
* `POST /v2/integrations/connections/schedules/backfill`

**Example — create a schedule for HOS daily logs:**

```bash theme={null}
POST /v2/integrations/connections/{connection_id}/schedules
Content-Type: application/json

{
  "resource": "hos_daily_log",
  "frequency": "daily"
}
```

**Example — filter resource operations by the new resource type:**

```bash theme={null}
GET /v2/integrations/connections/resource-operations?resource=hos_daily_log
```

**Example — backfill HOS daily log data:**

```bash theme={null}
POST /v2/integrations/connections/schedules/backfill
Content-Type: application/json

{
  "resource": "hos_daily_log",
  "from_datetime": "2026-01-01T00:00:00Z",
  "to_datetime": "2026-08-01T00:00:00Z"
}
```

## Optimus Tracker Integration

This release expands provider support in the Integrations API by adding **Optimus Tracker** as a new telematics service provider (TSP). The `optimus_tracker` value is now accepted and returned across all integration endpoints that reference a `source_name`, and a new credentials schema is available for creating and managing Optimus Tracker connections.

<Check>
  **Backward compatible:** All changes in this release are additive. No existing integrations are affected.
</Check>

### New provider support

<AccordionGroup>
  <Accordion title="Optimus Tracker credentials" icon="key">
    Two new credential schemas have been added to support Optimus Tracker connections:

    * **`OptimusTrackerCreds-Input`** — used when creating or updating a connection
    * **`OptimusTrackerCreds-Output`** — returned when reading a connection

    These schemas are available as new `anyOf` variants on the `credentials` field in `ConnectionCreate`, `ConnectionUpdate`, and `ConnectionRead`.

    **Creating an Optimus Tracker connection:**

    ```bash theme={null}
    POST /v2/integrations/connections
    ```

    ```json theme={null}
    {
      "source_name": "optimus_tracker",
      "credentials": {
        // OptimusTrackerCreds-Input fields
      }
    }
    ```
  </Accordion>

  <Accordion title="source_name enum updated" icon="list">
    The `optimus_tracker` value has been added to the `source_name` enum across all endpoints and schemas that reference a TSP source:

    | Endpoint | Change |
    | - | - |
    | `GET /v2/integrations/connections` | `source_name` now includes `optimus_tracker` in responses |
    | `POST /v2/integrations/connections` | `source_name` accepts `optimus_tracker` in request and response |
    | `GET /v2/integrations/connections/{connection_id}` | `source_name` now includes `optimus_tracker` in response |
    | `PATCH /v2/integrations/connections/{connection_id}` | `source_name` accepts and returns `optimus_tracker` |
    | `GET /v2/integrations/connections/resource-operations` | `source_name` filter and response now include `optimus_tracker` |
    | `GET /v2/integrations/connections/{connection_id}/resource-operations/{resource_operation_id}` | `source_name` now includes `optimus_tracker` in response |
    | `GET /v2/integrations/connections/{connection_id}/schedules/{schedule_id}/executions` | `source_name` now includes `optimus_tracker` in response |
    | `GET /v2/integrations/tsps` | `source_name` now includes `optimus_tracker` in response |
    | `GET /v2/integrations/tsps/{tsp_id}` | `source_name` now includes `optimus_tracker` in response |
  </Accordion>
</AccordionGroup>

### Filtering by Optimus Tracker

You can now filter resource operations by `source_name=optimus_tracker`:

```bash theme={null}
GET /v2/integrations/connections/resource-operations?source_name=optimus_tracker
```

***

## Need help?

<CardGroup cols={2}>
  <Card title="Integrations API reference" icon="puzzle-piece" 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 your integration? Our team is here to help
  </Card>
</CardGroup>


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