The CFBD API v2 is now publicly available! The free tier has been set at 500 monthly calls (tiering and call limits subject to change). Documentation is available at apinext.collegefootballdata.com. As previously announced, API v1 will be shut down prior to the start of the 2025 season. No specific date has been set, but this is tentatively planned for Spring 2025. When that happens, both api.collegefootballdata.com and apinext.collegefootballdata.com will point to v2.
To reiterate what has already been announced, there WILL be breaking changes, so it is recommended to check out the docs and update your code at your earliest possible convenience. Current API limits are as follows:
Free tier – 500 monthly calls
Patreon Tier 1 ($1/mo) – 5000 monthly calls
Patreon Tier 2 ($5/mo) – 30,000 monthly calls
Patreon Tier 3 ($10/mo) – 75,000 monthly calls (+ access to the GraphQL API with realtime data subscriptions)
These tiers and limits are subject to change prior to the 2025 season. More tiers will be added as needed. If you need more than 75k monthly calls, reach out ot me and I will add more tiers.
Unlike REST API v1, there is no request throttling in REST API v2. This was done in favor of monthly limits to make things more transparent and easier to communicate and implement. However, not that Cloudflare limits are still in place and if you make a ton of simultaneous requests, you may be blocked by Cloudflare for a short period of time (~10mins).
There are multiple ways to access REST API v2:
Read the API docs at apinext.collegefootballdata.com
Install the pre-release version of the official Python package. (NOTE: you must explicitly install the prerelease version of the package. Refer to documentation on the next branch of the GitHub repo.)
Install the new TypeScript package.
There will be a .NET package and I am exploring adding support for additional languages. Those timelines are TBD.
Subscribers in Patreon Tier 3 receive access to the new GraphQL API with realtime data subscriptions.
REST API v2 and the new GraphQL API should still be considered to be in beta. Please do not hesitate to reach out if you run into any potential bugs or issues.
