Self-Promotion
Show off what you're working on
Start new thread

I built GOAL API — a football data API with live scores, REST + WebSocket and 5 official SDKs

by•

Hey everyone, I've been building GOAL API, a football (soccer) data API aimed at developers. I kept hitting APIs that made me choose between coverage, real-time data, and a usable free tier, so I tried to do all three.

What it does:

Live scores, fixtures, results, standings, lineups, match stats, events and top scorers across 1,019 competitions in 184 countries.

REST for snapshots, plus a WebSocket you can subscribe to, so goals, cards and subs get pushed as they happen (no polling).

Five first-party SDKs (JS/TS, Python, Go, Dart/Flutter, PHP) released in lockstep, plus a public OpenAPI spec.

An MCP server, so you can wire live football data into Claude, Cursor or any AI agent.

Free plan, no credit card: generate a key and make your first call in about 2 minutes.

It's a small team and coverage grows weekly. I'd really value honest feedback on the docs, the data depth, or anything that would make it a drop-in for what you're building. If you've worked with sports data before, I'm especially curious what made past APIs painful.

Site and docs:

Thanks for reading!

2 views

Add a comment

Replies

Best

Push over WebSocket for goals and cards is so much nicer than polling every few seconds. Honestly my problem with APIs usually isn't the data. It's not knowing how much I've used. I've got alerts on my phone for every API I pay for once usage goes past a set number. If I could see usage per key right in your dashboard, I'd feel a lot better about building on the free plan.