An "aggregated averages" endpoint per team

Feature Request Football Won't Fix 🎖️ 5 Founder votes Sep 08, 2026 · srfcboy · 🥵 61 aura

An "aggregated averages" endpoint per team The biggest potential gain: Currently, to calculate an average ( xG, cards, corners ) based on a team's last 5 matches, we make 6 API calls (1 for the list + 5 for detailed stats). An endpoint like `/api/v2/teams/{id}/history-stats/?limit=5` that returns pre-calculated averages directly would reduce our call volume by a factor of 5 or 6 for several of our functions. Thanks

Comments

Bzzoiro · Admin Sep 11, 2026 15:44

Hi, Thanks, the use case is clear and so is the saving. There is no endpoint today that returns a team's averages over its last N matches, and I am not going to promise one. The ticket stays open as the request. Until then, the cheapest route on your side is to fetch each finished match's statistics once, cache them, and compute the averages locally, since a finished match rarely changes. Bzzoiro

Bzzoiro · Admin Sep 17, 2026 06:13

Hi, Still no, and I would rather say so once clearly than leave you waiting on it. We are not adding new endpoints to the football API on request. The saving you describe is real and the reasoning is sound, but an aggregated-averages route is a new surface to build, document, cache and keep correct across every stat we serve, and that is not where the time is going. What did change since my last reply: every endpoint now describes its full response body in the schema, so computing the averages on your side is at least no longer guesswork about which fields exist. The cheapest route is unchanged - fetch each finished match's statistics once, cache them, average locally. A finished match does not change, so that cache never needs invalidating. Staying open as the request. Bzzoiro