Redeem

Endpoint

Download schema

Batch Redeem (TRADE)

Redeem one or more settled prediction tokens on-chain to claim winnings. Requires SAS authorization.

POST

/sapi/v1/w3w/wallet/prediction/batch-redeem

https://api.binance.com

Batch Redeem (TRADE) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.

Batch Redeem (TRADE) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

IP Weight200

Batch Redeem (TRADE) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Batch Redeem (TRADE) › Query Parameters

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

Batch Redeem (TRADE) › Request Body

walletAddress

string · required

User's prediction wallet address

Example: 0x12e32db8817e292508c34111cbc4b23340df542c

walletId

string · required

Wallet ID

Example: 5b5c1ec3be4e4416a5872b21c1ca5d20

tokenIds

string[] · required

List of prediction token IDs to redeem. Not empty. Example: tokenIds=112233&tokenIds=112234

chainId

string

Chain ID. Default 56 (BSC)

Example: 56

Default: 56

Batch Redeem (TRADE) › Responses

200

Batch Redeem

batchId

string

Example: batch_20260525_redeem_001

object[]

requestId

string

Example: req_001

txHash

string

Example: 0xabc123def456789abcdef123456789abcdef123456789abcdef123456789abcd

status

string

Example: PENDING

error

string | null

Example: null

POST/sapi/v1/w3w/wallet/prediction/batch-redeem

curl --request POST \
  --url 'https://api.binance.com/sapi/v1/w3w/wallet/prediction/batch-redeem?timestamp=%3Cnumber%3E' \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --header 'X-MBX-APIKEY: <string>' \
  --data walletAddress=0x12e32db8817e292508c34111cbc4b23340df542c \
  --data walletId=5b5c1ec3be4e4416a5872b21c1ca5d20 \
  --data tokenIds=112233

Example Request Body

{
  "walletAddress": "0x12e32db8817e292508c34111cbc4b23340df542c",
  "walletId": "5b5c1ec3be4e4416a5872b21c1ca5d20",
  "tokenIds": [
    "112233"
  ]
}

json

Example Responses

{
  "batchId": "batch_20260525_redeem_001",
  "results": [
    {
      "requestId": "req_001",
      "txHash": "0xabc123def456789abcdef123456789abcdef123456789abcdef123456789abcd",
      "status": "PENDING",
      "error": null
    }
  ]
}

json

application/json

Get Redeem Status (USER_DATA)

Query the on-chain transaction status of a previously submitted redeem request.

GET

/sapi/v1/w3w/wallet/prediction/redeem/status

https://api.binance.com

Get Redeem Status (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.

Get Redeem Status (USER_DATA) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

IP Weight200

Get Redeem Status (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Get Redeem Status (USER_DATA) › Query Parameters

walletAddress

string · required

User's prediction wallet address

Example: 0x12e32db8817e292508c34111cbc4b23340df542c

txHash

string · required

Redeem transaction hash

Example: 0xabc123def456789abcdef123456789abcdef123456789abcdef123456789abcd

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

recvWindow

integer · int64 · max: 60000

Request validity window in milliseconds

Example: 5000

Get Redeem Status (USER_DATA) › Responses

200

Get Redeem Status

txHash

string

Example: 0xabc123def456789abcdef123456789abcdef123456789abcdef123456789abcd

status

string

Example: CONFIRMED

Status values:

Value Description
PENDING Transaction submitted, awaiting confirmation
CONFIRMED Transaction confirmed on-chain
FAILED Transaction failed
NOT_FOUND Transaction hash not found

Batch Redeem (TRADE)

Redeem one or more settled prediction tokens on-chain to claim winnings. Requires SAS authorization.

POST

/sapi/v1/w3w/wallet/prediction/batch-redeem

https://api.binance.com

Batch Redeem (TRADE) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.

Batch Redeem (TRADE) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

IP Weight200

Batch Redeem (TRADE) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Batch Redeem (TRADE) › Query Parameters

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

Batch Redeem (TRADE) › Request Body

walletAddress

string · required

User's prediction wallet address

Example: 0x12e32db8817e292508c34111cbc4b23340df542c

walletId

string · required

Wallet ID

Example: 5b5c1ec3be4e4416a5872b21c1ca5d20

tokenIds

string[] · required

List of prediction token IDs to redeem. Not empty. Example: tokenIds=112233&tokenIds=112234

chainId

string

Chain ID. Default 56 (BSC)

Example: 56

Default: 56

Batch Redeem (TRADE) › Responses

200

Batch Redeem

batchId

string

Example: batch_20260525_redeem_001

object[]

requestId

string

Example: req_001

txHash

string

Example: 0xabc123def456789abcdef123456789abcdef123456789abcdef123456789abcd

status

string

Example: PENDING

error

string | null

Example: null

Get Redeem Status (USER_DATA)

Query the on-chain transaction status of a previously submitted redeem request.

GET

/sapi/v1/w3w/wallet/prediction/redeem/status

https://api.binance.com

Get Redeem Status (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.

Get Redeem Status (USER_DATA) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

IP Weight200

Get Redeem Status (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Get Redeem Status (USER_DATA) › Query Parameters

walletAddress

string · required

User's prediction wallet address

Example: 0x12e32db8817e292508c34111cbc4b23340df542c

txHash

string · required

Redeem transaction hash

Example: 0xabc123def456789abcdef123456789abcdef123456789abcdef123456789abcd

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

recvWindow

integer · int64 · max: 60000

Request validity window in milliseconds

Example: 5000

Get Redeem Status (USER_DATA) › Responses

200

Get Redeem Status

txHash

string

Example: 0xabc123def456789abcdef123456789abcdef123456789abcdef123456789abcd

status

string

Example: CONFIRMED

Status values:

Value Description
PENDING Transaction submitted, awaiting confirmation
CONFIRMED Transaction confirmed on-chain
FAILED Transaction failed
NOT_FOUND Transaction hash not found

Value	Description
`PENDING`	Transaction submitted, awaiting confirmation
`CONFIRMED`	Transaction confirmed on-chain
`FAILED`	Transaction failed
`NOT_FOUND`	Transaction hash not found

Value	Description
`PENDING`	Transaction submitted, awaiting confirmation
`CONFIRMED`	Transaction confirmed on-chain
`FAILED`	Transaction failed
`NOT_FOUND`	Transaction hash not found