> ## 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.94.0 - Partner Reference on Telematics Write Operations

> New partner_ref field added to request and response schemas across Telematics API write endpoints

**Released 13th October 2026**

## Partner reference on Telematics write operations

A new `partner_ref` field has been added to the request body and response schemas of all Telematics API write endpoints. This field lets you attach a partner-side reference identifier to each resource at creation or update time, making it straightforward to correlate Catena records with objects in your own system.

The change is additive and backward-compatible — existing requests continue to behave exactly as before.

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

### New field

| Field | Type | Description |
| - | - | - |
| `partner_ref` | string | A partner-side reference identifier for the resource. May be `null` if no reference has been set. |

### Affected endpoints

<AccordionGroup>
  <Accordion title="POST /v2/telematics/dvir-logs" icon="file-lines">
    The request body and all response schemas (200, 202, 502) now include a `partner_ref` field.

    ```bash theme={null}
    POST /v2/telematics/dvir-logs
    ```

    Example request body excerpt:

    ```json theme={null}
    {
      "partner_ref": "your-internal-ref-123",
      ...
    }
    ```
  </Accordion>

  <Accordion title="POST /v2/telematics/fuel-transactions" icon="gas-pump">
    The request body and all response schemas (200, 202, 502) now include a `partner_ref` field.

    ```bash theme={null}
    POST /v2/telematics/fuel-transactions
    ```
  </Accordion>

  <Accordion title="POST /v2/telematics/group-messages" icon="comments">
    The request body and all response schemas (200, 202, 502) now include a `partner_ref` field.

    ```bash theme={null}
    POST /v2/telematics/group-messages
    ```
  </Accordion>

  <Accordion title="POST /v2/telematics/messages" icon="message">
    The request body and all response schemas (200, 202, 502) now include a `partner_ref` field.

    ```bash theme={null}
    POST /v2/telematics/messages
    ```
  </Accordion>

  <Accordion title="POST /v2/telematics/trailers and PATCH /v2/telematics/trailers/{id}" icon="truck-ramp-box">
    The request body and all response schemas (200, 202, 502) now include a `partner_ref` field on both the create and update endpoints.

    ```bash theme={null}
    POST  /v2/telematics/trailers
    PATCH /v2/telematics/trailers/{id}
    ```
  </Accordion>

  <Accordion title="POST /v2/telematics/users and PATCH /v2/telematics/users/{id}" icon="user">
    The request body and all response schemas (200, 202, 502) now include a `partner_ref` field on both the create and update endpoints.

    ```bash theme={null}
    POST  /v2/telematics/users
    PATCH /v2/telematics/users/{id}
    ```
  </Accordion>

  <Accordion title="POST /v2/telematics/vehicles and PATCH /v2/telematics/vehicles/{id}" icon="car">
    The request body and all response schemas (200, 202, 502) now include a `partner_ref` field on both the create and update endpoints.

    ```bash theme={null}
    POST  /v2/telematics/vehicles
    PATCH /v2/telematics/vehicles/{id}
    ```
  </Accordion>

  <Accordion title="POST /v2/telematics/workflows and PATCH /v2/telematics/workflows/{id}" icon="diagram-project">
    The request body and all response schemas (200, 202, 502) now include a `partner_ref` field on both the create and update endpoints.

    ```bash theme={null}
    POST  /v2/telematics/workflows
    PATCH /v2/telematics/workflows/{id}
    ```
  </Accordion>
</AccordionGroup>

***

## Need help?

<CardGroup cols={2}>
  <Card title="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.