Trade

There is no vault-specific trading & market data API. The vault is a subaccount owned by your wallet, so you run your strategy on it with the normal trading methods — orders, RFQs, transfers — passing the vault’s subaccount id. The managerId you chose at creation is the margin manager that governs what it can trade.

All of the steps in this guide can be done through the UX or SDKs.

await client.orders.place({
  subaccountId: vaultId, // the vault subaccount — that's the whole trick
  instrumentName: 'ETH-PERP',
  direction: 'buy',
  amount: '2',
  limitPrice: '2500',
});

# Coming soon.

// Coming soon.

# Body nonce/signature: EIP-712 trade signing (see /action-signing).
curl -X POST https://api.derive.xyz/v3/private/order \
  -H "Content-Type: application/json" \
  -H "X-DeriveWallet: $WALLET_ADDRESS" \
  -H "X-DeriveTimestamp: $TS" \
  -H "X-DeriveSignature: $SIG" \
  -d '{
    "subaccount_id": 42,
    "instrument_name": "ETH-PERP",
    "direction": "buy",
    "order_type": "limit",
    "time_in_force": "gtc",
    "amount": "2",
    "limit_price": "2500",
    "max_fee": "10",
    "mmp": false,
    "nonce": "1751558400000123000",
    "signature_expiry_sec": 1751558700,
    "signer": "0xCURATOR…",
    "signature": "0x…"
  }'

NAV is the vault subaccount’s live mark-to-market value from the risk engine, and share price ≈ NAV / total_shares. As you trade on behalf of the vault, the vault subaccount’s position values change. On each withdrawal, a management fee is charged, as well as a performance fee on any profits since the last withdrawal. The share price is computed after these fees are applied. The protocol ensures that deposits and withdrawals are never settled with a slippage to the mtm beyond maxSlippageBps set at vault creation.

const { nav_usd, simulated_share_price_usd } = await client.vaults.getVault(
  vaultId
);
console.log(
  `NAV $${nav_usd ?? '?'}, share price $${simulated_share_price_usd ?? '?'}`
);

# Coming soon.

// Coming soon.

curl -X POST https://api.derive.xyz/v3/public/get_vault \
  -H "Content-Type: application/json" \
  -d '{ "subaccount_id": 42 }'

Nothing is stored or settled per-trade — pricing is computed live, and hourly snapshots accumulate in getPerformanceHistory for the track record shareholders see.

Trading while requests are queued

Your positions and the settle loop interact in three ways worth engineering around: Redemption liquidity. Withdrawals pay out in the vault’s deposit asset. A vault that is fully deployed into positions cannot settle a large burn — unwind first, then settle. Curator stake floor. The protocol requires you to keep minimum skin-in-the-game. A withdrawal that would drop your own stake below the deployment-set floor is rejected (vault_curator_stake_below_min, 18013) — you cannot drain your seed while shareholders remain. See Winddowns for the exit order this implies.

Order types

Everything the normal trading API supports, the vault subaccount supports.

Process Deposits & Withdrawals

The settle loop your trading has to leave room for.

Get Started

Authentication & Keys

Trading Concepts

Permissionless Vaults

WebSocket

Reference

Trading while requests are queued

Order types

Process Deposits & Withdrawals

​How trading moves the share price

​Trading while requests are queued

Order types

Process Deposits & Withdrawals

How trading moves the share price

Trading while requests are queued