College Football Data

Install corsair and @corsair-dev/collegefootballdata, add the College Football Data plugin, and connect with an API key. Then call methods like corsair.collegefootballdata.api.account.getUserInfo() from your app. Corsair syncs data per tenant.

Yes. College Football Data requires an API key from your College Football Data account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit College Football Data, GitHub, Notion, Stripe, and the rest. Trigger College Football Data from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for college football statistics api for games, teams, players, and historical ncaa data. Common builds include sync jobs, admin tooling, and agents that call College Football Data APIs from your backend. Local DB entities let you query synced College Football Data records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per College Football Data API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/collegefootballdata in the open repo. When College Football Data ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your College Football Data data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store College Football Data data on your behalf.