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

# Players

> Get a player by ID, and find player IDs from team rosters, player prop markets and market participants

## Overview

The players endpoint returns metadata for individual players, including name, position, team association, and sport.

***

## Endpoints

> [accordion] GET /api/v2/players/\{playerID} — Get a player by ID
>
> Returns details for a single player.
>
> ### Path Parameters
>
> | Parameter | Description |
> | - | - |
> | `playerID` | Numeric player ID |
>
> ```bash cURL theme={null}
> curl --fail-with-body -H "X-TheRundown-Key: $THERUNDOWN_API_KEY" "https://therundown.io/api/v2/players/15954"
> ```
>
> ```bash Header Auth theme={null}
> curl --fail-with-body -H "X-TheRundown-Key: $THERUNDOWN_API_KEY" \
>   "https://therundown.io/api/v2/players/15954"
> ```
>
> ```python Python theme={null}
> import os
> import requests
>
> resp = requests.get(
>     "https://therundown.io/api/v2/players/15954",
>     headers={"X-TheRundown-Key": os.environ["THERUNDOWN_API_KEY"]},
>     timeout=15
> )
> resp.raise_for_status()
> player = resp.json()["players"][0]
> print(f"{player['display_name']} — {player['position']} — #{player['jersey']}")
> ```
>
> ```javascript Node.js 22+ (server) theme={null}
> const API_KEY = process.env.THERUNDOWN_API_KEY;
> if (!API_KEY) throw new Error("Set THERUNDOWN_API_KEY in the Node.js server environment");
> const resp = await fetch(
>   "https://therundown.io/api/v2/players/15954",
>   { headers: { "X-TheRundown-Key": API_KEY } }
> );
> if (!resp.ok) throw new Error(`Player request failed: HTTP ${resp.status}`);
> const { players: [player] } = await resp.json();
> console.log(`${player.display_name} — ${player.position} — #${player.jersey}`);
> ```
>
> ### Example Response
>
> ```json theme={null}
> {
>   "players": [
>     {
>       "id": 15954,
>       "sport_id": 4,
>       "team_id": 11,
>       "updated_at": "2026-10-15T13:42:53Z",
>       "first_name": "Onyeka",
>       "last_name": "Okongwu",
>       "display_name": "Onyeka Okongwu",
>       "weight": 240,
>       "height": 82,
>       "display_weight": "240 lbs",
>       "display_height": "6' 10\"",
>       "age": 25,
>       "date_of_birth": "2000-12-11T08:00Z",
>       "slug": "onyeka-okongwu",
>       "jersey": "17",
>       "position": "Forward",
>       "position_abbreviation": "F",
>       "birth_place_city": "Chino",
>       "birth_place_country": "USA",
>       "experience_years": 0,
>       "active": true,
>       "status": "Active"
>     }
>   ]
> }
> ```

***

## Finding Player IDs

Player IDs appear in several places throughout the API:

1. **Team roster** -- `GET /api/v2/teams/{teamID}/players` returns all players with their IDs
2. **Player prop markets** -- When fetching events with player prop `market_ids` (e.g., `29` for Player Points), each market participant's `id` is the player ID when its `type` is `TYPE_PLAYER`
3. **Market participants** -- `GET /api/v2/markets/participants` returns participant details for specified markets. On this endpoint the player ID is the `participant_id` field, not `id`

> [!NOTE]
>
> Player IDs are stable and consistent across endpoints. A player's ID from the team roster is the same ID used in prop market participants and stats endpoints.

***

## Related Endpoints

For player statistics, use these endpoints instead:

| Endpoint | Description |
| - | - |
| `GET /api/v2/teams/{teamID}/players/stats` | Season stats for all players on a team |
| `GET /api/v2/events/{eventID}/players/stats` | Game-level player stats for an event |

For live player box-score changes, bootstrap from the player game-stats endpoint and then subscribe to the [`stats` channel](https://docs.therundown.io/api-reference/v2/websocket#game-stats-messages). Each WebSocket frame contains only rows whose values changed.


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