Trends

include=trends

The trends include attaches a per-minute breakdown of match events to each fixture. Each entry represents the cumulative value of a specific stat for a given team at a given minute of the match — for example, how many corners team A had by minute 34, or how many shots on target by minute 67.

Two computed stats are also appended for every minute: Expected Goals (xG) and a Pressure Index, both calculated from per-minute data and event details.

Availability: Only returned when include=trends is added to the request. A default set of stats is returned when no filter is applied.

Object Schema

Each entry in the trends array represents one stat for one team at one minute.

Minute Scope

Minute values are global across the match, not reset per period. However, the second half always begins at minute 45, regardless of how much added time occurred in the first half.

Key rules:

• Minutes within a period count continuously until that period ends. A 1st half with 3 minutes of added time produces entries up to minute 48.
• When the 2nd half kicks off, the minute counter resets to 45 — not to wherever the 1st half ended. There is no gap or overlap in the stored data; use period_id to distinguish entries at the same minute value across the two halves.
• Use period_id as the disambiguator when plotting: entries at minute 45 can exist in both halves, and period_id tells you which is which.

Value Continuity Across Periods

Cumulative value fields are never reset between periods. Each new period picks up where the previous one left off — a team that had 6 corners by the end of the first half will show 6+ corners at the start of the second half, not 0.

This applies to all periods, including additional time in cup matches where both teams are level after 90 minutes:

When plotting a single stat across all periods, use the raw value directly — no per-period offset is needed. To isolate a period's contribution, subtract the last value of the preceding period from the first value of the current one.

Available Stats

Default Stats

Returned when no filter[trends] is provided.

Computed Stats

Calculated from per-minute data and event details. Included in the default response and available via filter.

Value Encoding

EXPECTED_GOALS

EXPECTED_GOALS values are stored as integers scaled by 100. To convert to the standard xG decimal, divide by 100.

Example:

{
  "team_id": 85,
  "period_id": 2101938,
  "minute": 34,
  "type_id": 117,
  "developer_name": "EXPECTED_GOALS",
  "value": 18
}

This means the team had 0.18 xG by minute 34.

Filtering

Add filter[trends] to limit which stats are returned. Two filter formats are supported.

By developer name — developer_names

Returns only the stats matching the listed names. Takes priority over types when both are provided.

filter[trends]=developer_names:GOALS,CORNERS,DANGEROUS_ATTACKS

By type ID — types

Returns only the stats matching the listed external type IDs. Ignored when developer_names is also set.

filter[trends]=types:117,118

Request Examples

All trends with defaults (no filter):

GET /fixtures?fixture_id=1063864&include=trends

Only goals and corners per minute:

GET /fixtures?fixture_id=1063864&include=trends&filter[trends]=developer_names:GOALS,CORNERS

Expected Goals and Pressure Index only:

GET /fixtures?fixture_id=1063864&include=trends&filter[trends]=developer_names:EXPECTED_GOALS,PRESSURE_INDEX

Full trend picture for live match analysis:

GET /fixtures?status=INPLAY_1ST_HALF,INPLAY_2ND_HALF&include=trends&filter[trends]=developer_names:ATTACKS,DANGEROUS_ATTACKS,SHOTS_ON_TARGET,SHOTS_OFF_TARGET,CORNERS,EXPECTED_GOALS,PRESSURE_INDEX

Example Response

"trends": [
  {
    "team_id": 85,
    "period_id": 2101938,
    "minute": 12,
    "type_id": 9,
    "developer_name": "ATTACKS",
    "value": 34
  },
  {
    "team_id": 85,
    "period_id": 2101938,
    "minute": 12,
    "type_id": 13,
    "developer_name": "CORNERS",
    "value": 2
  },
  {
    "team_id": 85,
    "period_id": 2101938,
    "minute": 12,
    "type_id": 117,
    "developer_name": "EXPECTED_GOALS",
    "value": 18
  },
  {
    "team_id": 85,
    "period_id": 2101938,
    "minute": 12,
    "type_id": 118,
    "developer_name": "PRESSURE_INDEX",
    "value": 42
  }
]

EXPECTED_GOALS value 18 = 0.18 xG (divide by 100).

Real-World Use Cases

Live match dashboard

Fetch all default trend stats for live matches and plot each stat as a time series. The minute field is your X-axis; the value is your Y-axis. Separate by team_id to show home vs. away lines side by side.

Momentum detection

Use DANGEROUS_ATTACKS and PRESSURE_INDEX filtered by the last 10–15 minutes to detect which team is currently dominating. A rising PRESSURE_INDEX combined with a low GOALS value often signals an imminent scoring opportunity.

xG chart

Request EXPECTED_GOALS (type_id 117) for both teams across the full match. Plot cumulative xG per minute to show how the match evolved and whether the final score reflects the balance of play. Divide each value by 100 to get the decimal xG before plotting.

Pre-match data review

Trends are stored for completed matches. Fetch historical fixtures with include=trends to analyse how a team typically builds up attacking pressure across a 90-minute window before predicting outcomes.

Substitution impact analysis

Combine ATTACKS and DANGEROUS_ATTACKS before and after the minute of a SUBSTITUTIONS event to measure whether a tactical change shifted momentum for a team.