---
title: "Get Live Data"
method: GET
path: "/live_data/milestone/{milestone_id}"
tags: ["live-data"]
---

# Get Live Data

`GET /live_data/milestone/{milestone_id}`

## Request

- Base URL: `https://external-api.kalshi.com/trade-api/v2`
- URL: `https://external-api.kalshi.com/trade-api/v2/live_data/milestone/{milestone_id}`
- Auth: none declared

Get live data for a specific milestone. The response's `live_data.details.status` is updated far more often than the milestone's own `details.status` and is the preferred source for game status. It is not guaranteed to be current: if the provider feed falls behind, a cached board may still be served, with `live_data.details.live_data_delayed` set to `true` only once it is significantly stale (some feeds never set it), so a missing flag does not by itself mean the data is current.

## Path parameters

- `milestone_id` string, required

## Query parameters

- `include_player_stats` boolean

## Response `200`

Live data retrieved successfully

- GetLiveDataResponse
  - `live_data` LiveData, required
    - `type` string, required: Type of live data
    - `details` object, required: Live data details as a flexible object
    - `milestone_id` string, required: Milestone ID

## Other responses

- `404`: Live data not found
- `500`: Internal server error

## Changes

- **2026-04-13** `218c1f661cbd`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/kalshi/apis/kalshi-trade-api-manual-endpoints/changes/live_data/milestone/:milestone_id/get.md)

---

[API](https://skmtc.dev/kalshi/apis/kalshi-trade-api-manual-endpoints.md) - [All operations](https://skmtc.dev/kalshi/apis/kalshi-trade-api-manual-endpoints/llms.txt) - [OpenAPI document](https://skmtc.dev/kalshi/apis/kalshi-trade-api-manual-endpoints/revisions/e6691cdd1915?raw)