/api/v1/mystery/redemption/submit cards:redeemRecords the burn tx the end user broadcast, moving the redemption PREPARED → BURN_SUBMITTED (202 — fulfillment is asynchronous). A fast-path courtesy: the worker also converges from on-chain state, so an un-submitted burn still advances the redemption. Re-submitting the same hash is idempotent.
POST /api/v1/mystery/redemption/submit write These inputs are shared across all docs pages — an id entered here carries over.
{
"redemption_id": 0,
"tx_hash": "0x0000000000000000000000000000000000000000000000000000000000000000"
}Not run yet — press Run to make a live call against https://staging-service.rip.fun (through this demo's server-side proxy; the API key never reaches the browser).
curl -X POST 'https://staging-service.rip.fun/api/v1/mystery/redemption/submit' \
-H 'X-API-Key: rip_v1_…' \
-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 burn tx |
data)| Field | Description |
|---|---|
redemption_id / status / burn_tx_hash | BURN_SUBMITTED + the recorded hash |
| Status | Code | When |
|---|---|---|
| 400 | invalid_tx_hash | not a 0x-prefixed 32-byte hash |
| 409 | kyc_required | redemption is still AWAITING_KYC |
| 409 | invalid_status | redemption is in any other non-PREPARED state |
| 404 | not_found | unknown redemption_id |
See Errors for the response envelope and the full code list.