> ## 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.111.0 - Load Tracking Stops

> New stops field added to load tracking endpoint responses

**Released 19th October 2026**

This release adds a new required `stops` field to the response schemas for both load tracking endpoints. The field lists the load's stops in travel order. Estimated and actual arrival and departure times are not yet populated and are always `null`.

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

## Schema Changes

<AccordionGroup>
  <Accordion title="stops 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 `stops` field. The field lists the load's stops in travel order. The endpoint descriptions have been updated to reflect this: *"Each load also lists its `stops` in travel order. Their estimated and actual arrival and departure times are not populated yet, so they are always null."*

    **Before:**

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

    **After:**

    ```json theme={null}
    {
      "vehicle_assignment": {
        "source": "declared",
        "vehicle": { "..." }
      },
      "last_position": { "..." },
      "tracking_health": "good",
      "stops": [
        {
          "stop_type": "pickup",
          "estimated_arrival_at": null,
          "actual_arrival_at": null,
          "estimated_departure_at": null,
          "actual_departure_at": null
        }
      ]
    }
    ```

    **Impact:**

    * `stops` is a new required field in the response schema for both endpoints
    * Stops are listed in travel order
    * `estimated_arrival_at`, `actual_arrival_at`, `estimated_departure_at`, and `actual_departure_at` are always `null` at this time
    * Integrations that do not read `stops` require no changes
  </Accordion>
</AccordionGroup>

## Integration Notes

<Steps>
  <Step title="Read stops alongside other load tracking fields">
    The `stops` array is present on every load tracking response. Each entry represents a stop in travel order:

    ```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",
      "stops": [
        {
          "stop_type": "pickup",
          "estimated_arrival_at": null,
          "actual_arrival_at": null,
          "estimated_departure_at": null,
          "actual_departure_at": null
        }
      ]
    }
    ```
  </Step>

  <Step title="No action required for existing integrations">
    The `stops` 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.