pnclENGINEGet API access

CAPACITY NOTES

Hand a match from prematch polling to live polling

Live and prematch are separate boards, so a starting match has to move between them. The handoff schedule, the cursor per board, and the refresh rhythm.

A match starting is a phase change, and on this API phases are separate boards: live and prematch are separate requests with the same shape, as the capacity guide states, checked 2026-10-09. Your poller has to move each fixture from one board to the other at the right moment, on the right rhythm, with a cursor per board.

The two boards run on different clocks

The documented prematch refresh is about every 30 seconds, so polling prematch faster buys nothing. Live prices reach the feed within a fraction of a second, which is where the interval actually matters. A single schedule for both phases either wastes requests on the slow board or starves the fast one.

The clean split is two jobs: a slow prematch poller on the prematch interval, and a fast live poller on the live one. Each holds its own cursor per board, because a cursor tracks a position in one board's stream of changes and means nothing to the other.

When to make the switch

The trigger is the fixture's start time, with a margin on both sides. Start live polling for a board a few minutes before the first match on it starts, so you catch the opening prices rather than reconstructing them. Keep the prematch poll running a few minutes past the start, because fixtures that start late sit on the prematch board longer than the schedule says.

A match leaving the prematch board is your confirmation it has started, not a rule to stop polling early. Late starts are normal; the prematch board keeps them visible until the market reports play.

What changes in your state

The event you tracked prematch is the same match on the live board, but the delivery is different: live moves faster, suspends around key moments, and produces far more changes per minute. Anything you sized for prematch volume, storage writes, alert thresholds, dedupe windows, should be re-thought for live cadence, not inherited.

The rate limits guide's headroom rule matters more during the transition than anywhere else: the minutes around a big kickoff are when boards move fastest and your live interval earns its keep, and a schedule already at the ceiling will show its first 429s there.

The close is the last prematch row

The handoff also defines your closing line: the last prematch snapshot before the start is the close, and the storage guide's close-capture job marks exactly that row per selection. A clean handoff gives you both things at once: a closing line you trust and a live feed that starts on time.

Two boards, two rhythms, two cursors, one start time. The handoff is small; getting it wrong is how a pipeline loses the most important minutes of the match.