API-Sports

Install corsair and @corsair-dev/apisports, add the API-Sports plugin, and connect with an API key. Then call methods like corsair.apisports.api.afl.getAflGamePlayerStatistics() from your app. Corsair syncs data per tenant.

Yes. API-Sports requires an API key from your API-Sports 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 API-Sports, GitHub, Notion, Stripe, and the rest. Trigger API-Sports from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for sports data api covering fixtures, standings, statistics, and live scores worldwide. Common builds include sync jobs, admin tooling, and agents that call API-Sports APIs from your backend. Local DB entities let you query synced API-Sports 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 API-Sports 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/apisports in the open repo. When API-Sports 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 API-Sports data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store API-Sports data on your behalf.