Integrate football probabilities, essential markets and structured pre-match data with free Developer or Starter.
Preview advanced data, with selected variables reserved for Starter.
Full Core Analytics for integrations that need more competitions, history and volume.
Compare Developer and Starter on the API plans page, then use the technical documentation as the integration reference.
Both plans use these routes. Server-side contract rights and the selected competition scope remain authoritative.
| Method | Route |
|---|---|
| GET | /v1/leagues |
| GET | /v1/leagues/{league_code}/matches |
| GET | /v1/matches/{match_id} |
| GET | /v1/matches/today |
| GET | /v1/picks/today |
| POST | /v1/matches/bulk |
GET /v1/health · GET /v1/me · GET /v1/me/usage
Responses may include availability. A starter_required entry means a variable belongs to the Starter contract and is not exposed to Developer. List responses stay compact and do not invent fields that only exist in analytics detail. elo_difference appears only in the relevant detail payload when it is actually available.
Developer provides 7 days of verified history and Starter up to 90 days. One request covers at most 31 days. history_available_from reports the depth actually published. Use include=past or include=all and follow next_cursor without changing the other parameters.
Send the key server-side only through X-API-Key. Developer accepts up to 5 matches per grouped request; Starter up to 100. Quota exhaustion returns 429 with available limit metadata. Never place a key in public JavaScript.
curl -H "X-API-Key: YOUR_API_KEY" \
"https://api.foresportia.com/v1/leagues/FIN/matches?include=all&days=7"2/min · 30/h · 50/day · 5 matches/grouped request · 100 rows/day
15/min · 500/h · 3000/day · 100 matches/grouped request · 10000 rows/day
The foresportia package handles authentication, typed responses, ETags, errors, cursor pagination and availability. Legacy beta keys remain compatible; the SDK never infers a plan from a key prefix.
pip install foresportia400/422 for invalid requests, 401 for a missing or invalid key, 403 for unavailable rights or competitions, 404 for an unknown resource, 409 for a business conflict, 429 for quota limits and 5xx for temporary unavailability.
Use the technical documentation and its LLM text versions when generating an integration. This page is an indexable overview; detailed schemas and payload examples remain canonical under /api/docs/.
Yes. Developer is an active free plan, explicitly provisioned after signing in to a Foresportia Account.
No. They share routes and authentication; rights, limits and available fields depend on the plan.
Not in Developer or Starter. Standard plans cover pre-match data and available verified historical results.
Keep the key server-side in a backend, script, bot or private environment variable.