Choose TradeLocker Cloud
In Signal Copier, add a Cloud account and select TradeLocker as the provider. A paid Cloud plan and a supported server are required.
Connect an eligible TradeLocker account to the cloud adapter, apply your own risk rules, and route supported instructions from an authorized Telegram source. Test the complete broker lifecycle on demo before live funds.
Current route
The supported account connects to the TradeJournal Pro cloud adapter.
The password is not stored; rotating session tokens are encrypted at rest.
Risk, symbols, selected targets, and daily limits apply before dispatch.
Acceptance and reconciliation remain separate from parsing success.
A TradeLocker logo or login does not prove a broker's full order lifecycle. Certify the exact account and server on demo.
In Signal Copier, add a Cloud account and select TradeLocker as the provider. A paid Cloud plan and a supported server are required.
Enter the TradeLocker email, password, server, and account selection. The password is used for login and is not stored; rotating tokens are encrypted at rest.
Set account risk, allowed symbols, selected targets, daily-loss limits, and execution mode before routing any channel.
On demo, test entry, modification, partial close, breakeven, pending cancellation, close, and reconciliation against the final TradeLocker state.
Honest compatibility
“Limited” means the function exists in the beta path but still needs exact broker, server, symbol, volume, and order-state validation.
Beta adapter; provider and broker schemas vary.
Supported through the beta adapter; demo validation required.
Target plan depends on symbol and volume rules.
Shared command executor with broker-volume normalization.
Command supported; automated trigger remains beta.
Move or remove SL and move selected TP.
Supported, subject to broker-specific order state.
The beta adapter does not publish trailing parity yet.
A connection test proves authentication. It does not prove that every symbol, order type, protection rule, or management command behaves correctly at the broker.
Open guided setupTest one valid market entry and one supported pending entry.
Confirm absolute stop and target placement on the broker account.
Test modify, breakeven, partial close, cancel, and close one at a time.
Compare dispatched, provider response, broker order, fill, and journal state.
No. It is a beta cloud route. Provider schemas, server availability, symbol definitions, permissions, and broker behaviour can differ. The public compatibility matrix records the tested adapter version and current limitations.
No local trading terminal is required after a supported account connects. Execution uses the TradeJournal Pro cloud adapter, but provider and platform availability still apply.
The password is used for the login request and is not stored. Rotating access and refresh tokens are encrypted at rest. Reconnect the account if its session can no longer be refreshed or decrypted.
No universal compatibility is claimed. The server, account permissions, symbols, routes, volume rules, and order lifecycle must be tested on the exact demo account first.
No. Parsing, dispatch, provider acceptance, broker order state, and final fill are different stages. Verify the final TradeLocker order or position and review execution evidence in TradeJournal Pro.
Use the public matrix as the current product truth, then create broker-visible evidence on the exact TradeLocker account you intend to use.