Data Retention
How long each kind of data stays queryable. Game data (items, monsters, spells, …) is a snapshot of the current patch and has no retention window: it is replaced wholesale when a new patch is imported. The live feeds below are time-series. Some are kept forever, some roll off.
| Data | Endpoint | Retention |
|---|---|---|
| Trade chat | /v2/trades/chat | 14 days |
| Market listings | /v2/market | Indefinite |
| Population | /v2/population/history | Indefinite |
| Server status | /v2/status/history | 90 days |
| Leaderboards | /v2/leaderboards | Indefinite |
| Patches & notes | /v2/patches | Indefinite |
Trade chat
/v2/trades/chat serves a rolling 14 day window. Messages older than that are deleted permanently. There is no archive, so mirror the feed on your side if you need longer history.
Market
Listings on /v2/market are kept indefinitely. Use listing_state — or the has_sold / has_expired / has_cancelled flags with is_confirmed — for lifecycle state. A missing listing was absent from a later complete family scan. That strongly suggests a sale, but the game did not confirm the outcome.
Population
Raw population samples are kept indefinitely. /v2/population/history answers coarse intervals (1h, 1d, 1w, 2w, 4w) from pre-computed aggregates and everything else straight from the raw samples, so any interval can reach the full history.
Server status
/v2/status/history serves per-component daily uptime buckets for the last 90 days. Older status samples are purged.
Permanent archives
Leaderboards (/v2/leaderboards) keep every season's final standings. Patches and patch notes (/v2/patches) are a permanent catalog. Neither is ever pruned.