/api/v1/mystery/feed/winners read:catalog Same shape as the recent feed but ordered by item value. Use it for a "biggest wins" marketing strip. Supports ?scope=mine, ?game= and pagination; rows are unique on (token_id, revealed_at), same as the recent feed.
GET /api/v1/mystery/feed/winners?limit=10 These inputs are shared across all docs pages, so an id entered here carries over.
{
"success": false,
"message": "Mystery partner API key required",
"error": "This endpoint requires an API key linked to a mystery partner account"
}curl -X GET 'https://service.rip.fun/api/v1/mystery/feed/winners?limit=10' \ -H 'X-API-Key: rip_…'
| Field | Type | Required | Description |
|---|---|---|---|
limit / offset | query int | — | Pagination (1–100 / 0–10000) |
scope | query string | — | `mine` → only this key’s pulls |
game | query string | — | Filter to one game (catalog ids: pokemon, onepiece, …) |
fresh | query bool | — | `true` bypasses the shared response cache and recomputes from source. Meant for a manual refresh, not for polling: it carries its own budget of 10 calls per minute per key, and past that you get a 429 while a plain read still answers from cache |