> ## 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.97.0 - Seven Days Log TSP Provider

> seven_days_log added as a new source_name value across the Organizations API TSP endpoints and all Telematics API endpoints

**Released 15th October 2026**

## Seven Days Log TSP provider support

This release adds `seven_days_log` as a new valid value for the `source_name` field across the Organizations API TSP endpoints and all Telematics API endpoints. The change is additive and backward-compatible.

<Check>
  **Backward-compatible addition:** The new `seven_days_log` enum value is purely additive. No existing integrations are affected.
</Check>

### New TSP source name

| New `source_name` value | Provider |
| - | - |
| `seven_days_log` | Seven Days Log |

***

## Organizations API

The `source_name` field now accepts and may return `seven_days_log` on all Organizations API TSP endpoints.

### Affected endpoints

<AccordionGroup>
  <Accordion title="GET /v2/orgs/tsps" icon="list">
    The `source_name` query parameter now accepts `seven_days_log` for filtering. The `source_name` field in each item of the response may now return `seven_days_log`.

    ```bash theme={null}
    # Filter TSPs by the new provider
    GET /v2/orgs/tsps?source_name=seven_days_log
    ```
  </Accordion>

  <Accordion title="POST /v2/orgs/tsps" icon="plus">
    The `source_name` field in the request body and the 201 response now accepts `seven_days_log`.

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

    {
      "source_name": "seven_days_log",
      ...
    }
    ```
  </Accordion>

  <Accordion title="GET /v2/orgs/tsps/{tsp_id}" icon="magnifying-glass">
    The `source_name` field in the response may now return `seven_days_log`.
  </Accordion>

  <Accordion title="PATCH /v2/orgs/tsps/{tsp_id}" icon="pen">
    The `source_name` field in the request body and the 200 response now accepts `seven_days_log`.

    ```bash theme={null}
    PATCH /v2/orgs/tsps/{tsp_id}
    Content-Type: application/json

    {
      "source_name": "seven_days_log"
    }
    ```
  </Accordion>
</AccordionGroup>

***

## Telematics API

The `source_name` field may now return `seven_days_log` on all Telematics API endpoints.

### Affected endpoints

<AccordionGroup>
  <Accordion title="Fleet & connections" icon="truck">
    * `GET /v2/telematics/fleet-info`
    * `GET /v2/telematics/fleet-info/{fleet_info_id}`
  </Accordion>

  <Accordion title="Vehicles & locations" icon="location-dot">
    * `GET /v2/telematics/vehicles`
    * `GET /v2/telematics/vehicles/{vehicle_id}`
    * `GET /v2/telematics/vehicle-locations`
    * `GET /v2/telematics/vehicle-sensor-events`
    * `GET /v2/telematics/engine-logs`
    * `GET /v2/telematics/engine-statuses`
  </Accordion>

  <Accordion title="Trailers" icon="trailer">
    * `GET /v2/telematics/trailers`
    * `GET /v2/telematics/trailers/{trailer_id}`
    * `GET /v2/telematics/trailer-locations`
    * `GET /v2/telematics/trailer-statuses`
    * `GET /v2/telematics/trailer-vehicle-associations`
  </Accordion>

  <Accordion title="Drivers & associations" icon="id-card">
    * `GET /v2/telematics/users`
    * `GET /v2/telematics/users/{user_id}`
    * `GET /v2/telematics/driver-vehicle-associations`
  </Accordion>

  <Accordion title="Compliance & HOS" icon="clipboard-check">
    * `GET /v2/telematics/hos-events`
    * `GET /v2/telematics/hos-events/{hos_event_id}/attachments`
    * `GET /v2/telematics/hos-daily-logs`
    * `GET /v2/telematics/hos-daily-snapshots`
    * `GET /v2/telematics/hos-availabilities`
    * `GET /v2/telematics/hos-violations`
    * `GET /v2/telematics/dvir-logs`
    * `GET /v2/telematics/dvir-logs/defects`
    * `GET /v2/telematics/dvir-logs/{dvir_log_id}/defects`
    * `GET /v2/telematics/ifta-summaries`
    * `GET /v2/telematics/documents`
  </Accordion>

  <Accordion title="Safety" icon="shield">
    * `GET /v2/telematics/driver-safety-events`
  </Accordion>

  <Accordion title="Messaging & workflows" icon="message">
    * `GET /v2/telematics/messages`
    * `GET /v2/telematics/group-messages`
    * `GET /v2/telematics/workflows`
    * `GET /v2/telematics/workflows/{workflow_id}`
  </Accordion>

  <Accordion title="Fuel & transactions" icon="gas-pump">
    * `GET /v2/telematics/fuel-transactions`
  </Accordion>

  <Accordion title="Analytics" icon="chart-bar">
    * `GET /v2/telematics/analytics/drivers`
    * `GET /v2/telematics/analytics/vehicles`
    * `GET /v2/telematics/analytics/vehicles/live-locations`
    * `GET /v2/telematics/analytics/trailers`
    * `GET /v2/telematics/analytics/trailers/live-locations`
  </Accordion>
</AccordionGroup>

***

## Need help?

<CardGroup cols={2}>
  <Card title="Organizations API reference" icon="building" href="/api-reference/organizations-api">
    View complete endpoint documentation for the Organizations API
  </Card>

  <Card title="Telematics API reference" icon="book" href="/api-reference/telematics-api">
    View complete endpoint documentation for the Telematics 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.