Some keys in 'stats' dict for Player object are numbers

[ostreon01001111]

I spent some time working backwards through the python code to find this, but some keys in the 'stats' dict are numbers rather than named. It would be helpful to know what these represent (or where they come from). I'm very curious to understand what they are.

Example: Lamar Jackson

{1: {'projected_points': 21.93,
'projected_breakdown': {'passingAttempts': 29.42747142,
'passingCompletions': 19.57216397,
'passingIncompletions': 9.855307454,
'passingYards': 235.1190702,
'passingTouchdowns': 1.840532493,
'5': 47.0, <------ ???
'6': 23.0,
'7': 11.0,
'8': 9.0,
'9': 4.0,
'10': 2.0,
'11': 3.0,
'12': 1.0, <------ ???
'passing40PlusYardTD': 0.187897253,
'passing50PlusYardTD': 0.122790855,
'passing300To399YardGame': 0.177428356,
'passing400PlusYardGame': 0.023965919,
'passing2PtConversions': 0.084506857,
'passingInterceptions': 0.593560007,
'passingCompletionPercentage': 0.665098394,
'rushingAttempts': 8.309834847,
'rushingYards': 51.58898176,
'rushingTouchdowns': 0.254203748,
'rushing2PtConversions': 0.009961347,
'27': 10.0, <------ ???
'28': 5.0,
'29': 2.0,
'30': 2.0,
'31': 1.0,
'33': 1.0, <------ ???
'rushing40PlusYardTD': 0.016410738,
'rushing50PlusYardTD': 0.011487517,
'rushing100To199YardGame': 0.116369401,
'rushing200PlusYardGame': 0.003971241,
'rushingYardsPerAttempt': 6.208183762,
'2PtConversions': 0.094468204,
'fumbleRecoveredForTD': 0.002505968,
'passingTimesSacked': 2.205078462,
'65': 0.451048355, <------ ???
'66': 0.118489889, <------ ???
'fumbles': 0.569538244,
'69': 0.21650321, <------ ???
'70': 0.054505349, <------ ???
'lostFumbles': 0.271008559,
'turnovers': 0.864568566,
'210': 1.0, <------ ???
'211': 11.15860679, <------ ???
'212': 2.55815856}, <------ ???
'projected_avg_points': 0},

[brikc]

Hi, I am also digging into player stats for my fantasy league. I'm curious which method did you call to get that output because my JSON response for Lamar Jackson (I was testing it for your question) is a bit different. Did you pull this with league.player_info(playerId=3916387) for 2024 season? Or via accessing the player through the roster?

I think the numbers that show up as keys have something to do with scoring settings for the league. Maybe if you have a certain scenario unchecked in your league, it comes across as a number. As an example, your payload includes:

passing300To399YardGame': 0.177428356

but mine does not, and I confirmed that I have that option unchecked in my league scoring settings. If I could get my payload to match yours we might be able to triangulate on the keys.

[ostreon01001111]

@brikc that would make sense! The method I used to retrieve Player instances was: players = league.free_agents(position='QB')

Then, players[0].stats, players[0].name, to look at a specific player's Player class attributes.

If you are using league.player_info(playerId:int), possible that info is sourced from a different endpoint in the ESPN API.

[brikc]

When I run those calls for 2024 player[0] that is returned is Jalen Hurts. It probably makes sense that the lists won't always been ordered the same. I did notice that when I access stats via roster versus player info (and now versus free_agents), different payloads are returned. I have only been able to get complete historical stats via the playerInfo call. If I get a chance to play around with league scoring toggles and comparing the payloads I will update here. I wonder if you change the toggles in league settings if it actually will send different values for historical or if it'd only be different go foward.

[ostreon01001111]

I ran players = league.free_agents(position='QB'), and this time players[0].name is Josh Allen. There appears to be some order to them, but it's unclear to me at this time what it is.

[ostreon01001111]

How are you executing the "playerInfo" call? I can pass:

league.player_info(playerId=3918298).stats

...and receive identical stats payload for Josh Allen (only gives me dict key '0' though - free_agents() will give me both dict keys '0' and '1': '0' appears to be 2025 season, '1' appears to be "Week 1").

[brikc]

I was looking at 2024 season stats. Here's the call I used for Lamar Jackson
league.player_info(playerId=3916387)

I actually just created a new league (so I wasn't messing with my actual league) and toggled on the checkboxes for ALL scoring, hoping it would fill in the random keys that are showing up as numbers. But it did not, the payload shows the same keys you called out in your original message. So I'm stumped. :)

And you're right, the top level 0, 1, 2, 3, 4 ... 18 etc all represent the stats for those weeks and I think 0 is season totals. If you pull 2024 (or a past season) you'll see those weeks but they're obvi not available for 2025.