The trend archive

Why an archive is a different product

Every other API in this market answers what is trending now and discards it — their caches run two to thirty minutes. That answer cannot be reconstructed later, because nobody photographed the past.

A single snapshot cannot tell you whether a topic is accelerating or dying. Two snapshots an hour apart can. That is the only thing this product does, and it is the reason it had to start collecting before it had customers.

What it stores, and what it refuses to

Six fields per item and no more: an id, the title or caption, the link, when it was published, a score, and a comment count. No author fields, no profiles, no follower counts, no avatars, no bios. Captions are cut at 200 characters — enough to tell one item from another, not enough to reproduce someone’s work.

The exceptions, and why they exist, are written out on the privacy page. There is also a removal route.

Start here

• API documentationEndpoints, credits, limits — and the caveats, including what this data does not support yet.
• Live trendsWhat is rising right now, per niche, with the real interval between snapshots rather than a rounded window.
• Archive statusHow deep the archive is per niche, and how long since the last capture. Published because depth is the thing you are buying.

Before you build on it

The archive began on 5 September 2026. Ask /api/v1/nichos how deep it is for your niche before you depend on it. We would rather tell you that than have you find out.