A channel writes BUY BTC, and everyone appears to understand. One reader buys coins, another opens a perpetual position and a third trades a broker's crypto CFD. They share an underlying market reference, but their orders, collateral and closing behaviour are not interchangeable.
Before configuring a copier, identify the exchange, instrument type and account mode intended by the source. Then confirm that the selected route supports that combination. An exchange logo on a compatibility list is not a declaration that every product offered by that exchange is available through the connector.
In this guide
Decide what is being bought
Spot trading and derivative exposure have different account mechanics. A sell instruction might dispose of an owned balance in one arrangement and open or reduce short exposure in another. The destination's position mode and connector semantics must be explicit before an automated SELL is allowed to act.
AlgoWay's Binance integration guide separates market selection, account settings and API permissions. Those destination checks still matter when Telegram supplies the source instead of TradingView. Do not substitute one exchange's field names or behaviour for another's merely because both use API keys.
Read the quantity convention
A monetary allocation is not the same as a coin quantity. In a simplified spot example at 200 quote-currency units per coin, an allocation of 50 corresponds to 0.25 coins before fees and normalisation. Sending the number 50 as the coin quantity instead would request a very different order.
Likewise, order notional, initial margin and loss to a stop are separate figures. Leverage does not make the notional vanish, and a multiplier should not be assumed to represent an intended margin amount. The position-sizing guide explains the arithmetic and why the final accepted quantity is the number to verify.
| Decision | Check before enabling |
|---|---|
| Market | Exact spot or derivative instrument |
| Quantity | Coins, contracts or converted monetary amount |
| Position behaviour | Supported one-way or hedge treatment |
| Permissions | Required trading access for the chosen market |
| Protection | Supported stop and target order behaviour |
The exchange can reject an otherwise good-looking number
An instrument can impose a quantity step, minimum quantity and minimum notional. Prices also have allowed increments. Binance documents these separately in its official filter reference; use the corresponding official specification for your exchange rather than assuming the values match.
Consider a hypothetical quantity step of 0.01 and a calculated size of 0.257. A valid size must fit that increment, and its resulting value still needs to satisfy other rules. Splitting a small total across several targets can make individual legs invalid even when the unsplit order would pass.
Keep the API connection specific
Use credentials and account permissions appropriate to the supported integration. AlgoWay's Binance guide states that withdrawal permission is not required for its trading workflow. That is a concrete permission distinction, not a reason to make wider claims about every third-party service's security or storage practices.
Account eligibility and regional product access must also be checked at the exchange. A successful key does not prove that a particular derivative is available to the account. Preserve the actual rejection response when something fails, because it often distinguishes a permission problem from a malformed signal.
Prove one market before adding another
Follow the setup walkthrough with one destination and one unambiguous instrument. Compare the parsed symbol, mapped destination name, accepted quantity and final order state. Use a supported test environment where available; do not assume every exchange route offers one.
Only then add further markets or sources. Keep routes separate where the same shorthand means different instruments, and consult the market-coverage comparison when choosing software. The useful promise is a verified route to a specific market, not the largest collection of exchange badges.
Put the route to a demo test
Use the current setup instructions and verify the resulting orders in your destination account. Start with a configuration you can inspect before adding more sources.
Open TelegramSignal in AlgoWay