Through Balls in Football: Definition, Data, and API Access
Contents

What is a through ball in football?

A through ball is a pass played into the space behind the defensive line for a teammate to run onto, bypassing one or more defenders. It is one of the most difficult passes in football to execute: it requires the passer to time the release precisely, weight the ball correctly, and read the movement of both the receiving player and the defensive line simultaneously. A successful through ball immediately creates a goal-scoring opportunity; an unsuccessful one is typically intercepted or runs harmlessly through to the goalkeeper. For developers building chance creation analytics, tactical dashboards, or player profiling tools, through balls are a key indicator of a player’s ability to play dangerous, line-breaking passes.

How through balls are classfied

In event-level football data, a through ball is recorded as a pass with a specific qualifier that indicates the ball was played into space between or behind the defensive line. The classification is made by the data provider’s event coders at the point of data capture, not derived algorithmically from coordinates alone, which means definitions can vary slightly across providers.

The key characteristics that define a through ball:

Destination. The pass endpoint is in the space behind the defensive line, not to a player already behind the defence. The ball travels through the defensive structure rather than over it (which would be a lofted through ball or a chip) or around it.

Intent. The pass is directed into space for a runner to receive, rather than to a stationary teammate’s feet.

Completion status. Through balls are tracked regardless of whether they were completed (received by the intended teammate) or intercepted. Both outcomes are analytically useful.

Through balls differ from long balls (which may be played forward without necessarily penetrating a defensive line) and from key passes (which require the pass to directly precede a shot). A completed through ball is often a key pass, but short passes that create shots are also key passes without being through balls.

Why through balls matter

Tactical signature. Teams that play a high through ball volume typically employ attacking players capable of running in behind and a centre-forward who creates space with movement. High through ball numbers are a marker of a direct, penetrative attacking approach.

Passer quality. Completing through balls at a high rate requires both the technical ability to execute the pass and the spatial awareness to identify the opportunity. Players who combine high attempted through balls with high completion rates are rare and analytically distinctive.

Defensive vulnerability. From a defensive analysis perspective, tracking through balls conceded (where the opponent successfully plays a through ball past your defensive line) reveals structural weaknesses in defensive shape and line management.

Expected threat models. Through balls that are completed generate high-value shooting opportunities. Including through ball completions as an input to expected threat (xT) models improves their accuracy in identifying pre-shot danger.

Through balls in the context of chance creation

A through ball is one of the highest-quality chance-creating actions in football. When a through ball is completed and results in a shot, that shot typically comes from a high-danger zone (close to goal, one-on-one with the goalkeeper, or from inside the six-yard box). This is why through balls, despite being a relatively infrequent event, have a disproportionate impact on expected goals and match outcomes.

For an analytics application, combining through balls with xA (expected assists) and shot location data gives you a clear picture of which players are generating the highest-quality attacking chances. A midfielder who completes 1.5 through balls per 90 minutes is likely generating a significant share of their team’s most dangerous opportunities.

HOW TO ACCESS THROUGH BALL DATA VIA API

Through balls are a real, confirmed statistic: total through balls played and accurate through balls played, tracked per player. They’re not logged as individual pass events in the events stream, passes aren’t itemized as discrete events the way goals, cards, and substitutions are. Instead, through-ball counts are aggregated directly into the player statistics object.

To retrieve them at the fixture level:

GET /v3/football/fixtures/{fixture_id}?include=statistics

playerStats isn’t a valid include name; the correct one is statistics.

For season-level totals, verify the exact endpoint against the current docs or Postman collection before using it; the confirmed season-statistics pattern is team-scoped rather than a dedicated players-under-seasons path.

FAQs

What is the difference between a through ball and a key pass?
A key pass is any pass that directly leads to a shot. A through ball is specifically a pass played into the space behind the defensive line for a teammate to run onto. Every completed through ball that results in a shot is also a key pass, but most key passes are not through balls — many are short passes in the penalty area or crosses from wide positions.
Are unsuccessful through balls tracked in football data?
Yes. Both completed and unsuccessful through balls are recorded in event-level football data. An unsuccessful through ball (intercepted by a defender or running through to the goalkeeper) is still analytically useful: it shows the passer's intent to play in behind the defence. High attempted through ball volume combined with low completion rate suggests a player is seeing opportunities that are not quite there, or is struggling with execution.
Which football API provides through ball data at the match and season level?

Sportmonks' Football API includes through ball data as an aggregated statistic, total through balls played and accurate through balls played, per player. This lives in the statistics object, not the match event stream; individual passes (through balls included) aren't logged as discrete events the way goals, cards, and substitutions are.

Access it via:

GET /v3/football/fixtures/{fixture_id}?include=statistics

For season-level totals, confirm the exact endpoint against current docs before use, the season-statistics pattern documented elsewhere is team-scoped, and I haven't found a confirmed players-under-seasons equivalent

Written by David Jaja

David Jaja is a technical content manager at Sportmonks, where he makes complex football data easier to understand for developers and businesses. With a background in frontend development and technical writing, he helps bridge the gap between technology and sports data. Through clear, insightful content, he ensures Sportmonks' APIs are accessible and easy to use, empowering developers to build standout football applications