Wallets & Addresses
Edit Wallet
Update the configuration of an existing Finrock wallet: freeze or unfreeze it, and set or unset auto-forwarding of incoming funds to an address.
PATCH
MCP scope:
dac.funds (not available to AI connectors yet)
Use this endpoint to freeze or unfreeze an existing wallet, or to set or update its auto-forwarding. Identify the wallet by its asset, then pass is_frozen to change its frozen state, a forwarding object to configure auto-forwarding, or both.
Auto-forwarding
Auto-forwarding sends funds from your wallet to an external address automatically, so you don’t have to submit withdrawals yourself. When a wallet has auto-forwarding set up, Finrock forwards incoming funds to theforwarding.address you provide. With RealTime frequency, funds are forwarded as soon as they are added to the wallet. With Nightly (the default), they are batched and forwarded once per night.
The destination must be an external address. Forwarding to an address that belongs to your own Finrock account returns HTTP 400 with {"code": 1100, "error": "INTERNAL_DESTINATION_NOT_ALLOWED"}.
A new forwarding address doesn’t take effect straight away. The response shows forwarding.status as PENDING_OWNER_APPROVAL until the owner, or at least 2 admins, approve it in the dashboard.
To turn off auto-forwarding, send "forwarding": { "address": null }. To cancel a forwarding address that’s still waiting for approval, send "forwarding": { "address": "" }. Sending "forwarding": null, or leaving forwarding out, leaves the current forwarding unchanged.
Common uses include:
- Sweeping customer deposits into a cold wallet or treasury account
- Settling received funds straight to an exchange account
- Keeping balances in hot wallets as low as possible
Body Parameters
The asset of the wallet to update. Use the
id value from the Supported Assets list (e.g. ETH, BTC, TRX_TEST).Set to
true to freeze the wallet, or false to make it active. Send null or leave this field out to keep the current state. In the dashboard, the Freeze Wallet toggle under Settings → Sub Accounts → Manage does the same.XRP wallets only. Makes the XRP Ledger reject any deposit to this wallet that doesn’t include a destination tag. Use this when you share one XRP address across customers and rely on destination tags to credit the right one. Send
null or leave this field out to keep the current setting.A change takes effect once the owner, or at least 2 admins, approve it in the dashboard. Until then, requires_dt_memo.change in the response is PENDING_OWNER_APPROVAL.Auto-forwarding settings for the wallet. To turn off auto-forwarding, send
{ "address": null }. Sending null, or leaving this field out, leaves the current forwarding unchanged.Response
A successful request returns HTTP200 with the updated wallet object.
The type of wallet:
Legacy, HSM or MPC. See Wallet Types.XRP wallets only. Whether the XRP Ledger rejects deposits to this wallet that don’t include a destination tag.

