Data Freshness
The API automatically manages data freshness for every request. There is no mode segment in the URL — instead, the cache strategy is smart by default, and you opt into a live re-scrape only when you need it.
GET /v2/users/dymerz ← default: cache-first, no quota cost
GET /v2/users/dymerz?refresh=true ← force live scrape, costs 1 daily request
How It Works
Default (no ?refresh)
Every request checks the internal cache first. No quota is consumed regardless of the result.
Data is kept fresh via fixed refresh intervals per endpoint. Each endpoint type has a maximum data age determined at deployment. See the Refresh Intervals section for details. Most requests are served directly from cache without ever touching the RSI website. You only pay a quota cost when you explicitly request a fresh scrape with ?refresh=true.
With ?refresh=true
Bypasses the cache and forces an immediate live scrape from the RSI website. The result is stored in the cache before being returned.
?refresh=true always costs 1 daily request from your quota, even if the data hasn't changed. Only use it when you genuinely need the latest data from the RSI website right now.
Quick Reference
| Scenario | What to do | Quota cost |
|---|---|---|
| General use | No extra parameter | Never |
| Need guaranteed up-to-date data | Add ?refresh=true | 1 per call |
| Quota running low | No extra parameter | Never |
Every response includes a expiresAt timestamp telling you exactly when the data may next be automatically re-scraped. For detailed per-endpoint refresh intervals, see Refresh Intervals.