My pulls (scope=mine)

GET /api/v1/mystery/feed/recent?scope=mine read:catalog

Every pull is attributed to the calling key’s partner (partner_id + api_key_id stamped on each purchase, plus a "{partner-slug}-{purchase_id}" memo). ?scope=mine filters the feed to your own pulls — the CollectorCrypt-style "filter activity by your key".

Try it GET /api/v1/mystery/feed/recent?scope=mine&limit=10

These inputs are shared across all docs pages — an id entered here carries over.

response
401 66ms preloaded server-side with the default context
object · 3 keys 
{
  "success": false,
  "message": "Invalid API key",
  "error": "API key not found or inactive"
}
curl (tracks the inputs above) 
curl -X GET 'https://staging-service.rip.fun/api/v1/mystery/feed/recent?scope=mine&limit=10' \
  -H 'X-API-Key: rip_v1_…'