> ## 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.48.0 - New TSP Providers & Connection Type

> Five new TSP source names and a new webfleet_slc connection type added across Organizations API endpoints

**Released 4th September 2026**

## New TSP providers & connection type

This release expands the `TspEnum` with five new telematics service providers and adds `webfleet_slc` as a new connection type across TMS and TSP endpoints.

<Check>
  **Backward-compatible addition:** All new enum values are additive. No existing integrations are affected.
</Check>

### New TSP source names

The following `source_name` values are now valid across `GET /v2/orgs/tsps`, `POST /v2/orgs/tsps`, `GET /v2/orgs/tsps/{tsp_id}`, and `PATCH /v2/orgs/tsps/{tsp_id}`:

| New `source_name` value | Provider |
| - | - |
| `elog_plus` | Elog Plus |
| `garmin` | Garmin |
| `simplex` | Simplex |
| `spectre_eld` | Spectre ELD |
| `under_control_eld` | Under Control ELD |

### New connection type

`webfleet_slc` has been added to the `ConnectionTypeEnum` (`conn_type` field) across all TMS and TSP endpoints.

### Affected endpoints

<AccordionGroup>
  <Accordion title="GET /v2/orgs/tsps" icon="list">
    The `source_name` query parameter and response field now accept all five new values. The `conn_type` response field now includes `webfleet_slc`.

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

  <Accordion title="POST /v2/orgs/tsps" icon="plus">
    The `source_name` and `conn_type` fields in the request body and 201 response now accept the new values.

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

    {
      "source_name": "garmin",
      "conn_type": "webfleet_slc"
    }
    ```
  </Accordion>

  <Accordion title="GET /v2/orgs/tsps/{tsp_id}" icon="magnifying-glass">
    The `source_name` and `conn_type` fields in the response may now return any of the new values.
  </Accordion>

  <Accordion title="PATCH /v2/orgs/tsps/{tsp_id}" icon="pen">
    The `source_name` and `conn_type` fields in the request body and response now accept the new values.

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

    {
      "source_name": "spectre_eld",
      "conn_type": "webfleet_slc"
    }
    ```
  </Accordion>

  <Accordion title="GET /v2/orgs/tms" icon="list">
    The `conn_type` response field now includes `webfleet_slc`.
  </Accordion>

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

  <Accordion title="GET /v2/orgs/tms/{tms_id}" icon="magnifying-glass">
    The `conn_type` field in the response may now return `webfleet_slc`.
  </Accordion>

  <Accordion title="PATCH /v2/orgs/tms/{tms_id}" icon="pen">
    The `conn_type` field in the request body and response now accepts `webfleet_slc`.
  </Accordion>
</AccordionGroup>

***

## Need help?

<CardGroup cols={2}>
  <Card title="API reference" icon="book" href="/api-reference/organizations-api">
    View complete TSP and TMS endpoint documentation
  </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.