> ## 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.109.0 - Load Tracking Vehicle Assignment Agreement

> New agreement field added to declared vehicle assignments on load tracking endpoints

**Released 19th October 2026**

This release adds a new `agreement` field to the `LoadTrackingVehicleAssignmentRead` schema on both load tracking endpoints. When a vehicle was declared on the load, `agreement` reports whether vehicles matched independently from location data corroborate that declaration. The endpoint descriptions have been updated to explain this behaviour.

<Check>
  **Minor Release:** Backward-compatible addition. The `agreement` field is new and required in the response schema; existing integrations that do not read it are unaffected.
</Check>

## Schema Changes

<AccordionGroup>
  <Accordion title="agreement field on vehicle_assignment — declared assignments" icon="sparkles">
    **Updated endpoints:**

    * `GET /v2/visibility/loads/tracking`
    * `GET /v2/visibility/loads/{load_id}/tracking`

    **What changed:**

    The `LoadTrackingVehicleAssignmentRead` schema now includes a required `agreement` field. This field is present when `source` is `declared` and indicates whether vehicles matched from location data back up the declared vehicle assignment.

    The endpoint descriptions have been updated to reflect this: *"For a declared vehicle, `agreement` says whether the vehicles matched from location data back it up."*

    **Before:**

    ```json theme={null}
    {
      "vehicle_assignment": {
        "source": "declared",
        "vehicle": { ... }
      }
    }
    ```

    **After:**

    ```json theme={null}
    {
      "vehicle_assignment": {
        "source": "declared",
        "vehicle": { ... },
        "agreement": "confirmed"
      }
    }
    ```

    **Impact:**

    * The `agreement` field is new and required in the response schema
    * It only applies to `declared` vehicle assignments (i.e. when you sent vehicle identifiers when posting or editing the load)
    * Integrations that do not read `agreement` require no changes
  </Accordion>
</AccordionGroup>

## Integration Notes

<Steps>
  <Step title="Read the agreement field for declared assignments">
    If your integration uses declared vehicle assignments, you can now read `agreement` to understand whether location data corroborates the declared vehicle:

    ```json theme={null}
    {
      "vehicle_assignment": {
        "source": "declared",
        "vehicle": {
          "id": "veh_abc123",
          "license_plate_number": "ABC-1234"
        },
        "agreement": "confirmed"
      }
    }
    ```
  </Step>

  <Step title="No action required for existing integrations">
    The `agreement` field is additive. If your integration does not read it, no changes are needed. The field is only present on `declared` vehicle assignments.
  </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 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.