Get the play-by-play of one game from the live API, one row per play.
Endpoint: GET https://live.euroleague.net/api/PlayByPlay?gamecode={game_code}&seasoncode={season_code}
The body carries one array per period (FirstQuarter, SecondQuarter,
ThirdQuarter, ForthQuarter (sic), ExtraTime) beside the two team names
and codes. The arrays are unrolled in game order with a leading quarter
column (1-4; 5 for every overtime period, which the body does not split
further) and the team_a / team_b / code_team_a / code_team_b header
fields repeated on every row. Team A is the home side as measured on one
game.
Arguments
- game_code
(integer required): Game number within the season (1-based; the
game_codecolumn ofeuroleague_games()).- season_code
(character required): Competition code + start year:
E2025(EuroLeague 2025-26),U2025(EuroCup).
Value
A hoopR_data tibble with one row per play.
Its columns are listed in return_columns
(subset(return_columns, fn == "euroleague_game_pbp")) and in the searchable
return columns article.
Details
Unofficial, keyless API, not supported by Euroleague Basketball; hoopR only wraps it. This function mirrors its sportsdataverse-py twin of the same name: same arguments, defaults and snake_case columns, one row per sportsdataverse-py row.
The live API's codes are space-padded fixed-width strings
(TEAM = "IST "); every string cell is stripped. Its "no such game"
answer is an empty 200 body, returned as a zero-row tibble with the
documented columns (not an error). A 404 raises hoopR_no_data, a 400 / 422
hoopR_invalid_request, any other failure hoopR_fetch_error (all inherit
hoopR_error).
See also
family_euroleague lists every function in this family.
