/api/v1/mystery/redemption/submit cards:redeem Records the transaction the end user already sent (from /prepare), moving the redemption PREPARED → BURN_SUBMITTED. tx_hash must be a transaction the holder already sent. This records it, it doesn’t send anything. Re-submitting the same hash is safe.
POST /api/v1/mystery/redemption/submit write These inputs are shared across all docs pages, so an id entered here carries over.
{
"redemption_id": 0,
"tx_hash": "0x0000000000000000000000000000000000000000000000000000000000000000"
}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 -X POST 'https://service.rip.fun/api/v1/mystery/redemption/submit' \
-H 'X-API-Key: rip_…' \
-H 'Content-Type: application/json' \
-d '{"redemption_id":0,"tx_hash":"0x0000000000000000000000000000000000000000000000000000000000000000"}' | Field | Type | Required | Description |
|---|---|---|---|
redemption_id | number | yes | From the prepare response |
tx_hash | string | yes | 0x-prefixed 32-byte hash of the redemption transaction the holder already sent |
data)| Field | Description |
|---|---|
redemption_id / status / burn_tx_hash | BURN_SUBMITTED + the recorded hash |
tracking_number / tracking_url / label_url / carrier / service | Present only when the shipping label was bought right here — that needs the burn already confirmed on-chain AND the shipping payment landed. Absent (or null) otherwise, which is the normal case: the label is bought later and the tracking number reaches you on GET /redemption/:id and the redemption.updated webhook. Never treat their absence as a failure |
| Status | Code | When |
|---|---|---|
| 400 | invalid_tx_hash | not a 0x-prefixed 32-byte hash |
| 409 | invalid_status | redemption is in any non-PREPARED state |
| 404 | not_found | unknown redemption_id |
See Errors for the response envelope and the full code list.