Skip to main content

Overview

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

Endpoints

Returns details for a single player.

Path Parameters

Example Response


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
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.

For player statistics, use these endpoints instead: For live player box-score changes, bootstrap from the player game-stats endpoint and then subscribe to the stats channel. Each WebSocket frame contains only rows whose values changed.