> ## Documentation Index
> Fetch the complete documentation index at: https://enterprise.predexon.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Live State

> Get one live score and game-state snapshot by sports game_id

## Overview

Returns one live game-state snapshot for a broad sports `game_id`.

Use this endpoint after discovering games from [`GET /v2/sports/games`](/api-reference/sports/games) or market listings from [`GET /v2/sports/markets`](/api-reference/sports/markets). Live state keys off `game_id`, not `event_id`, because many tradable markets can belong to the same real-world game.

<Info>
  For source reliability semantics, see [Sports Live State](/concepts/sports-live-state). For the websocket contract, see [Sports Live WebSocket](/api-reference/sports/live-websocket).
</Info>

## Path Parameters

| Param     | Type   | Description                      |
| --------- | ------ | -------------------------------- |
| `game_id` | string | Broad real-world sports game ID. |

## Query Parameters

| Param             | Type    | Default | Description                                       |
| ----------------- | ------- | ------- | ------------------------------------------------- |
| `include_sources` | boolean | `true`  | Include source-level snapshots under `sources[]`. |

## Event List

The response includes `significant_events[]`, a normalized list of key incidents when available. This can include score changes, cards, substitutions, period events, game start/end, or source-supported `other` events.

Incident availability depends on source and sport support. Kalshi soccer milestones commonly include goals, cards, substitutions, period events, and game-end events. Kalshi basketball can include made shots/free throws and period boundaries. Baseball play-by-play may be available for some games, but typed key incidents are less consistent. Polymarket primarily provides score, period, status, clock, and game-level state. If no key incidents are available for the game, `significant_events` is returned as `[]`.

## Example

`GET /v2/sports/live/mlb-ari-pit-2026-05-07`

```json theme={null}
{
  "game_id": "mlb-ari-pit-2026-05-07",
  "league": "mlb",
  "sport": "baseball",
  "game_date": "2026-05-07",
  "title": "Arizona Diamondbacks vs Pittsburgh Pirates",
  "home_team": null,
  "away_team": null,
  "participants": [
    { "code": "ari", "name": "Arizona Diamondbacks" },
    { "code": "pit", "name": "Pittsburgh Pirates" }
  ],
  "status": "open",
  "status_text": null,
  "live": false,
  "ended": false,
  "period": null,
  "clock": null,
  "score": {
    "home": null,
    "away": null,
    "display": null
  },
  "winner": null,
  "last_play": null,
  "significant_events": [],
  "reliability": {
    "state": "no_data",
    "source_count": 0,
    "sources": [],
    "conflict": false,
    "stale": true
  },
  "sources": [],
  "updated_at": null
}
```

## Reliability

| Field          | Description                                                                                      |
| -------------- | ------------------------------------------------------------------------------------------------ |
| `state`        | Aggregate source state, such as `no_data`, `single_source`, `confirmed`, `conflict`, or `stale`. |
| `sources`      | Direct source names used for the aggregate, such as `polymarket` or `kalshi`.                    |
| `source_count` | Number of source snapshots used for the aggregate state.                                         |
| `conflict`     | Whether sources disagree on material fields like score, status, or winner.                       |
| `stale`        | Whether the latest source data is stale or absent.                                               |


## OpenAPI

````yaml GET /v2/sports/live/{game_id}
openapi: 3.1.0
info:
  title: Predexon Enterprise API
  description: Unified cross-venue prediction market discovery
  version: 1.0.0
servers:
  - url: https://api.predexon.com
security:
  - apiKey: []
paths:
  /v2/sports/live/{game_id}:
    get:
      tags:
        - sports
      summary: Get Live State
      description: >-
        Get one sports live score and game-state snapshot by canonical sports
        game_id.
      operationId: get_live_state_v2_sports_live_game_id_get
      parameters:
        - name: game_id
          in: path
          required: true
          schema:
            type: string
          description: Canonical sports game ID.
        - name: include_sources
          in: query
          required: false
          schema:
            type: boolean
            default: true
          description: Include source-level live state snapshots.
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema: {}
              example:
                game_id: mlb-ari-pit-2026-05-07
                league: mlb
                sport: baseball
                game_date: '2026-05-07'
                title: Arizona Diamondbacks vs Pittsburgh Pirates
                home_team: null
                away_team: null
                participants:
                  - code: ari
                    name: Arizona Diamondbacks
                  - code: pit
                    name: Pittsburgh Pirates
                status: open
                status_text: null
                live: false
                ended: false
                period: null
                clock: null
                score:
                  home: null
                  away: null
                  display: null
                winner: null
                ended_at: null
                last_play: null
                significant_events: []
                reliability:
                  state: no_data
                  source_count: 0
                  sources: []
                  conflict: false
                  stale: true
                sources: []
                updated_at: null
        '404':
          description: Game not found
components:
  securitySchemes:
    apiKey:
      type: apiKey
      in: header
      name: x-api-key
      description: >-
        Data key provided by Predexon. The trading key used by the Order Router
        on trade.predexon.com is a separate credential.

````