> ## 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.110.0 - Load Tracking Health

> New tracking_health field added to load tracking endpoint responses

**Released 19th October 2026**

This release adds a new required `tracking_health` field to the response schemas for both load tracking endpoints. The field indicates how far to trust the `last_position` reported for the vehicle carrying a load. The endpoint descriptions have been updated to explain this behaviour.

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

## Schema Changes

<AccordionGroup>
  <Accordion title="tracking_health field on load tracking responses" icon="sparkles">
    **Updated endpoints:**

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

    **What changed:**

    Both load tracking response schemas now include a required `tracking_health` field alongside `last_position`. This field describes how far to trust the last reported position for the vehicle carrying the load.

    The endpoint descriptions have been updated to reflect this: *"`last_position` is the last position that vehicle reported, and `tracking_health` says how far to trust it."*

    **Before:**

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

    **After:**

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

    **Impact:**

    * `tracking_health` is a new required field in the response schema for both endpoints
    * It applies to all load tracking responses regardless of whether the vehicle assignment is `declared` or `inferred`
    * Integrations that do not read `tracking_health` require no changes
  </Accordion>
</AccordionGroup>

## Integration Notes

<Steps>
  <Step title="Read tracking_health alongside last_position">
    Use `tracking_health` to understand the reliability of the position data returned for a load's vehicle:

    ```json theme={null}
    {
      "vehicle_assignment": {
        "source": "declared",
        "vehicle": {
          "id": "veh_abc123",
          "license_plate_number": "ABC-1234"
        }
      },
      "last_position": {
        "latitude": 41.8781,
        "longitude": -87.6298,
        "occurred_at": "2026-10-19T17:00:00Z"
      },
      "tracking_health": "good"
    }
    ```
  </Step>

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