Home · Solutions · By what you want to do
Trend detection API — what moved, not what is big
Rank a window of archived history by how much each item actually gained. Position is not movement, and the archive keeps both.
The problem
A leaderboard tells you who is already big. Catching a rise means comparing two moments, and that needs history somebody kept before you asked — which is the one thing a live scrape cannot give you.
What answers it — 3 endpoints
archive/coveragearchive/trendsarchive/movers
Shape, parameters and the errors each one returns are in the endpoint reference, generated from the same catalogue the router reads.
The recipe
Which topics in your niche climbed fastest this week — the steps, with real commands and real output, plus the measured caveats that change the result.