User Manual
Everything you need to know about Crypto Broker — from first setup to advanced automation.
Conditional Orders
Conditional Orders let you define IF/THEN automation rules that execute automatically — even when the app is running in the background or in the menu-bar tray. This feature is available on desktop (macOS & Windows) only.
Conditional Orders place real orders using your exchange API credentials. Double-check every rule before activating it. Always test with small amounts first.
How it works
The app monitors your open orders every 30 seconds in the background. When a trigger order fills, it checks whether any active rule matches that fill, optionally evaluates a price condition, then places a new order on the configured target exchange.
Example: When my SHIB/USDT sell order on Kraken fills and releases at least $500 USDT → buy ETH at market on KuCoin using 100% of the released USDT.
Opening the Conditional Orders window
Click the ⚡ lightning bolt button in the desktop toolbar. This opens the Conditional Orders overlay panel.
Creating a rule
Click + Add Rule.
In the rule builder, configure the Trigger: select the exchange, the trading pair whose fill will trigger the rule, and the minimum amount of released currency (or leave as "any amount").
Configure the Action: choose the target exchange, the crypto to buy or sell, the order type (Market or Limit), and the amount — either a fixed USD value or a percentage of the released funds.
Optionally add a Price Condition — the action only fires if the target crypto's current price is above or below a threshold.
Click Save Rule. The rule becomes active immediately.
Managing rules
Each rule card shows a live status dot (active / paused), a human-readable summary, the last triggered time, and a trigger count. You can pause, edit, or delete rules at any time. The monitoring ticker at the bottom of the panel shows when the last check ran.
Liquidity Pool display
At the top of the Conditional Orders window, a row of currency cards shows the total capital currently deployed in open orders, grouped by quote currency (USDT, USDC, USD, EUR, etc.). This gives you an at-a-glance view of how much liquidity would be released if your ladders filled completely.
Automatic withdrawals
A rule's action can be a withdrawal instead of an order: when the trigger fills, the funds it produced are sent to a wallet you have already set up on the exchange. This is entirely optional — it is off by default, and everything else in Crypto Broker works without it.
Withdrawals cannot be undone. An API key with withdrawal permission is more dangerous than a trading key: if it is ever stolen, funds can leave your account. Only enable this if you want it, and secure the key as described below.
What you need
A withdrawal address saved on the exchange. Crypto Broker never stores wallet addresses and cannot send funds to an address you type into the app. It can only use destinations you have already added and confirmed in your exchange account, and it refers to them by the name you gave them there.
An API key with withdrawal permission. Edit or recreate your key on the exchange and enable its withdrawal permission. In Crypto Broker, open Settings → Exchanges, select the exchange, and click Check permissions — the Withdraw badge should turn green.
The master switch. Go to Settings → Parameters → Automatic Withdrawals and turn it on. Until you do, no rule can withdraw anything, even with a key that has the permission.
Creating a withdrawal rule
Create a rule as usual and set up the trigger.
In the Action block, change the dropdown from "Add new order" to Withdraw funds.
Pick a destination. Only destinations matching the asset your trigger will produce are listed, and the network is shown for confirmation — you never choose it separately, because the address you saved on the exchange already determines its chain.
Choose the amount: a percentage of what the trigger produced, or a fixed amount. Optionally set a fee limit so the withdrawal is cancelled if the network fee would take too large a share.
Save the rule, then confirm it once. The first time a withdrawal rule would fire, it stops and asks. Nothing is sent until you confirm, and confirming does not withdraw anything at that moment — it allows future runs. Changing the destination or amount asks again.
What gets withdrawn
The rule withdraws what the trigger credited to your account. If a buy order fills, that is the crypto you just bought. If a sell order fills, it is the proceeds. The rule summary always names the asset, for example "Withdraw all USDC received to 'My Ledger' on Kraken".
"Withdraw all" means whatever is actually available. Exchanges take their trading fee out of the fill, so slightly less arrives than the order was for — the amount is reduced to what can really be sent. A fixed amount you typed is never reduced; if it exceeds your balance the withdrawal is cancelled and the reason is logged.
Supported exchanges
Automatic withdrawal is currently available on Kraken, and is marked BETA in the app while the other exchanges are still being verified. Fiat is not withdrawn directly — crypto and stablecoins only. Bank withdrawals must be made on the exchange itself.
Selling into a currency, then withdrawing
Because fiat cannot be withdrawn, a sell that settles into USD or EUR would otherwise have no route out. A rule can chain steps to solve this: the trigger fills, an action buys a stablecoin with the proceeds, and a withdrawal step then sends that stablecoin to your wallet.
Example: your ETH/USD sell fills → buy USDC with the released USD → withdraw the USDC to your wallet.
Each step waits for the one before it to actually complete. The withdrawal does not start until the stablecoin purchase has really filled, and it uses the amount that was genuinely received — not the amount that was expected. If the purchase does not fill, the chain stops rather than trying to withdraw funds that have not arrived.
The exchange takes its trading fee out of the conversion, so slightly less arrives than the sale was worth. Choosing "withdraw all" handles this — it moves whatever is actually there.
Security
Your API keys are stored encrypted by your operating system (macOS Keychain, Windows Credential Manager, Android Keystore) and are never sent to our servers. That protects a key at rest, but it cannot limit what the key is allowed to do — so if you enable withdrawal permission, also do the following on the exchange:
- Restrict the key to your IP address.
- Enable the withdrawal address whitelist, so funds can only ever go to addresses you approved.
- Use a separate key for withdrawals rather than reusing your trading key.
Your data on this device
Everything Crypto Broker keeps on your device is encrypted — not only your API keys. Trade history, deposits and withdrawals, positions, staged orders and conditional order rules are all stored encrypted, with the key held in your operating system's secure store alongside your API keys.
Data is also kept separate per account. If two people use the same computer, or you have more than one Crypto Broker account, each one's keys, history and rules are only visible while that account is logged in.
Because the encryption key lives in your operating system's secure store, resetting your keychain or credential manager makes the stored data unreadable — the same event that would lose your API keys. Trade history and balances simply re-download from the exchange; staged local orders and conditional rules do not, so export or note anything you cannot recreate before resetting an operating system credential store.
Before every withdrawal, Crypto Broker re-reads your destination list from the exchange and cancels if the destination is gone, checks that the key still has permission, and requests a fee quote — refusing if the fee moved above what was quoted. Every step is written to the console at the bottom of the Conditional Orders window.
Need help with something not covered here? Contact support.