> ## 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.99.0 - Load Stop Type

> New stop_type field added to intermediate stops on the visibility loads endpoint

**Released 15th October 2026**

This release adds a new optional `stop_type` field to intermediate stops on the `POST /v2/visibility/loads` endpoint, allowing callers to indicate the purpose of each stop along a load's route.

<Check>
  **Minor Release:** Backward-compatible addition. Existing integrations that omit `stop_type` are unaffected.
</Check>

## New Features

<AccordionGroup>
  <Accordion title="stop_type on intermediate load stops" icon="sparkles">
    **Updated endpoint:**

    * `POST /v2/visibility/loads`

    **What changed:**

    The `stops` array in both the request body and the `201` response now supports an optional `stop_type` field on each intermediate stop. This lets you describe what a stop is for — for example, a fuel stop or a rest break.

    **Request body — before:**

    ```json theme={null}
    {
      "stops": [
        {
          "latitude": 40.4406,
          "longitude": -79.9959,
          "name": "Pittsburgh, PA"
        }
      ]
    }
    ```

    **Request body — after:**

    ```json theme={null}
    {
      "stops": [
        {
          "latitude": 39.9976,
          "longitude": -78.2403,
          "name": "Pilot Travel Center, Breezewood, PA",
          "stop_type": "fuel"
        }
      ]
    }
    ```

    The `stop_type` field is also returned on each stop object in the `201` response, so callers can confirm the value was recorded.

    **Impact:**

    * `stop_type` is optional — omitting it behaves exactly as before
    * No changes to required fields or existing response structure
  </Accordion>
</AccordionGroup>

## Integration Notes

<Steps>
  <Step title="Add stop_type to intermediate stops (optional)">
    If you want to label what each stop is for, include `stop_type` in the stop object when creating a load:

    ```bash theme={null}
    POST /v2/visibility/loads
    Content-Type: application/json

    {
      "load_ref": "BOL-482910",
      "origin": { "latitude": 39.9612, "longitude": -82.9988, "name": "Columbus, OH" },
      "destination": { "latitude": 40.7357, "longitude": -74.1724, "name": "Newark, NJ" },
      "stops": [
        {
          "latitude": 39.9976,
          "longitude": -78.2403,
          "name": "Pilot Travel Center, Breezewood, PA",
          "stop_type": "fuel"
        }
      ],
      "estimated_departure_at": "2026-08-14T12:00:00Z",
      "estimated_arrival_at": "2026-08-16T08:00:00Z"
    }
    ```
  </Step>

  <Step title="No action required for existing integrations">
    The `stop_type` field is fully optional. Loads created without it continue to work without any changes.
  </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.