Build a transaction

Builds a DEPOSIT or a REDEEM_REQUEST for the vault slug names: it runs the checks below in order (the first failure answers), returns the unsigned transactions and simulates them. Nothing is signed or sent.

DEPOSIT (syncDeposit: the shares are minted in the same transaction):

• Checks: the amount is at least the minimum and within the per-request limit (400 amount_below_minimum / invalid_amount); receiver, when sent, equals sender, compared case-insensitively (400 on body.receiver); the vault exists (404 vault_not_found) and is active (409 vault_not_active); the vault is not paused (409 vault_paused); it accepts synchronous deposits and its NAV is valid (409 deposits_unavailable); the cap has room, counting the deposits waiting for settlement (409 deposit_cap_reached); the vault’s allow list (isAllowed) accepts the sender and the receiver (403 wallet_not_allowed); the sender holds the amount (422 insufficient_balance); the simulation passes (422 simulation_failed).
• The transactions are an exact-amount approve of the deposit asset when the allowance is short, then syncDeposit(amount, sender, referral) on the vault: the shares go to the sender. referral defaults to the zero address.

REDEEM_REQUEST, a redeem request (requestRedeem(shares, sender, sender): the shares leave the wallet at once, and the assets become claimable when the vault settles the request, usually within window.maxDays):

• Checks: the vault exists and is active (404 / 409); the vault is not paused (409 vault_paused); the vault’s allow list accepts the sender (403 wallet_not_allowed); shares is at most the sender’s balance (422 insufficient_shares); the sender has no redeem request waiting for settlement in this vault (409 redeem_request_already_pending); the simulation passes (422 simulation_failed).
• If the sender has a settled redeem request it has not claimed, requestRedeem pays those assets to the sender first, in the same transaction; claimFirst shows them (null otherwise). Once the new redeem request settles, the wallet claims its assets in the Kamui app, or its next redeem request pays them out.
• No approval is needed: the sender owns the shares.

Both types:

• simulation.status is passed (the bundle ran with eth_simulateV1, or a single transaction with eth_call), partial (the node cannot simulate a bundle and the deposit needs the approval first, so only the checks ran) or skipped (skipSimulation: true).
• A legacy slug resolves to its canonical vault, and the response carries the canonical slug.
• Transaction building must be enabled for your API client (403 actions_not_enabled) and can be switched off (503 actions_disabled). A DEPOSIT’s amount and receiver checks answer first.