ATC Trade Sources
Awesome Trades Copier - Trade Sources
A Trade Source is any platform Awesome Trades Copier can read live trade signals from. Once connected, every open, modify, or close event on the source is captured and copied to your linked destination accounts in real time.
ATC currently supports six trade sources, spanning MetaTrader terminals, messaging platforms, custom API integrations, and browser-based prop firm platforms.
How it works
Every source feeds into the same ATC Node pipeline, so switching or combining sources doesn't change how copying, risk settings, or symbol mapping behave downstream.
Overview
| Source | Type | Connection Method | Typical Use |
|---|---|---|---|
| MT4 | Trading terminal | EA installed on source terminal | Signal providers running strategies on MetaTrader 4 |
| MT5 | Trading terminal | EA installed on source terminal | Signal providers running strategies on MetaTrader 5 |
| Telegram | Messaging platform | Bot listens to channel/group | Signal providers who post trade calls as text messages |
| API Request | Custom integration | REST webhook (POST) | Bots, algos, or third-party tools sending structured signals directly |
| HankoX | Prop firm platform | Browser automation bridge | Traders funded on HankoX evaluating or funded accounts |
| Rebels Funding | Prop firm platform | Browser automation bridge | Traders funded on Rebels Funding evaluating or funded accounts |
1. MT4
A lightweight Expert Advisor (EA) is attached to the source MT4 chart. It watches the terminal for order events (open, modify, close, partial close) and forwards them instantly to the ATC Node.
Requires: MT4 terminal running with the ATC source EA attached and algo trading enabled.
2. MT5
Same principle as MT4, using an MT5-native EA. Supports MT5-specific order types and hedging/netting account modes.
Requires: MT5 terminal running with the ATC source EA attached and algo trading enabled.
3. Telegram
ATC connects to a Telegram channel, group, or bot as a listener and parses incoming messages for trade instructions (symbol, direction, entry, SL/TP). Useful for signal providers who don't trade on MetaTrader directly but publish calls as text.
Requires: Bot access or user session connected to the source channel/group, and messages following a recognizable signal format.
4. API Request
For signal sources that aren't a terminal or chat app — custom bots, algorithmic strategies, or third-party platforms — ATC exposes a REST webhook. Sending a structured JSON payload to the endpoint triggers a trade the same way a terminal signal would.
Requires: A source system capable of sending authenticated HTTP POST requests to your ATC API endpoint.
5. HankoX
ATC connects to HankoX accounts through a browser automation bridge, monitoring the account's trading activity and mirroring it to your destination accounts. Useful for copying your own or a provider's HankoX evaluation or funded account.
Requires: Valid HankoX login credentials linked in ATC and an active automation node.
6. Rebels Funding
Same approach as HankoX — a browser automation bridge watches trading activity on a Rebels Funding account and copies it in real time. Commonly used to mirror prop-firm challenge or funded accounts into other accounts.
Requires: Valid Rebels Funding login credentials linked in ATC and an active automation node.
Choosing a source
- Already trading on MetaTrader? Use MT4 or MT5 — lowest latency, most reliable.
- Following a signal provider who posts in a chat? Use Telegram.
- Building your own bot or strategy? Use API Request for full control over the payload.
- Trading on a prop firm platform without native MT4/MT5 access? Use the matching bridge — HankoX or Rebels Funding.