> ## 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.101.0 - Load Vehicle & Driver Objects

> Vehicle and driver details on visibility loads restructured into nested objects; top-level license_plate_number, license_plate_region, and vin fields removed

**Released 16th October 2026**

This release restructures vehicle and driver details on the `POST /v2/visibility/loads` endpoint. The top-level `license_plate_number`, `license_plate_region`, and `vin` fields have been removed and replaced by a nested `vehicle` object. A new `driver` object has also been added, allowing you to associate a driver with a load at creation time.

<Warning>
  **Breaking Change:** The top-level `license_plate_number`, `license_plate_region`, and `vin` fields have been removed from both the request body and the `201` response. Move these values into the new `vehicle` object before upgrading.
</Warning>

## Breaking Changes

<AccordionGroup>
  <Accordion title="Vehicle fields moved into nested vehicle object" icon="wrench">
    **Updated endpoint:**

    * `POST /v2/visibility/loads`

    **What changed:**

    The top-level `license_plate_number`, `license_plate_region`, and `vin` fields have been removed. These values are now provided inside a `vehicle` object alongside the existing `eld_id` field.

    **Request body — before:**

    ```json theme={null}
    {
      "load_ref": "BOL-482910",
      "license_plate_number": "HMT-3570",
      "license_plate_region": "OH",
      "vin": "1FUJGLDR7CSBF1234",
      "carrier": { "dot_number": "1234567", "mc_number": "MC-7654321", "scac": "ABCD" },
      "origin": { "latitude": 39.9612, "longitude": -82.9988, "name": "Columbus, OH" },
      "destination": { "latitude": 40.7357, "longitude": -74.1724, "name": "Newark, NJ" },
      "estimated_departure_at": "2026-08-14T12:00:00Z",
      "estimated_arrival_at": "2026-08-16T08:00:00Z"
    }
    ```

    **Request body — after:**

    ```json theme={null}
    {
      "load_ref": "BOL-482910",
      "vehicle": {
        "eld_id": "TRUCK-1042",
        "license_plate_number": "HMT-3570",
        "license_plate_region": "OH",
        "vin": "1FUJGLDR7CSBF1234"
      },
      "carrier": { "dot_number": "1234567", "mc_number": "MC-7654321", "scac": "ABCD" },
      "origin": { "latitude": 39.9612, "longitude": -82.9988, "name": "Columbus, OH" },
      "destination": { "latitude": 40.7357, "longitude": -74.1724, "name": "Newark, NJ" },
      "estimated_departure_at": "2026-08-14T12:00:00Z",
      "estimated_arrival_at": "2026-08-16T08:00:00Z"
    }
    ```

    The same restructuring applies to the `201` response — `license_plate_number`, `license_plate_region`, and `vin` are no longer returned at the top level; they appear inside the `vehicle` object.

    **Impact:**

    * Any integration that reads or writes `license_plate_number`, `license_plate_region`, or `vin` at the top level must be updated
    * The `vehicle` object is optional — omit it entirely if you have no vehicle details to send
  </Accordion>
</AccordionGroup>

## New Features

<AccordionGroup>
  <Accordion title="Driver object on load creation" icon="sparkles">
    **Updated endpoint:**

    * `POST /v2/visibility/loads`

    **What changed:**

    A new optional `driver` object can now be included when creating a load. This lets you associate a driver with the load at creation time using any combination of identifiers you have available.

    **Request body example:**

    ```json theme={null}
    {
      "load_ref": "BOL-482910",
      "driver": {
        "eld_id": "DRV-2087",
        "first_name": "Jane",
        "last_name": "Doe",
        "email": "jane.doe@example.com",
        "phone_number": "+1 614-555-0142"
      },
      "origin": { "latitude": 39.9612, "longitude": -82.9988, "name": "Columbus, OH" },
      "destination": { "latitude": 40.7357, "longitude": -74.1724, "name": "Newark, NJ" },
      "estimated_departure_at": "2026-08-14T12:00:00Z",
      "estimated_arrival_at": "2026-08-16T08:00:00Z"
    }
    ```

    The `driver` object is also returned in the `201` response, confirming the values were recorded.

    **Impact:**

    * `driver` is optional — omitting it behaves exactly as before
    * Send only the driver identifiers you know; all fields within the object are optional
  </Accordion>
</AccordionGroup>

## Migration Guide

<Steps>
  <Step title="Move vehicle fields into the vehicle object">
    Replace any top-level `license_plate_number`, `license_plate_region`, and `vin` fields with a `vehicle` object:

    ```json theme={null}
    {
      "vehicle": {
        "license_plate_number": "HMT-3570",
        "license_plate_region": "OH",
        "vin": "1FUJGLDR7CSBF1234"
      }
    }
    ```

    If you were also sending an ELD vehicle identifier, include it in the same object:

    ```json theme={null}
    {
      "vehicle": {
        "eld_id": "TRUCK-1042",
        "license_plate_number": "HMT-3570",
        "license_plate_region": "OH",
        "vin": "1FUJGLDR7CSBF1234"
      }
    }
    ```
  </Step>

  <Step title="Update response parsing">
    If your integration reads `license_plate_number`, `license_plate_region`, or `vin` from the `201` response body, update your parser to read them from `response.vehicle.license_plate_number`, `response.vehicle.license_plate_region`, and `response.vehicle.vin` respectively.
  </Step>

  <Step title="Optionally add driver details">
    If you have driver information available at load creation time, you can now include it in the `driver` object. This step is optional and does not affect existing integrations.
  </Step>
</Steps>

***

## Need Help?

<CardGroup cols={2}>
  <Card title="API Reference" icon="book" href="/api-reference/telematics-api">
    View complete endpoint documentation for the Visibility API
  </Card>

  <Card title="Contact Support" icon="life-ring" href="mailto:support@catenaclearing.io">
    Questions about migrating 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.