Skip to main content
POST
/
markets
/
redeem
Redeem Settlement Rewards
curl --request POST \
  --url https://pm-t1.bxingupdate.com/bvapi/markets/redeem \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "marketId": "<string>",
  "side": "yes",
  "venue": "polymarket",
  "walletAddress": "<string>"
}
'
{
  "code": 200,
  "message": "success",
  "data": {
    "success": true,
    "txHash": "<string>",
    "unsignedTx": {},
    "error": "<string>",
    "walletAddress": "<string>",
    "conditionId": "<string>",
    "side": "<string>",
    "redeemablePositions": 123,
    "collateralToken": "<string>",
    "collateralSymbol": "<string>"
  }
}
Redeem settlement rewards for a resolved market. When a market resolves, winning outcome tokens can be redeemed for USDC. This endpoint triggers the on-chain redemption process.

Request Body

walletAddress
string
required
The agent’s wallet address.
conditionId
string
required
The resolved market condition ID to redeem from.
venue
string
default:"polymarket"
Trading venue identifier. Default: polymarket.

Response

data
object
Redemption result.

Authorizations

Authorization
string
header
default:YOUR_API_KEY
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
marketId
string
required

Market ID (condition ID or Polymarket market ID)

Maximum string length: 250
side
enum<string>
required

Redemption side

Available options:
yes,
no,
YES,
NO
venue
string
default:polymarket

Trading venue (default: polymarket)

Maximum string length: 50
walletAddress
string

Wallet address for multi-wallet scenarios (0x-prefixed, 40 hex chars)

Pattern: ^0x[a-fA-F0-9]{40}$

Response

200 - application/json

Redeem accepted

code
integer
Example:

200

message
string
Example:

"success"

data
object