Create a restricted API key
Use a separate testnet or sub-account key with Futures trading permission. Never enable withdrawal permission.
Telegram → Binance Futures
Copy Telegram crypto signals to Binance—with a hard USDT cap
Route supported market-entry signals to Binance USDT-M Futures, attach one selected take-profit and an available stop, and limit every order by an explicit USDT amount. Start on testnet and verify the final exchange state.
Pro or Lifetime plan required · Testnet first · Never enable withdrawals
Current route status
Limited—not EA parity
Cloud execution
No MetaTrader terminal or local EA is required for this exchange route.
Market entry
Supported futures symbols with an explicit USDT amount and hard cap.
Entry protection
One selected TP and an available stop can be submitted with the entry.
No management parity
Trailing, partial close, and the full EA/Cloud command lifecycle are not exposed.
Connect Binance
Open Crypto Futures Accounts, choose the exchange, enable testnet for the first run, and verify that the available USDT balance loads.
Set the USDT guardrails
Choose the per-order USDT amount and hard maximum. The executor rejects an invalid amount or any request above the configured safety cap.
Send one test signal
Route one authorized channel, send a supported crypto pair and direction, then verify the final Binance futures order and its protection.
Minimum API-key safety
- Create a separate key with only Futures trading permission.
- Disable withdrawals—TradeJournal Pro never needs that permission.
- Use testnet first, then a restricted sub-account for any live validation.
- Revoke and replace the key immediately after suspected exposure.
What the test must prove
Confirm symbol normalization, available balance, minimum notional, quantity step, direction, entry, stop, selected TP, and the final exchange position. A parser result alone is not execution evidence.
Telegram to Binance questions
Does Telegram to Binance support spot trading?
No. The current TradeJournal Pro route targets Binance USDT-M Futures. The public compatibility matrix does not claim spot execution.
Can one signal open several exchange take-profit orders?
No. The current route submits one selected broker TP. If several targets are selected, it uses the first available target from the resolved selection plan.
Does the exchange route support close, breakeven, trailing, or partial close commands?
Not through the full shared management lifecycle today. Entry SL/TP submission is supported, but later EA-style management commands are not published as supported for exchange positions.
How is order size controlled?
The route uses an explicit USDT order amount with a separate hard maximum. It converts that notional into exchange quantity using current price, quantity step, minimum quantity, and minimum notional rules.
How are my API credentials stored?
New and migrated exchange credentials are encrypted at rest. Use trading-only keys, disable withdrawals, restrict access where the exchange permits it, and revoke the key immediately if you suspect exposure.
Does submitted mean the Binance position is guaranteed?
No. Parsing, dispatch, API acceptance, protection placement, and the final exchange position are different stages. Always confirm the result in the exchange account.
Use testnet before a live API key
The exchange route is intentionally smaller than the MT4/MT5 execution lifecycle. Validate only the features published on the compatibility page.