FOOTYQUANTA · API DOCUMENTATION
From your first fixture to the full game.
Explore 43 read-only endpoints, organized by use case. Find parameter types, requirements, defaults, response fields and JSON examples.
Explore the API referenceBrowse by resource
Fixtures, scores, events, lineups and match statistics.
Match analysis3Aggregated match overviews, previews and insights.
Competitions & seasons6Competition profiles, seasons, stages and knockout brackets.
Standings & rankings5League tables, qualification zones, competition statistics and leaderboards.
Teams8Team profiles, squads, form, transfers, honors and season performance.
Players & coaches7Player search, profiles, statistics, transfers, honors and coach profiles.
Odds & markets3Bookmakers, odds summaries and market snapshots.
Countries & venues2Country and region classifications and venue profiles.
1. Create an API key
Create an account, then generate a key in the console. The full key is shown only once. Store it in a server-side environment variable.
export FQ_API_KEY="fq_live_..."
2. Make a request
All endpoints use GET with an X-API-Key header. Base URL: https://api.footyquanta.com/v1/football.
curl 'https://api.footyquanta.com/v1/football/matches/today' \ -H "X-API-Key: $FQ_API_KEY"
const response = await fetch(`https://api.footyquanta.com/v1/football/matches/today`, {
headers: { "X-API-Key": process.env.FQ_API_KEY },
});
if (!response.ok) throw new Error(await response.text());
const body = await response.json();
console.log(body.data);3. Read the response
Successful responses have code: 0. data contains an object or array. Only paginated endpoints include meta. Application errors return data: null; query parsing errors use a plain-text 400 response.
{
"code": 0,
"message": "ok",
"request_id": "req_demo_001",
"data": [],
"meta": {
"page": 1,
"page_size": 50,
"total": 0
}
}Common conventions
| Convention | Details |
|---|---|
| Pagination | Only endpoints listing page/page_size accept them. Defaults: page 1, page_size 50. Maximum page_size: 100. The number of skipped records must not exceed 100000. |
| Batch IDs | Only endpoints listing ids accept batch lookups. Use up to 20 comma-separated IDs. Treat entity IDs as opaque strings. |
| Timezones | Omit timezone to use UTC. Only fixed UTC offsets are supported, not IANA names such as Europe/London. Encode + as %2B in URLs. |
| Missing data | null means missing or unavailable data. An empty array means no records were returned. Neither should be treated as zero. |
| Validation | Use only parameters listed for the endpoint. Unknown query parameters return 400. GET requests do not need a request body. |