Update Frequencies

Intro

Each NASCAR API endpoint updates at a variable frequency, influenced by both caching behavior and underlying data updates.

For example, a race-centric feed such as the Race Leaderboard has a short cache interval while Standings has a longer cache duration, with data only updating when official results are published or standings are recalculated. During the offseason, many endpoints will not update at all.

Given API request limits and QPS constraints, these update patterns should be understood and factored into your pull strategy.

Use this page to help determine the most appropriate pull frequency for your integration needs.

Time-to-Live (TTL) and Data Updates

Understanding the distinction between TTL and data updates is crucial for designing an efficient and reliable NASCAR API solution. TTL is focused on the validity of cached data to optimize performance, whereas data updates are concerned with the actual data within the API.

Time-to-Live (TTL)

Time-to-Live (TTL) is a mechanism used to define the lifespan of data in a cache or network. It specifies the duration for which the data remains valid and can be reused. Once the TTL expires, the data may be stale and should be re-fetched.

You can find the TTL for each RESTful feed in the response header of a request under Cache-Control. A response of public, must-revalidate, max-age=300 signifies a time-to-live of 300 seconds.

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 NASCAR 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 NASCAR API endpoint, as well as our recommended pulling frequency.

Endpoint	TTL / Cache	Data Updates	Recommended Pull (Non-Live)	Recommended Pull (Live)
Daily Change Log	300 seconds	Entries populate every 20 minutes for changes to drivers, race data, statistics, schedules, tracks, and standings. Log window runs from 05:00:00 UTC to 04:59:59 UTC.	Pull every 10 minutes or less, depending on use case.	Not applicable
Driver Standings	2 seconds	Standings update within 2 minutes of a race moving to `closed`.	Pull on an as-needed basis.	Pull 2–5 minutes after an event moves to `closed` to receive the fastest updates.
Driver Statistics	2 seconds	Seasonal statistics update approximately 5 minutes after a race moves to `closed`.	Pull on an as-needed basis. Use the Daily Change Log to detect post-race updates.	Pull 5–10 minutes after an event moves to `initialized` to receive the fastest updates.
Drivers	2 seconds	Driver data updates on a ~5-minute interval after a race moves to `closed`.	Pull on an as-needed basis. Use the Daily Change Log to capture changes after a race has ended.	Pull 2–5 minutes after an event moves to `closed` to receive the fastest updates.
Entry List	2 seconds	Updates occur in near real time as the league modifies the entry list during race week. Typically 3–5 small adjustments occur over the week.	Pull on an as-needed basis. Can generally be ignored until race week.	Pull 5–10 minutes after an event moves to `initialized` to receive the fastest updates.
Manufacturer Standings	2 seconds	Standings update within 2 minutes of a race moving to `closed`.	Pull on an as-needed basis.	Pull 2–5 minutes after an event moves to `closed` to receive the fastest updates.
Owner Standings	2 seconds	Standings update within 2 minutes of a race moving to `closed`.	Pull on an as-needed basis.	Pull 2–5 minutes after an event moves to `closed` to receive the fastest updates.
Playoff Schedule	2 seconds	Schedule updates occur in real time as playoff details become available. Initial playoff schedule populates once the season structure is finalized.	Pull on an as-needed basis.	Pull every hour or less, depending on use case. This feed should be used for schedule data prior to race start.
Practice Leaderboard	2 seconds	Updates occur in near real time as drivers cross the start/finish line. Only recent crossings trigger updates.	Pull on an as-needed basis. Can generally be ignored until race week.	Pull 5–10 minutes after an event moves to `initialized`, then increase frequency when race status is `practice`.
Qualifying Leaderboard	2 seconds	Updates occur in near real time as drivers cross the start/finish line. Only recent crossings trigger updates.	Pull on an as-needed basis. Can generally be ignored until race week.	Pull 5–10 minutes after an event moves to `initialized`, then increase frequency when race status is `qualifying`.
Race Leaderboard	2 seconds	Updates occur in near real time as drivers cross the start/finish line. Only recent crossings trigger updates.	Pull on an as-needed basis. Can generally be ignored until race week.	Pull 5–10 minutes after an event moves to `initialized`, then increase frequency when race status is `warmup` or `inprogress`.
Rookie Standings	2 seconds	Standings update within 2 minutes of a race moving to `closed`.	Pull on an as-needed basis.	Pull 2–5 minutes after an event moves to `closed` to receive the fastest updates.
Schedule	2 seconds	Schedule updates occur in near real time as changes are made.	Pull every hour or less, depending on use case.	Not applicable
Seasons	2 seconds	New seasons appear as they are added. Season status updates on the day of the first event.	Pull on an as-needed basis.	Not applicable
Starting Grid	2 seconds	Updates occur in near real time during race week. Typically finalized after qualifying. If qualifying is canceled, updates occur once the grid becomes official.	Pull on an as-needed basis. Can generally be ignored until race week.	Pull 5–10 minutes after an event moves to `initialized` to receive the fastest updates.
Tracks	2 seconds	Updates occur in near real time as track details change.	Pull on an as-needed basis.	Not applicable