Using the API
Caching and freshness
How long results are cached, and how to get fresh data.
Reads are cached so that repeated calls are fast. Every response says what you got: meta.cache is HIT or MISS, and meta.data_age_s is how many seconds ago the data was fetched from the platform.
How long things are cached
| What | Cached for |
|---|---|
| Profiles, tracks, collections, ads, events | 1 hour |
| Posts and single posts | 15 minutes |
| Comments and replies | 10 minutes |
| Search and trending | 5 minutes |
| Live status | 1 minute |
| Transcripts, audience, advertisers | 24 hours |
Forcing a fresh read
Add fresh=true to skip the cache. It costs 2× and the result replaces the cached copy, so the next normal call gets it too. Most applications should not need it: check data_age_s and only go fresh when the age matters for that request.