Update Frequencies

Intro

Each NCAAFB API endpoint updates at a variable frequency, in terms of both its cache and its data.

For example, a Game endpoint may have a 3-second cache during a live game. After the game concludes, this shifts to a 600-second cache, and after seven days, to 30 minutes. Alternatively, a Standings endpoint may have a 10-minute cache, with the data updating when games conclude.

Given your limited amount of API requests and QPS, these frequencies should be understood and factored into your pull rate.

Use this section to help determine the best pull frequency for your needs.

Time-to-Live (TTL) and Data Updates

Understanding the distinction between TTL and data updates is crucial for designing an efficient and reliable NBA API solution. TTL is focused on the length of time an object is cached, whereas data updates are concerned with the actual data within the API.

Time-to-Live (TTL)

Time-to-Live (TTL) defines the maximum duration a response may be served from cache before revalidation. TTL values are returned in the Cache-Control header for each REST feed. For example:

Cache-Control: public, must-revalidate, max-age=300

This indicates a TTL of 300 seconds.

TTL is an upper bound, not a guarantee. When underlying event data changes, our system proactively invalidates and replaces the cached object immediately, even if the TTL has not expired.

Data Updates

Data updates refer to the changes made to the underlying data that the API provides access to. This can occur through various operations such as creating, updating, or deleting our sports data.

Data updates are critical to ensuring that the API delivers the most current and accurate information. Data entry workflows and processes specific to NCAA Football data will affect your suggested request frequency.

Additional Frequency Resources

Visit our Headers documentation to learn how to interpret and use header responses to access the freshest sports data.

Frequency Chart

What is the right request frequency for your use? Which endpoints should you pull to get the most efficient use of your allotted calls?

The below chart provides answers to these questions, with a breakdown of the cache and data updates for every NCAAFB API endpoint, as well as our recommended pulling frequency.

Endpoint	TTL / Cache	Data Updates	Recommended Pull (Non-Live)	Recommended Pull (Live)
Current Season Schedule	10 minutes when payload includes active games (games in non-`closed` status) 60 minutes when no active games	Hourly A new season begins on the date of the first game of a season.	Pull every hour or less, depending on your use case. Note that this feed should be used for schedule info prior to a game start. For status of a live game, reference a "game" endpoint.	Not applicable Use this feed for non-live schedule retrieval only.
Current Week Schedule	10 minutes when payload includes active games (games in non-`closed` status) 60 minutes when no active games	Hourly New weeks begin when the first game of a week is moved to `created` status. See our Weekly Data Entry section for typical status updates.	Pull every hour or less, depending on your use case. Note that this feed should be used for schedule info prior to a game start. For status of a live game, reference a "game" endpoint.	Not applicable Use this feed for non-live schedule retrieval only.
Daily Change Log	4 hours	Entries populate live for changes to teams, players, game statistics, schedules, and standings. Start time of the log is 05:00:00 UTC; end time is 04:59:59 UTC	Pull every ten minutes or less, depending on your use case.	Not applicable
Game Boxscore	60 seconds when a game is in `scheduled` status 3 seconds when a game moves to `inprogress` 600 seconds when a game moves to `closed` 30 minutes when seven days have passed since `closed`	Realtime	Pull on an as-needed basis. Feed can be ignored until 10 minutes before the scheduled game start, depending on your use case. Utilize the daily change log to capture data changes after a game has ended.	Can request as fast as every 3 seconds (matching the TTL) when a game is live. Game feeds should be requested 10 minutes before the scheduled start. Use the `expected_latency` field to determine how many this feed may lag behind live play.
Game Play-by-Play	60 seconds when a game is in `scheduled` status 3 seconds when a game moves to `inprogress` 600 seconds when a game moves to `closed` 30 minutes when seven days have passed since `closed`	Realtime	Pull on an as-needed basis. Feed can be ignored until 10 minutes before the scheduled game start, depending on your use case. Utilize the daily change log to capture data changes after a game has ended.	Can request as fast as every 3 seconds (matching the TTL) when a game is live. Game feeds should be requested 10 minutes before the scheduled start. Use the `expected_latency` field to determine how many this feed may lag behind live play.
Game Roster	60 seconds when a game is in `scheduled` status 3 seconds when a game moves to `inprogress` 600 seconds when a game moves to `closed` 30 minutes when seven days have passed since `closed`	Realtime	Pull on an as-needed basis. Feed can be ignored until 10 minutes before the scheduled game start, depending on your use case. Utilize the daily change log to capture data changes after a game has ended.	Can request as fast as every 3 seconds (matching the TTL) when a game is live. Game feeds should be requested 10 minutes before the scheduled start. Use the `expected_latency` field to determine how many this feed may lag behind live play.
Game Statistics	60 seconds when a game is in `scheduled` status 3 seconds when a game moves to `inprogress` 600 seconds when a game moves to `closed` 30 minutes when seven days have passed since `closed`	Realtime	Pull on an as-needed basis. Feed can be ignored until 10 minutes before the scheduled game start, depending on your use case. Utilize the daily change log to capture data changes after a game has ended.	Can request as fast as every 3 seconds (matching the TTL) when a game is live. Game feeds should be requested 10 minutes before the scheduled start. Use the `expected_latency` field to determine how many this feed may lag behind live play.
League Hierarchy	4 hours	Hierarchy updates appear as they are updated in the database.	Pull daily or less, depending on your use case.	Not applicable
Player Profile	30 minutes	Seasonal stats update around 5 minutes after a game moves to `closed`	Pull on an as-needed basis. Utilize the daily change log to capture data changes after a game has ended.	Pull 5-10 mins after a game is moved to `closed` to receive the quickest updates
Postgame Standings	10 minutes	Standings update within 2 minutes of each game moving to `complete`	Pull every hour or less, depending on your use case.	Pull 2-5 mins after a game moves to `complete` to receive the quickest updates
Rankings (By Week)	4 hours	Rankings update within 15 minutes after their release to the public, typically on Sundays. The CFP rankings begin after week 10, and are typically released on Tuesdays.	Pull every hour or less, depending on your use case.	N/A
Rankings (Current Week)	4 hours	Rankings update within 15 minutes after their release to the public, typically on Sundays. The CFP rankings begin after week 10, and are typically released on Tuesdays.	Pull every hour or less, depending on your use case.	N/A
Season Schedule	10 minutes when season includes active games (games in non-`closed` status) 4 hours when no active games	Schedule info updates in realtime as changes are made.	Pull every hour or less, depending on your use case. Note that this feed should be used for schedule info prior to a game start. For status of a live game, reference a "game" endpoint.	Not applicable
Seasonal Statistics	30 minutes	Seasonal stats update around 5 minutes after a game moves to `closed`	Pull on an as-needed basis. Utilize the daily change log to capture data changes after a game has ended.	Pull 5-10 mins after a game is moved to `closed` to receive the quickest updates
Seasons	4 hours	New seasons appear as they are added to the database.	Pull on an as-needed basis.	Not applicable
Team Roster	30 minutes	Updates in realtime as changes are made to rosters or player profiles.	Pull on an as-needed basis.	Not applicable
Teams	4 hours	New teams appear as they are added to the database.	Pull on an as-needed basis.	Not applicable
Tournament List	4 hours	Each NCAAFB Playoff `tournament` entry is available shortly after the regular season schedule is released.	Pull on an as-needed basis.	Pull daily or less, depending on your use case.
Tournament Schedule	4 hours	Schedule info updates in realtime as changes are made. The initial playoff schedule (with TBD matchups) will be available shortly after the regular season schedule is released. Teams advance to the next round on a 2-minute timer after the previous game moves to `complete` status.	Pull on an as-needed basis.	Pull every hour or less, depending on your use case. Note that this feed should be used for schedule info prior to a game start. For status of a live game, reference a "game" endpoint.
Tournament Summary	4 hours	Schedule info updates in realtime as changes are made. Brackets and seeds are available shortly after they are made official.	Pull on an as-needed basis.	Pull daily or less, depending on your use case.
Transfer Portal	4 hours	Transfer portal updates appear as they are updated in our database.	Pull on an as-needed basis.	Not applicable
Weekly Schedule	10 minutes when week includes active games (games in non-`closed` status) 4 hours when no active games	Schedule info updates in realtime as changes are made.	Pull every hour or less during the current week, depending on your use case.	Not applicable

🏈
Important Note
Pull recommendations are based on a typical customer's needs. We suggest starting with our recommended rate and adjusting as necessary according to your needs.