> ## 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.62.0 - TSP Provider Types

> New types field added to TSP schemas across all Organizations API TSP endpoints

**Released 9th September 2026**

## TSP provider types

This release adds a `types` field to the TSP schemas across all Organizations API TSP endpoints. The field categorises a telematics service provider by the type of service it offers (for example, `ELDs` or `GPS telematics`). The change is additive and backward-compatible.

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

### New field

| Field | Type | Description |
| - | - | - |
| `types` | `string[]` | List of service categories for the TSP (e.g. `ELDs`, `GPS telematics`). |

### Affected endpoints

<AccordionGroup>
  <Accordion title="GET /v2/orgs/tsps" icon="list">
    The `types` field is now included in each TSP object in the response array.

    ```json theme={null}
    {
      "id": "11223344-5566-7788-99aa-bbccddeeff00",
      "name": "Samsara",
      "source_name": "samsara",
      "types": ["ELDs", "GPS telematics"],
      "status": "active"
    }
    ```
  </Accordion>

  <Accordion title="POST /v2/orgs/tsps" icon="plus">
    The `types` field is now accepted in the request body and returned in the 201 response.

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

    {
      "source_name": "samsara",
      "types": ["ELDs", "GPS telematics"],
      ...
    }
    ```
  </Accordion>

  <Accordion title="GET /v2/orgs/tsps/{tsp_id}" icon="magnifying-glass">
    The `types` field is now included in the TSP object in the response.

    ```json theme={null}
    {
      "id": "11223344-5566-7788-99aa-bbccddeeff00",
      "name": "Samsara",
      "source_name": "samsara",
      "types": ["ELDs", "GPS telematics"],
      "status": "active"
    }
    ```
  </Accordion>

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

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

    {
      "types": ["ELDs", "GPS telematics"]
    }
    ```
  </Accordion>
</AccordionGroup>

***

## Need help?

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