Hi all,<\/p>\n
I\u2019m currently using API-Football<\/strong> and I\u2019m running into a fundamental issue with how player IDs and stats<\/strong> work, and I\u2019m trying to understand if this is just how the API is designed or if I\u2019m missing something.<\/p>\n The core problem is that a player ID is not sufficient on its own to reliably fetch stats<\/strong>.<\/p>\n In practice, player stats only resolve correctly when combined with team + competition + season<\/strong>, but the API treats Because of this, you can\u2019t safely persist just a On top of that, stats tend to default to the \u201clatest\u201d season, competition filtering isn\u2019t always clean, and aggressive caching feels mandatory due to rate limits.<\/p>\n My question is:<\/p>\n Any insights from people who\u2019ve dealt with this would be hugely appreciated.<\/p>\n<\/div>\n submitted by \/u\/Thin_Road_88 <\/a> player_id<\/code> as if it\u2019s globally usable. This leads to several issues:<\/p>\n\n
player_id<\/code> alone often returns empty or incomplete results<\/li>\nplayer_id<\/code> and query it later. You effectively need a compound key like (player_id, team_id, season, competition)<\/code>, which makes generic or long-term player tracking very brittle \u2014 especially if you don\u2019t already know where the player was playing in a given season.<\/p>\n\n
[link]<\/a><\/span> [comments]<\/a><\/span><\/p>
