Skip to content
VT

Riot review build

VALORANT Tracker SEA

Ranked archive

Competitive snapshots are treated like a journal, not a one-off fetch.

The leaderboard surface pulls official ranked data by Act, stores periodic snapshots, and prepares the UI for playback and movement over time once live data lands.

Query recipe

Fetch the official leaderboard by passing an Act ID into the API route.

/api/leaderboard?actId=<act-id>

Each response can be persisted as time-stamped rows for later comparison instead of being discarded after render.

Storage model

Dimension

Act ID

Metric

RR and wins

Time axis

captured_at

Endpoint

val/ranked/v1/leaderboards/by-act/{actId}

Why store snapshots

A single leaderboard response is useful. A timeline is much better.

Once snapshots are captured repeatedly, the surface can show movement, gaps between entries, and how an Act evolves instead of only rendering a flat list.

Review note

Input

Act ID query parameter

Output

Official ranked rows from Riot

Persistence

LeaderboardSnapshot table

Next UI step

Trend lanes and gap views