College Football Stats in WordPress: NCAA Box Scores Are Now Live
The short version
If you looked into building a college football stats site earlier this year and gave up, look again. NCAA player stats weren’t available then. They are now.
Sports API Hub imports college football box scores across all three competitions the providers carry: Division FBS, Division FCS, and interdivisional games. Scores, schedules, and the per-player passing, rushing, receiving, defensive and kicking lines that make a stats site worth visiting.
That last part is the change. Everything else about American football support has been in the plugin since v1.2.3 shipped in April.
Why every guide still says “NFL only”
Because until recently it was true.
When I first probed the college endpoints in April 2026, requests for lineups and player statistics came back HTTP 204 – no content. Scores worked. Schedules worked. Player data didn’t exist.
That’s what the documentation said, that’s what every blog post and forum answer said, and that’s what I told people who asked. Then I re-probed while preparing the American football launch and got a completely different answer: a full lineup response, 40 players on one roster and 32 on the other, 67.7 KB of it, for a finished college game.
The coverage had expanded and nobody’s documentation had caught up. If you search for this today you will still mostly find pages telling you it can’t be done.
Sports API Hub imports it today. That gap between what’s actually available and what the internet believes is available is worth something to you, because it means a college site with real box scores has almost no competition right now.
The trap that keeps this hidden
There’s a specific reason this change went unnoticed for months, and it’s worth understanding even if you never write a line of code.
If you test an API’s coverage by asking about an upcoming game, you get HTTP 204 back. That’s correct behaviour – the game hasn’t been played, so there are no player stats to return. But that response is byte-for-byte identical to what you’d get from a league the provider doesn’t cover at all.
So the test looks conclusive and tells you nothing. Anyone who checked college coverage against next Saturday’s fixtures concluded it wasn’t supported, and they’d have concluded that whether it was supported or not.
Always probe a game that has actually finished. That single habit is the difference between knowing what your data source covers and guessing.
I mention it because it’s the kind of thing you shouldn’t have to think about. Sports API Hub already knows which competitions carry which endpoints – it was built by running exactly these probes, repeatedly, against finished games.
What you actually get
Three competitions, imported the same way as the NFL:
- Division FBS – the Football Bowl Subdivision, the tier most people mean by “college football”
- Division FCS – the Football Championship Subdivision
- Interdivisional – games between the two
For each finished game you get the box score: passing, rushing, receiving, fumbles, defensive, interceptions, kick returns, punt returns, kicking and punting, broken out per player. Plus the things that were always there – scores, fixtures and scoring summaries.
Both providers return identical college payloads. I checked that specifically before adding the second one, because a “supported” league that quietly returns thinner data on the cheaper plan would be a nasty surprise to discover in October.
Where the line still is
I’d rather you know the limits now than find them after you’ve built pages around them.
The CFL, the UFL and the European League of Football return no player data. Both providers answer 204 for lineups and statistics on all three. You get scores, schedules, standings and scoring summaries, which is enough for a results-and-table site and not enough for a stats site.
If your project is built on one of those leagues, the honest answer is that the data isn’t there yet – from anyone, not just from us. Coverage does change, as college just demonstrated, so it’s worth re-checking rather than treating today’s answer as permanent.
College has no standings feed. This is the one thing on this page you can’t have. Both providers publish standings for the NFL and the CFL, and answer 204 for all three college competitions. I probed the league id and both stage ids before writing that, and there is nothing to fall back on either – the feed models college as FBS, FCS and interdivisional, not as the Big Ten and the SEC, so there are no conference competitions to pull a table from. Records and results you do get, because those are calculated from the games themselves. A conference table is upstream work, not plugin work.
What WordPress already offers, and why it isn’t this
Search for a college football plugin and you’ll find two things.
The first is a sidebar widget that displays one team’s standings. It does that one job, it’s been sitting unchanged on the plugin directory for years, and it isn’t a stats site – it’s a box in your sidebar.
The second is SportsPress, which is a genuinely capable league manager and the right answer for a club running its own competition. But its import path is CSV: you go to Tools, choose an importer, and supply a file you got from somewhere else. There’s no API connection. For a college season that means you are still the data entry, you’ve just moved it into a spreadsheet first.
That gap is the whole reason Sports API Hub exists. The plugin isn’t competing to be a better league manager. It’s solving the part neither option addresses – getting real box scores in, on a schedule, without you touching them.
But isn’t some of this data free?
Some of it is, and I’d rather say so than have you find out afterwards. ESPN runs undocumented endpoints that return college box scores with no key at all.
Here’s what that actually buys you: the feed, and nothing else. No documentation, so a field changes shape with no changelog to read. No published rate limit, which also means none you’re entitled to rely on. No republishing rights, which matters far more for a commercial site than a personal one.
And the feed was never the hard part. You still need somewhere to put 100+ columns of player data, a scheduled job that runs when nobody is visiting, handling for postponed games, and templates for all of it. That’s weeks of work, and it’s work you maintain forever.
Sports API Hub is that entire layer, already built and already tested against these exact endpoints. Ten dollars a month against a build you’d own for the life of the site is not a close call.
Two providers, two price points
American football is the one sport where you have a genuine choice, and the cheaper option is not the worse one.
AmericanFootballApi – $9.99/month. American football only, including college. 15,000 requests per day. If college football is your site, this is the one to take.
AllSportsAPI2 – $19.99/month. All eight sports the API carries, unlimited requests, throttled to 6 per second. Worth the extra ten dollars only if you also run basketball or baseball – the plugin’s other two fully built-out sports.
Both carry NCAA. Both were probed against the same finished games before AmericanFootballApi was added in v1.3.2. Pick on whether you need basketball or baseball too, not on whether the football data differs, because it doesn’t.
AmericanFootballApi has a free Basic tier at 50 requests a day. It’s fine for confirming the plugin talks to the API. It will not import a season – a full NFL season alone runs 1,200 to 1,400 requests, and a college schedule is substantially larger than the NFL’s.
What you can build with it
This is the part that decides whether a stats site is worth visiting, so it’s worth being specific.
Team pages. Full schedule, results and season record, updated after every game. A visitor lands on your Michigan page in November and sees the current record, not something you last touched in September.
Game pages with the real box score. Every player who took a snap, broken out by passing, rushing, receiving, fumbles, defensive, interceptions, kick and punt returns, kicking and punting. This is the page that earns return visits, and it’s the page you cannot build without player-level data.
Player pages. Per-game lines and season totals, built from the same import. No separate data source, no reconciliation.
Division leaders. Passing, rushing, receiving, tackles, sacks and kicking leaders across the whole division, calculated from the games you imported.
Live scores. In-game updates during the Saturday window, if you want them.
Shortcodes for all of it. Drop any of the above into any page, post or widget. Your existing theme keeps its design – the plugin supplies the data and the markup, not a new look.
All of it comes from one import. You configure the competitions once and the plugin owns the schedule, the storage and the display from then on. The full setup walkthrough is in the NFL guide and nothing about it changes for college.
A note on running a college season
Two things behave differently from the NFL, and both are easier to plan for than to discover.
Volume. Your request budget scales with games played, not with how much you care about the league. FBS plays far more games than the NFL does, and adding FCS multiplies it again. Import the divisions you’ll actually publish rather than ticking every box on the first run, and check the result of one season before queuing several.
Timing. Saturdays are concentrated in a way Sundays are not – a large share of the week’s games finish inside a few hours. Schedule your import to run after that window rather than trying to keep pace with it, unless you specifically want live scores, which is a separate setting.
Who this is for
A good fit if: you run a program, conference or college football blog and you’re tired of typing box scores in by hand. Or you tried this earlier in 2026, hit the wall, and assumed it was permanent. Either way the setup is an afternoon, not a project – you add your API key, pick FBS, FCS or both, and run the import.
Not yet a fit if: your site is built on the CFL, UFL or ELF and you need player-level stats. Scores and standings work today; the rest doesn’t exist upstream.
FAQ
Is NCAA college football really supported now?
Yes, including full player box scores across FBS, FCS and interdivisional games. This changed during 2026 – if you read somewhere that American football means NFL only, that page is out of date.
Do I need the more expensive plan for college?
No. AmericanFootballApi at $9.99/month carries college, and its payloads match the $19.99 multi-sport plan. Pay more only if you also run basketball or baseball.
Can I import past seasons?
Yes, subject to what the provider holds and to your daily request budget. Import one season first and check the result before queuing several.
Why did my coverage test say there was no data?
Almost certainly because you tested an upcoming game. An unplayed fixture returns 204 whether or not the league is covered. Re-run the test against a game that has finished.
Do I get conference standings?
No – college is the one American football competition the providers publish no standings for. The NFL and the CFL return full tables; FBS, FCS and interdivisional return 204. Team pages still carry each team’s record and results, because those are calculated from the games rather than fetched.
What about the CFL and UFL?
Scores, schedules and standings work. Player statistics return 204 from both providers, so box scores aren’t available for those leagues yet.
Get Started
College football player stats are available now, most of the internet hasn’t noticed yet, and the season is already running. That’s a short window where a site with real box scores has very little competition.
Sports API Hub owns the import, the storage, the scheduling and the display. You bring an API key and pick your competitions – the rest is configuration, not development.
