Redemption status

GET /api/v1/mystery/redemption/:purchase_id packs:read

Every redemption for a card, newest first (404 when none). The path accepts a purchase id OR an on-chain token id (token-first redemptions carry purchase_id: null). Fill in either input below. Status: PREPARED → BURN_SUBMITTED → IN_FULFILLMENT → COMPLETED, or FAILED / CANCELLED / EXPIRED.

Try it GET /api/v1/mystery/redemption/

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

response

Not run yet — press Run to make a live call against https://service.rip.fun (through this demo's server-side proxy; the API key never reaches the browser).

curl (tracks the inputs above)
curl -X GET 'https://service.rip.fun/api/v1/mystery/redemption/' \
  -H 'X-API-Key: rip_…'

Request fields

FieldTypeRequiredDescription
verifyquery booltrue → check the card’s status live on-chain instead of cached

Response fields (data)

FieldDescription
redemptions[].purchase_idnull for token-first (own-gacha) redemptions
redemptions[].statusLifecycle status (see overview); failure_reason set when FAILED
redemptions[].burndb_status, is_burned (flips when the item ships), burn_type + label (REDEEM_CARD…)
redemptions[].queue / orderRedeem-queue + fulfillment order status (tracking_number once shipped)
redemptions[].burn_tx_hash / shipping_quote / expires_atRecorded burn tx, locked-in rate, and when the transaction expires

Errors

StatusCodeWhen
404not_foundno redemptions exist for the purchase or token

See Errors for the response envelope and the full code list.