canonical: https://jentic.com/apis/api-sports.io/api-sports # Api Sports API-Football v3 API-Football v3 from api-sports.io provides programmatic access to football (soccer) data covering 900+ leagues and cups, including fixtures, standings, players, coaches, transfers, injuries, predictions, and odds. Coverage includes real-time scores, pre-match and in-play odds, and team and player statistics. The 18 endpoints in this spec deliver the core surface for live scores, standings, player profiles, and predictions. Authentication is via the x-apisports-key header. ## For AI agents Pull live scores, standings, fixtures, player and team statistics, transfers, injuries, predictions, and odds from api-sports.io's football v3 surface. ## Scope Does not handle ticketing, fantasy league management, or non-football sports - use for football fixtures, standings, statistics, transfers, injuries, predictions, and odds only. ## Capabilities - Check the current account status and subscription tier with /status - List supported countries, seasons, and leagues for query-building - Retrieve fixtures filtered by league and season including live in-play matches - Get current and historical league standings with points, wins, draws, and losses - Look up team and player profiles, top scorers, transfers, injuries, predictions, and odds ## Use cases ### Live Scores Service Build a live football scoreboard by polling /fixtures with the live filter to surface in-progress matches with their period, score, and elapsed time. Pair the returned fixture id with /predictions and /odds for richer context. The api-sports.io listing is suited to direct subscribers who want to call the v3 host without going through RapidAPI. Example prompt: Call /fixtures with live=all and read the score, period, and elapsed time for each returned match ### Season Standings and Top Scorers Surface league tables and top scorer lists for editorial widgets, fantasy reminders, or analyst notebooks by calling /standings and /players together with consistent league and season parameters. The data feeds weekly recaps, season previews, and value-tracking tools across the 900+ supported leagues. Example prompt: Call /standings with league=39 season=2024 and /players with league=39 season=2024 type=topscorers and merge into a single team-and-player snapshot ### Transfer and Injury Watch Track squad changes by combining /transfers with /injuries for a tracked team. The pair gives an up-to-date view of incoming and outgoing players plus availability for the next fixture, which is core data for fantasy app reminders and editorial coverage of a club's selection problems. Example prompt: Call /transfers with team=541 and /injuries with team=541 to build a single availability report for Real Madrid's next fixture ### Agent Integration via Jentic An AI agent built on Jentic can search for the api-sports.io football operations by intent and execute them without holding the x-apisports-key in agent context. Jentic's your Jentic One instance holds the credential and returns scoped access at call time, which matters when the same agent needs to call both api-sports.io and other sports providers in the same workflow. Example prompt: Use Jentic search for 'get live football fixtures from api-sports', load the /fixtures operation, execute it with live=all, and return the in-progress matches ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /status | Check account status and quota | | GET | /fixtures | List fixtures filtered by league, season, team, or live status | | GET | /standings | Get league or cup standings for a season | | GET | /leagues | List supported leagues and cups | | GET | /teams | Look up team profiles and team statistics | | GET | /predictions | Get match predictions for a fixture | | GET | /transfers | List transfers by team or player | | GET | /injuries | List player injuries by team or fixture | ## Key resources - **Status** — Account status and subscription quota lookup via /status - **Reference Data** — Countries, seasons, leagues, and teams catalogues for query-building - **Fixtures and Standings** — Live and historical fixtures, standings by league and season - **Players and Teams** — Player and team profiles, top scorers, and transfers - **Predictions and Odds** — Match predictions and pre-match odds across leagues and rounds - **Injuries** — Current and historical player injury status ## Why Jentic - **Setup:** Wiring API-Football v3 by hand means handling its x-apisports-key header, targeting the v3 host, and mapping fixture, standings, transfer, and injury routes with their query parameters yourself. Through Jentic you install once, import API-Football from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** API-Football selects data through query parameters rather than resource ids in the URL path, so you limit the agent to the operations it needs, such as reading fixtures, standings, or injuries. Operations like predictions or odds are only available if you include them in the allowed set. - **Credential handling:** Your x-apisports-key is stored once, encrypted, by your own Jentic One instance and injected as the request header at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'get football league standings' or 'get live football fixtures', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **API-FOOTBALL** — RapidAPI listing of the same v3 football data surface - **Sportmonks Football API** — Football data provider with a different licence model and bookmaker mix - **TheSportsDB** — Open sports database covering teams, leagues, and events across multiple sports - **SportsData.io** — Multi-sport data provider including soccer, NFL, NBA, and others ## FAQ ### What authentication does API-Football v3 on api-sports.io use? Authentication is via the x-apisports-key header. When called through Jentic the key is held in your Jentic One instance and a scoped execution token is granted to the agent at call time, never the raw key. ### Can I get live in-play scores from api-sports.io? Yes. Call GET /fixtures with the live=all filter to receive only currently in-progress matches with their period, score, and elapsed time. Pair the returned fixture id with /predictions and /odds for richer context. ### What are the rate limits for api-sports.io football? Rate limits depend on your subscription tier on api-sports.io: free plans permit 100 requests per day, paid plans raise the daily ceiling and per-minute caps. Call GET /status to inspect your current quota and respect any 429 responses with exponential backoff. ### How do I get league standings through Jentic? Install the Jentic SDK with pip install jentic, search for 'get football league standings', load the GET /standings operation, and execute it with league and season parameters. Run it through Jentic One, the self-hosted execution layer to get a Jentic agent key. ### Does this API include predictions and odds? Yes. GET /predictions returns model-driven match probabilities for a fixture and the wider api-sports.io football surface includes pre-match and in-play odds for the same fixtures. Combine the two to compare model output with the bookmaker market. ### What's the difference between this and the api-football.com listing? Both expose the same v3 football data hosted at v3.football.api-sports.io. The api-sports.io listing is for direct api-sports.io subscribers using x-apisports-key, while the api-football.com listing is the RapidAPI surface using x-rapidapi-key. Pick whichever matches your subscription channel. ### Can I limit what my agent is allowed to do with the API-Sports Football v3 API? Yes. Because you run Jentic One yourself, your own rules decide which API-Sports Football operations and credentials the agent may use, so you can allow it to read only what it needs, such as fixtures, standings, or injuries. API-Football selects data through query parameters rather than resource ids in the URL path, which lets you scope access at the operation level rather than per record. Operations like predictions or odds are reachable only if you add them to the allowed set, and your stored x-apisports-key is injected at call time without ever entering the agent's context.