Skip to content

ESPN Fantasy Football API

ESPN Fantasy Football in Spring Boot: Live Scoring and Projected Ceilings

Quickly reviewing what I learned looking through the API.

In the in-match api return for an active week, i.e. scoringPeriodId is set to the current week, and our view contains mBoxScore, mScoreBoard, mLiveScoring, mMatchupScore, we'll get each team's active roster, current total projected points, and current live points. In each roster spot, we'll get two different stat objects, one representing the original projection and one the live stats. In the original projection, it's important to note that we have a appliedTotalCeiling value, we'll need that.

ESPN Fantasy Football in Spring Boot: Roster IDs and Composite Keys

I've written a lot of the SpringBoot project so far, but I wanted to start taking a few notes as I go.

Roster IDs

Many of the entities that I have created by nature have composite IDs. The composite primary key design of RosterEntry could be a little tricky because you need to decide which field provides uniqueness to the instance, i.e. is it lineupSlotId (and Team) or is it playerId (and Team). If it's the former, then really your primary key could be the playerPoolEntry field, as this is already unique to the Team and league. To determine this, we need to determine if the RosterEntry is predicated on the slot itself, or the players within the Roster. If I move some players out of their starting positions, this will create additional slots. However, the roster entry array size does not change when queried from

Uncovering the ESPN Fantasy Football API: Game Cast API

Today I finished up the basic game cast api that is used when you click on the game cast for a matchup. The thing I care most about here is the percentComplete field for each event because I think that will definitely help with the matchup win probability field. I can query that for each player by using the player's team id and cross referencing which event that competetitor is in and see the percent complete.