Returns the momentum flow of a match as chart-ready timeline points. Positive values represent the home team and negative values represent the away team.The endpoint supports both a full response and incremental live updates. Momentum is always recalculated using the complete match history; after_second only filters the items returned in the response.
Timeline points are generated at 60-second intervals and use a normalized range from -1 to 1.
Returns timeline points and goals strictly after this match second. Completed phases ending at or before this second are excluded, while a phase that continues beyond it is included.Must be zero or a positive integer. Omit this parameter to retrieve the complete timeline.
Comma-separated optional response sections. Accepted values are phases, goals, and inputs.If omitted, phases and goals are included. Passing include=inputs returns only the standard momentum response plus calculation inputs. Use include=phases,goals,inputs to return all optional sections.
strDominantTeam and strPhase are separate classifications. A point can therefore have strDominantTeam: "BALANCED" while its phase remains HOME_CONTROL or AWAY_CONTROL.
Continuous control phases. Returned by default and omitted when include does not contain phases.strTeamSide and strStrength are null for a balanced phase. Otherwise, strStrength is NORMAL or STRONG.
Goal annotations for the timeline. Returned by default and omitted when include does not contain goals.Each goal includes its match-event ID, time, team, scorer, shirt number when available, and the score immediately after the goal.
Request the endpoint without after_second to initialize the complete chart.
Store the greatest intSecond received in arrPoints.
On the next poll, send that value as after_second.
Append the returned points and goals by their unique time or ID.
Replace overlapping/current phase data rather than blindly appending phases, because an active phase may have started before the requested cursor.
For example, after_second=4800 returns points beginning at 4860; the point at 4800 is not repeated.
An incremental response is not calculated from only the newly received match events. The server uses the full match history to preserve consistency, then filters the response exclusively after the requested second.