Distributor Fees
Set Distributor Wallet
Calldata that moves where the vault pays your instance’s distributor fees
POST
Builds
The route validates every field of the schema it shares with the other distributor actions, even where this action ignores it.
The confirmation response, after the backend has verified the receipt:
setDistributorWallet(distributor, wallet) on the vault. It moves the payout wallet of one of your instance’s distributor wallets in this vault, the wallet Pay Distributor sends its fees to. The attribution does not change: holders stay bound to the distributor, and only the destination of its fees moves.
Only the distributor’s current payout wallet can sign. Until it is first moved, that is the distributor address itself. The contract accepts any non-zero address as the new wallet from that signer. The API is stricter and refuses a wallet your instance has not verified.
Path Parameters
string
required
Vault ID.
Body Parameters
string
The new payout wallet, as a
0x address. Required to build the calldata. It must be a verified wallet of your instance, and not the zero address.string
Which of your instance’s distributor wallets to move the payout wallet for. Defaults to your instance’s distributor wallet: its primary verified wallet, or its earliest when none is primary. A wallet your instance has not verified answers
DISTRIBUTOR_NOT_OWNED.string
The wallet that will sign. When given, the API refuses with
NOT_DISTRIBUTOR_WALLET unless it is the current payout wallet.string
Hash of the mined transaction,
0x and 64 hex characters. Send it to confirm and record the result; nothing else is needed then. Omit it to receive the calldata.Response Fields
The calldata response:object
object
Error Codes
Confirming with
txHash can also return TX_NOT_FOUND (404), TX_REVERTED, TX_WRONG_TARGET or TX_WRONG_FUNCTION (400), and TX_NOT_VERIFIED (400) when the transaction carries no payout-wallet change on this vault. See transaction verification errors.