The GOAL API blog
Guides, tutorials and engineering notes for developers shipping live scores, webhooks and match data.
Three quirks in our own API used to be every integrator's problem. Now five first-party clients absorb them — npm, PyPI, pkg.go.dev, pub.dev and Packagist, all shipping 1.0.0.
GOAL API
A 10,000 request plan covers 4 matches if you poll and 200 if you use webhooks. Size your plan by matches tracked, with the arithmetic.
GOAL API
Every football API has a free tier. One caps you at 12 competitions, one at 2 leagues, one hides live scores. Here is exactly where each one ends.
GOAL API
Four vendors price football data four different ways. A 29 euro plan buys 5 leagues at one vendor and 1,019 at another. Here are the real numbers and the request math.
GOAL API
Four endpoints cover a full match page. Draw a 4-2-3-1 from the lineup data, read odds keyed by line, and know which fields go missing.
GOAL API
Your webhook URL is public. Without a signature check, anyone who learns the URL posts fake goals into your app. Six lines of code stop them.
GOAL API
Polling 20 matches costs 43,200 requests on a Saturday. A socket costs one connection. Here is which transport fits which job, with the request math.
GOAL API
Open one connection and receive goals as they happen. Token auth, match subscriptions, and the reconnect logic most teams forget until production breaks.
GOAL API
Most football APIs make you poll. We push match events to your server the second they land. Register an endpoint, handle the retry schedule, and cut hundreds of wasted requests per match.
GOAL API
