Set pool wallet

PUT /api/v1/mystery/pool-wallet pool:manage

Sets or replaces the address bought-back cards are sent to. Any transfers waiting on a pool wallet (buyback.transfer_held) complete automatically once this is set.

Try it PUT /api/v1/mystery/pool-wallet write

These inputs are shared across all docs pages — an id entered here carries over.

request body
object · 1 keys 
{
  "wallet_address": ""
}
response

Not run yet — press Run to make a live call against https://service.rip.fun (through this demo's server-side proxy; the API key never reaches the browser).

curl (tracks the inputs above) 
curl -X PUT 'https://service.rip.fun/api/v1/mystery/pool-wallet' \
  -H 'X-API-Key: rip_…' \
  -H 'Content-Type: application/json' \
  -d '{"wallet_address":""}'

Request fields

FieldTypeRequiredDescription
wallet_addressstringyes0x-prefixed EVM address (`address` is accepted as an alias)
chainstring—Defaults to "base"

Response fields (data)

FieldDescription
chain / address / is_active / created_atThe new active pool wallet

Errors

StatusCodeWhen
400invalid_addressnot a valid 0x-prefixed EVM address
403Insufficient permissionskey lacks the pool:manage scope

See Errors for the response envelope and the full code list.

Flow

  1. End user accepts your buyback offer → the card comes to rip.fun
  2. rip.fun sends the card to your active pool wallet → buyback.card_transferred webhook
  3. No pool wallet set yet → buyback.transfer_held; the transfer retries until you set one with PUT /pool-wallet
  4. The fronted USDC is settled daily either way (GET /billing)