The whole API in one file

The manual in Markdown, OpenAPI, Postman and MCP, all generated from the same registry.

The manual, one Markdown file

Everything on these pages in one document: every guide, every endpoint with its parameters, its plan and a real sample answer, and the plans and limits. Read it offline, search it in one place, or hand the whole API to an assistant in one paste.

footballsoccerapi-manual.md

229 KB Markdown75 endpoints14 guidesUpdated 29 October 2026

You can download it hereSaves the file to your computer You can open it in the browserReads it in a new tab, nothing to install

Or from the command line

curl "https://footballsoccerapi.com/documentation/manual.md" -o footballsoccerapi-manual.md

No key needed. It rebuilds itself whenever these pages change, and the date above says when. Assistants that read a short map first can start at /llms.txt, which points here.

OpenAPI 3.1

The full surface as a spec you can generate a client from, in any language your toolchain supports. Regenerated on every release, so it cannot describe an endpoint that no longer exists.

curl "https://api.footballsoccerapi.com/v1/openapi.json" -o fsapi.json

Postman

A collection with every endpoint and example parameters filled in. Import it, paste your key into the api_key variable once, and every request in the collection fires.

curl "https://api.footballsoccerapi.com/v1/postman.json" -o fsapi.postman_collection.json

Optional filters arrive switched off rather than silently narrowing your first call.

MCP tools

The archive exposed as Model Context Protocol tools, so an assistant can query it without any glue code. Point it at the endpoint with your key and ask questions in words: how a club does at home after leading at half-time, and what the market paid at kickoff in those matches.

https://api.footballsoccerapi.com/mcp
# header: X-API-Key: your key

It is a curated set rather than all 75 endpoints: finding a competition, finding a club, matches, odds, standings, form, head-to-head, previews, league stats, price calibration and the backtest. An assistant handed fifty near-identical tools chooses badly, so it gets the ones worth asking a question about.

Open the endpoint in a browser and it lists the tools rather than returning a protocol error.

Why they cannot drift

All four are produced from one registry: the same file that drives the router, these documentation pages and the plan badges. There is no second list to keep in step, which is the usual reason an API spec ends up lying.

← Live odds Batch requests →