SplitsGame

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/sharpapi/main/json-schema/sharpapi-splits-game-schema.json",
  "title": "SplitsGame",
  "description": "Public betting splits for a single event from one source sportsbook.",
  "x-generated": "2026-10-14",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/sharpapi-openapi.json#/components/schemas/SplitsGame",
  "type": "object",
  "required": [
    "event_id",
    "sport",
    "league",
    "sportsbook"
  ],
  "properties": {
    "event_id": {
      "type": "string",
      "description": "Canonical event ID (joinable with /odds)"
    },
    "sport": {
      "type": "string"
    },
    "league": {
      "type": "string"
    },
    "sportsbook": {
      "type": "string",
      "enum": [
        "draftkings",
        "circa",
        "betmgm",
        "consensus"
      ],
      "description": "Source sportsbook for the splits data. `consensus` is a synthetic label, not a sportsbook: when every source covering an event posts identical numbers those rows are merged into one row tagged `consensus`, so a `sportsbook=draftkings` filter does not return them. It is accepted by this endpoint's `sportsbook` filter but never appears in /api/v1/sportsbooks."
    },
    "away_team": {
      "type": "string"
    },
    "home_team": {
      "type": "string"
    },
    "spread": {
      "type": "object",
      "description": "Spread market splits. NOTE: `away_odds` and `home_odds` here carry spread *line* values (e.g. -1.5/+1.5), not American odds. Field naming is a known inconsistency vs `/splits/history` which uses `away_line`/`home_line`.",
      "properties": {
        "away_odds": {
          "type": "number"
        },
        "home_odds": {
          "type": "number"
        },
        "handle_pct": {
          "type": "object",
          "description": "Share of money wagered on each side (0.0-1.0). Both members are `null` on `betmgm` rows: BetMGM publishes a ticket percentage only, so no handle figure exists to report. The keys are always present - only their values are null.",
          "properties": {
            "away": {
              "type": [
                "number",
                "null"
              ],
              "minimum": 0,
              "maximum": 1
            },
            "home": {
              "type": [
                "number",
                "null"
              ],
              "minimum": 0,
              "maximum": 1
            }
          }
        },
        "bets_pct": {
          "type": "object",
          "description": "Share of tickets wagered on each side (0.0-1.0). Members are `null` when the source has posted no percentage for this market; observed on `betmgm` rows, whose feed is intermittent. The keys are always present - only their values are null.",
          "properties": {
            "away": {
              "type": [
                "number",
                "null"
              ],
              "minimum": 0,
              "maximum": 1
            },
            "home": {
              "type": [
                "number",
                "null"
              ],
              "minimum": 0,
              "maximum": 1
            }
          }
        }
      }
    },
    "total": {
      "type": "object",
      "properties": {
        "line": {
          "type": "number"
        },
        "handle_pct": {
          "type": "object",
          "description": "Share of money wagered on each side (0.0-1.0). Both members are `null` on `betmgm` rows: BetMGM publishes a ticket percentage only, so no handle figure exists to report. The keys are always present - only their values are null.",
          "properties": {
            "over": {
              "type": [
                "number",
                "null"
              ],
              "minimum": 0,
              "maximum": 1
            },
            "under": {
              "type": [
                "number",
                "null"
              ],
              "minimum": 0,
              "maximum": 1
            }
          }
        },
        "bets_pct": {
          "type": "object",
          "description": "Share of tickets wagered on each side (0.0-1.0). Members are `null` when the source has posted no percentage for this market; observed on `betmgm` rows, whose feed is intermittent. The keys are always present - only their values are null.",
          "properties": {
            "over": {
              "type": [
                "number",
                "null"
              ],
              "minimum": 0,
              "maximum": 1
            },
            "under": {
              "type": [
                "number",
                "null"
              ],
              "minimum": 0,
              "maximum": 1
            }
          }
        }
      }
    },
    "moneyline": {
      "type": "object",
      "properties": {
        "away_odds": {
          "type": [
            "number",
            "null"
          ],
          "description": "American odds. `null` when the source has pulled the moneyline for this event while still publishing its split percentages; the key stays present."
        },
        "home_odds": {
          "type": [
            "number",
            "null"
          ],
          "description": "American odds. `null` when the source has pulled the moneyline for this event while still publishing its split percentages; the key stays present."
        },
        "handle_pct": {
          "type": "object",
          "description": "Share of money wagered on each side (0.0-1.0). Both members are `null` on `betmgm` rows: BetMGM publishes a ticket percentage only, so no handle figure exists to report. The keys are always present - only their values are null.",
          "properties": {
            "away": {
              "type": [
                "number",
                "null"
              ],
              "minimum": 0,
              "maximum": 1
            },
            "home": {
              "type": [
                "number",
                "null"
              ],
              "minimum": 0,
              "maximum": 1
            }
          }
        },
        "bets_pct": {
          "type": "object",
          "description": "Share of tickets wagered on each side (0.0-1.0). Members are `null` when the source has posted no percentage for this market; observed on `betmgm` rows, whose feed is intermittent. The keys are always present - only their values are null.",
          "properties": {
            "away": {
              "type": [
                "number",
                "null"
              ],
              "minimum": 0,
              "maximum": 1
            },
            "home": {
              "type": [
                "number",
                "null"
              ],
              "minimum": 0,
              "maximum": 1
            }
          }
        }
      }
    },
    "fetched_at": {
      "type": "string",
      "format": "date-time"
    },
    "available_metrics": {
      "type": "array",
      "description": "Which public-betting split metrics this row's sportsbook publishes AT ALL. This is a per-book declaration, not a description of the values this particular row happens to hold, and it is serialised in the order shown. Omitted entirely when SharpAPI has not declared what the book publishes: an absent field means 'not stated', never 'publishes nothing'. Read it together with the value - `handle_pct` listed while its members are `null` is a number we are missing, whereas `handle_pct` absent from this list while its members are `null` means the book does not publish money share. A synthetic `consensus` row carries the intersection of its contributing books, and omits the field if any contributor is undeclared.",
      "items": {
        "type": "string",
        "enum": [
          "bets_pct",
          "handle_pct"
        ]
      }
    }
  }
}