> ## 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.81.0 - TSP Operations Map

> New operations field added to TSP integration responses, exposing per-operation write support status alongside existing read support

**Released 5th October 2026**

## TSP operations map

This release adds a new `operations` field to the TSP integration response schema on both the list and get endpoints. The field exposes write-operation support status (create/update) for each resource, complementing the existing `integrations` field which reflects read support.

<Check>
  **Backward-compatible addition:** The `operations` field is a new required property in the response. Existing integrations that do not read this field are unaffected.
</Check>

### New `operations` field

The `operations` object maps each resource to a nested object describing the support status of individual write operations:

```json theme={null}
{
  "tsp_id": "00000000-0000-0000-0000-000000000001",
  "integrations": {
    "vehicle": "implemented",
    "vehicle_location": "implemented",
    "hos_event": "unknown",
    "user": "not_implemented",
    "message": "implemented"
  },
  "operations": {
    "vehicle": {
      "create": "implemented",
      "update": "not_implemented"
    },
    "vehicle_location": {
      "create": "unknown",
      "update": "unknown"
    },
    "hos_event": {
      "create": "unknown",
      "update": "unknown"
    },
    "user": {
      "create": "not_implemented",
      "update": "not_implemented"
    },
    "message": {
      "create": "implemented",
      "update": "not_implemented"
    }
  }
}
```

Each operation value uses the same support status enum as `integrations`: `implemented`, `not_implemented`, `not_supported`, or `unknown`.

### `integrations` field clarification

The description of the `integrations` field has been updated to clarify that it reflects **read support** only. Write support is now surfaced via the new `operations` field.

| Field | Reflects |
| - | - |
| `integrations` | Read support per resource |
| `operations` | Write support (create/update) per resource |

### Affected endpoints

<AccordionGroup>
  <Accordion title="GET /v2/integrations/tsps" icon="list">
    Each item in the `items` array now includes an `operations` object.

    ```bash theme={null}
    GET /v2/integrations/tsps
    ```
  </Accordion>

  <Accordion title="GET /v2/integrations/tsps/{tsp_id}" icon="magnifying-glass">
    The response object now includes an `operations` field.

    ```bash theme={null}
    GET /v2/integrations/tsps/{tsp_id}
    ```
  </Accordion>
</AccordionGroup>

***

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