Returns the active pool wallet — where bought-back card NFTs are forwarded after a buyback offer is accepted. Gated strictly by the pool:manage scope, since this controls where NFTs are sent.
Try itGET /api/v1/mystery/pool-wallet
response
40126mspreloaded server-side with the default context
object · 3 keys
{
"success": false,
"message": "Invalid API key",
"error": "API key not found or inactive"
}
curl (tracks the inputs above)
curl -X GET 'https://staging-service.rip.fun/api/v1/mystery/pool-wallet' \
-H 'X-API-Key: rip_v1_…'
Request fields
Field
Type
Required
Description
chain
query string
—
Defaults to "base"
Response fields (data)
Field
Description
chain / address
The active forwarding wallet
is_active / created_at
Replaced wallets are kept inactive as an audit trail
Errors
Status
Code
When
404
pool_wallet_not_set
no pool wallet configured yet — transfers are HELD until one is set
403
Insufficient permissions
key lacks the pool:manage scope
See Errors for the response envelope and the full code list.