FotMob API: What Exists, and What to Use Instead
FotMob has never offered an official public API, so everything shared as a "FotMob API" is a wrapper around the app's internal endpoints — the ones FotMob locked behind signed requests. Here is what those routes are, how each fails in production, and a legitimate way to get the same football data.
curl https://api.5dollarfootballapi.com/v1/fixtures/{id}/statistics
-H "Authorization: Bearer fb_live_your_key"{
"success": 1,
"data": {
"fixture_id": 422841891,
"statistics": {
"attacks": { "home": 112, "away": 88 },
"shots_on_target": { "home": 7, "away": 4 },
"possession": { "home": 58, "away": 42 },
"first_half": {
"attacks": { "home": 47, "away": 40 },
"shots_on_target": { "home": 3, "away": 2 },
"possession": { "home": 55, "away": 45 }
}
}
}
}The short answer
FotMob has never offered an official public API. For years its app endpoints were open enough that dozens of GitHub wrappers and data projects quietly built on them — until FotMob began requiring signed request tokens, breaking those libraries overnight. That is the inherent risk of building on someone's internal API: they owe you nothing, and one deploy ends your product.
What people mean by "FotMob API"
Every route below reads the same undocumented endpoints the FotMob app calls (fotmob.com/api/...). None is a FotMob product, none issues an API key, and none comes with a licence to use the data.
| Route | What it is | Where it breaks |
|---|---|---|
| Internal endpoints | The JSON calls behind fotmob.com — matches by date, league tables, match details, player pages. | Undocumented and unversioned; since FotMob began requiring signed request headers, unsigned calls are rejected outright. Automated access is against their terms. |
| Community wrappers (fotmob-api and pyfotmob on PyPI, JavaScript and Ruby packages, a Raycast extension) | Volunteer packages that wrap those calls behind typed functions — some reproduce the request signature to keep working. | Every signing or schema change breaks them until someone patches the package; reproducing the signature is hostile access, not an integration. No SLA, no support, no commercial licence. |
| Marketplace "FotMob API" listings | Third-party scrapers sold as an API on parsing and data marketplaces, priced per request or per result. | The same terms-of-use and lock-out risk, now with a middleman: when FotMob changes something, your vendor is down too. |
| Tutorials: "extract FotMob data with Python" | Blog and notebook walkthroughs that call the endpoints directly for a one-off analysis. | Fine for a notebook, not for a product — most were written before request signing and no longer run as published. |
Why the unofficial route fails
- No official API or developer program exists, and FotMob's data comes from licensed providers such as Opta — they cannot resell it
- The unofficial endpoints now require signed headers; the wave of broken GitHub wrappers is the cautionary tale
- Workarounds that forge request signatures are explicitly hostile access — worse than plain scraping, legally and practically
- Even when the endpoints were open there was never a schema contract, SLA or changelog
The same data, the legitimate way
FotMob API seekers usually want live scores, fixtures, league tables and match stats in clean JSON. That exact shape is what a licensed football API serves:
| What you want | Our endpoint |
|---|---|
| Live scores & match status | GET /v1/fixtures?status=live |
| Fixtures by date or league | GET /v1/fixtures?start_time=&end_time= |
| League tables | GET /v1/standings?league=&season= |
| Match stats (shots, corners, cards) | GET /v1/fixtures/{id}/statistics |
| Odds for every fixture | GET /v1/fixtures/{id}/odds |
What you can build on instead
Frequently asked questions
No. FotMob has no public API or developer program. Its app endpoints were informally used by community projects for years, but FotMob has since locked them behind signed request tokens.
FotMob added a request-signing requirement to its internal endpoints, which broke unofficial libraries overnight. That is the standing risk of building on an internal API: there is no contract, and one deploy can end your integration.
No. FotMob does not issue API keys, because it has no API product. The signing token some wrappers compute is not a key — it is a reproduction of the app's own request signature, which FotMob can change at any time. A licensed football API gives you a real key, documented endpoints and a rate limit you can plan around.
There is none from FotMob. What exists are README files in community wrappers describing reverse-engineered endpoints, which go stale whenever the app changes. Our documentation covers every /v1 endpoint with parameters and sample responses, and stays current because it is the product.
Read the API docsA licensed football data API with the same core data — live scores, fixtures, standings, match statistics and odds. Ours starts free with no card and covers every major league from $5/mo.
Skip the scraper. Ship the product.
A licensed football API with live scores, stats and odds — free tier, no card, live in under a minute.