Skip to main content
POST
/
operations
/
redeem-position
Redeem position
curl --request POST \
  --url https://relayer.forka.st/operations/redeem-position \
  --header 'Content-Type: application/json' \
  --data '
{
  "contract": "0xCeAfDb29f9fC7c25fF6F0768d45b288c9b7C5cA5",
  "collateral_token": "0x2791Bca1F2de4661ED88A30C99A7a9449Aa84174",
  "condition_id": "0xf1013774fef741c35a375718d6b1f542d98382cc0d3a0fd2fd0c12e3b3c6f6e5",
  "parent_collection_id": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "index_sets": [
    "1"
  ]
}
'
{
  "txHash": "0x0123...",
  "confirmations": 1
}
Redeem resolved outcome tokens for collateral by having the relayer call redeemPositions. This is typically the final step once a market has been settled on-chain.
POST to https://relayer.forka.st/operations/redeem-position with the usual L2 headers. You will receive the relayer-broadcast transaction hash and confirmation count.

​
Request body

FieldTypeRequiredDescription
contractstringYesConditional Tokens contract that will process the redemption.
collateral_tokenstringYesCollateral token you expect to receive.
condition_idstringYesResolved condition identifier.
parent_collection_idstringYesParent collection (use zero hash when redeeming the root).
index_setsarray<string>YesList of partition indexes being redeemed.

​
Notes

  • Make sure the outcomes in index_sets already resolved; otherwise the relayer’s transaction will revert.
  • Redemptions send collateral back to the relayer’s custody first—coordinate any follow-up transfers out-of-band.
  • Validation failures (bad hex, missing fields) return 400. Execution issues surface as 502 with the RPC error appended to error.

Body

application/json
​
contract
string
required
​
collateral_token
string
required
​
condition_id
string
required
​
parent_collection_id
string
required
​
index_sets
string[]
required

Response

Transaction broadcast by the relayer.

​
txHash
string
required
​
confirmations
integer<int32>
required