> ## 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.17.0 - HOS Availability in Live Locations

> Vehicle live locations now include optional Hours of Service availability data

**Released 1st July 2026**

## HOS Availability in Live Locations

This release extends the vehicle live locations endpoint with optional Hours of Service (HOS) availability data, enabling you to surface driver compliance status directly alongside real-time vehicle telemetry.

<Check>
  **Backward-compatible addition:** All new fields are optional and only returned when `include_hos_availability=true`. Existing integrations are unaffected.
</Check>

### New features

<AccordionGroup>
  <Accordion title="HOS availability in vehicle live locations" icon="sparkles">
    `GET /v2/intelligence/analytics/vehicles/live-locations` now accepts an `include_hos_availability` query parameter. When set to `true`, each vehicle in the response includes the following additional fields:

    | Field | Description |
    | - | - |
    | `hos_id` | Identifier for the current HOS record |
    | `duty_status_code` | Current duty status of the driver (e.g., `ON_DUTY`, `DRIVING`, `OFF_DUTY`, `SLEEPER`) |
    | `hos_ruleset_code` | The HOS ruleset the driver is operating under |
    | `hos_occurred_at` | Timestamp when the current duty status began |
    | `shift_ends_at` | Timestamp when the driver's current shift expires |
    | `next_break_due_at` | Timestamp when the driver's next required break is due |
    | `available_drive_seconds` | Remaining drive time available in seconds |
    | `available_shift_seconds` | Remaining shift time available in seconds |
    | `available_cycle_seconds` | Remaining cycle time available in seconds |
    | `time_until_break_seconds` | Time remaining until the next required break in seconds |

    **Example request:**

    ```bash theme={null}
    GET /v2/intelligence/analytics/vehicles/live-locations?include_hos_availability=true
    ```

    **Example response (single vehicle item):**

    ```json theme={null}
    {
      "vehicle_id": "veh_abc123",
      "latitude": 41.8781,
      "longitude": -87.6298,
      "speed_mph": 62.4,
      "duty_status_code": "DRIVING",
      "hos_ruleset_code": "USA_60_7",
      "hos_occurred_at": "2026-07-01T14:00:00Z",
      "shift_ends_at": "2026-07-02T01:00:00Z",
      "next_break_due_at": "2026-07-01T17:30:00Z",
      "available_drive_seconds": 21600,
      "available_shift_seconds": 39600,
      "available_cycle_seconds": 172800,
      "time_until_break_seconds": 12600
    }
    ```

    Omit the parameter (or set it to `false`) to receive the original response without HOS fields — no changes to existing behavior.
  </Accordion>
</AccordionGroup>

***

## Need help?

<CardGroup cols={2}>
  <Card title="API reference" icon="book" href="/api-reference/telematics-api">
    View complete endpoint documentation with current API structure.
  </Card>

  <Card title="Contact support" icon="life-ring" href="mailto:support@catenaclearing.io">
    Questions about this release? Our team is here to help.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.