A big match count means little if the possession field is missing where it matters.
A cup tie appears in a football app’s fixture list, but its possession panel is empty. The API returned the match; it did not return that statistic. The same gap can surface when a newly added league starts appearing in an otherwise reliable feed.
Before choosing a plan, check possession coverage, not just fixture coverage. Test a sample of the competitions the app displays, including cup rounds, and check whether possession is available live, only after full time, or not at all. An inexpensive subscription may still be costly if missing values require manual fixes or leave users staring at blank panels.
A provider can list “possession” without supplying the version a product needs. A final home/away percentage works for a match recap, but it cannot show when control changed. Half-by-half percentages show whether the balance shifted after halftime; they should be separate fields, not figures inferred by splitting the full-match number.
Live values are another commitment. Check whether the API returns a current cumulative percentage, timestamped historical snapshots, or both—and how often values refresh. An endpoint that overwrites its previous reading cannot produce a possession chart unless snapshots are stored locally.
Event feeds describe passes, touches, or recoveries, not necessarily possession time. Those records can support custom measures, but the result depends on the calculation method. The guide to football possession data provides context for choosing the measure a display needs.
Before comparing plans, request a written field and definition specification covering match and period fields, live updates, event availability, and how possession is calculated. Ask how stoppages, contested balls, rounding, and post-match corrections are handled; identical-looking percentages may not be directly comparable.
Build a fixture list from the seasons and divisions the project needs, including lower-profile matches. Query each match for a possession value; a competition appearing in the catalog is not proof that its fixtures have one.
Test early rounds and smaller-club ties as well as later matches. Cup coverage may vary by round, even when the competition is listed as supported.
Do not assume coverage follows the equivalent men’s senior league. Sample the specific women’s and youth competitions, seasons, and fixtures the project will use.
Include postponed, abandoned, awarded, and replayed fixtures where relevant. Check whether a missing value reflects the match status or an unexplained gap in an otherwise completed fixture.
A possession figure can be available during a match without being ready for a report. In-play values may change at each refresh; a figure shown at full time may still be provisional; and the archived value may be corrected later. Buyers should check whether the API identifies those states or merely overwrites the same field.
For a live display, ask how often possession is recalculated and how long it typically takes to reach the API. A feed polled every 15 seconds is not necessarily fresh if its source updates several minutes late. Watch a representative match and record the time between a visible match event, a status change, and the corresponding API response.
Match status matters just as much as the percentage. Check what happens at half-time, full-time, extra time, abandonment, and postponement: does possession freeze, disappear, or continue to change? A next-day report needs a reliable point at which figures can be treated as settled, while an archive needs a way to detect later revisions. Compare the same fixture immediately after full time, the following morning, and a week later. If values change, look for a revision timestamp or plan to refresh stored records.
Use a trial key to request several representative matches. Confirm that possession appears in a usable response, rather than only in documentation or a dashboard, and note how many requests it takes to retrieve it.
Check that fixture, team, competition, and season identifiers remain consistent across the fixture and statistics endpoints. A percentage is less useful if matching it to the correct game requires manual cleanup.
Compare a completed match with a postponed match and one whose statistics are unavailable. Check whether the API distinguishes a missing field, a null value, and zero; treating them as equivalent can corrupt reports.
Request enough fixtures to trigger pagination and observe page sizes, rate limits, and any 429 response or retry guidance. A low request allowance may make historical imports or frequent updates expensive.
Try an invalid fixture ID and an expired or invalid key to see whether errors are actionable. Fetch a completed match again later to check whether corrected possession values and update timestamps can be detected.
Look for working examples, clear field definitions, a usable sandbox, and support for trial accounts. Sparse documentation can turn an inexpensive plan into a costly integration.
A match-statistics endpoint may bundle possession percentage with shots, corners, and fouls. That can be enough for a results page or a simple comparison of how much of the ball each team had. It does not show how a team kept possession.
Pass-level or event data records individual actions, often with timestamps, locations, outcomes, and player IDs. It can support questions such as whether a team completed passes in its defensive third or lost the ball soon after gaining it. But a pass feed alone does not establish that an opponent applied pressure: that requires reliable pressure labels or, for proximity-based analysis, tracking data. The data needed to measure pressing resistance is therefore more specific than the data needed to display a possession figure.
Before paying for an event tier, write down the exact question the product must answer and check the required fields in a sample response. If the output is only a match card with possession and shots, bundled totals may avoid a much larger integration and licensing bill.
A plan price means little until it is matched to the competitions, seasons, and fixtures that actually return possession. Count verified matches, not every fixture in the catalogue. If a $240 monthly plan covers 1,000 listed fixtures but only 600 return the required possession field, the starting cost is $0.40 per usable match—before request overages or backfills.
Estimate calls at the intended refresh rate. For 300 live matches, polling once a minute for 90 minutes takes about 27,000 requests; add calls for fixture discovery, final figures, retries, and historical backfills. Check both monthly allowances and burst limits: a generous monthly quota may still block polling during a busy match window. League-specific packages or higher rate tiers can change the price substantially.
Keep published prices separate from quote-only terms. A listed subscription may exclude older seasons, particular leagues, commercial display rights, or redistribution; confirm these in writing before treating the figure as a budget. Ask whether support includes help diagnosing missing possession and how quickly coverage issues are handled. For a point of reference on premium data agreements, see Opta and StatsBomb data costs compared.
The useful comparison is total first-year cost divided by verified usable matches, with one-time backfill charges shown separately from recurring fees.
A possession feed can pass every technical test and still be unsuitable for the intended product. Before signing, check whether the licence permits public display and commercial use, including use in a paid app or on pages with advertising. Then check whether caching is allowed, how long figures may be retained, and whether possession values can appear in downloads, partner feeds, or other forms of redistribution. A right to display a match card does not necessarily include a right to share the underlying data.
Read the service terms with the same care. An uptime commitment usually concerns API availability; it does not promise that possession will exist for every scheduled fixture. Ask how missing statistics are reported, whether support will investigate specific fixtures, and whether corrected values are flagged or silently replaced. If coverage changes, advance notice matters to anyone maintaining a published match list.
Finally, check cancellation and post-cancellation rights. A short notice period is useful, but not if historical possession must be removed from an archive immediately. Request written clarification wherever the contract and product documentation describe different permissions.
Record the permitted display, caching period, redistribution rules, correction process, coverage notices, and exit terms alongside the quoted price.
A familiar brand or low monthly price does not establish whether possession is available for the matches that matter. Put broad commercial feeds, specialist football providers, and lighter-weight APIs through the same fixture sample: target leagues, cup rounds, recent and older seasons, and any match statuses the application must handle. Use the same required fields and freshness threshold for every candidate.
| Provider type | Possible appeal | Point to verify |
|---|---|---|
| Broad commercial feed | Multiple sports or datasets under one contract | Whether the quoted tier includes possession for the sampled football fixtures |
| Specialist football provider | Football-specific fields and competition detail | Whether possession coverage extends to the required seasons and cup rounds |
| Lighter-weight API | Simpler integration or a lower entry price | Whether live updates, historical access, and permitted use meet the actual need |
For each sampled fixture, record whether possession is returned, which fields are populated, and when the value first meets the freshness threshold. Treat a fixture record with a null statistic as a miss, not a successful match. Check redistribution and display rights against the intended product rather than assuming API access grants permission to publish the data.
Finally, request a quote for the same expected usage period. Include minimum commitments, polling and overage charges, historical access, backfill, and support where applicable. Compare total quoted cost alongside usable fixtures, not as a stand-alone monthly fee. No provider type wins by default: advertised coverage, refresh rates, field availability, and licensing terms need confirmation in current documentation, a trial, or the written quote.
Set a minimum before comparing prices: which competitions and seasons must be covered, what share of the required fixtures must have possession, and how soon the figures must be available. Test shortlisted feeds against the same matches, including awkward cases such as early cup rounds and postponed fixtures. Then price only the feeds that pass, using the expected request volume and the rights the project needs. The least costly compliant option is a stronger choice than a cheaper feed whose gaps undermine the result.
Decide how the product will handle gaps before launch. Withhold a missing possession value rather than estimate one from an unrelated statistic; if a substitute feed is used, label its source. If no API clears the coverage or cost threshold and live updates are unnecessary, downloadable match data may be the simpler route.
A common version uses completed passes in each team’s attacking third: Team A field tilt…
Live possession usually gives a reliable broad picture of which team has seen more of…
