How to connect your broker
What each broker type needs, how PIPFORGE encrypts credentials, and how real orders are sent.











The two pieces you are connecting
A broker connection is where PIPFORGE sends trades. A signal source is where PIPFORGE receives trade ideas. Today PIPFORGE's own strategies generate the signals you see on the Signals page. TradingView and Telegram are optional ways to add more signals later.
Credential security
PIPFORGE never stores your MT5 broker password. For crypto exchanges, PIPFORGE only asks for a trade-only API key. Your exchange login password is never requested. All API keys are encrypted with AES-256-GCM before they are saved.
Binance
- Log in to Binance and go to Wallet → API Management.
- Create a new API key. Enable only Spot & Margin trading.
- Disable withdrawals. Restrict the key to PIPFORGE's server IP if you can.
- In PIPFORGE Trading connections choose Binance and paste the API key and secret.
- Leave 'Use live endpoints' unchecked to practise on the Binance Spot Testnet first.
Bitget
- Log in to Bitget and create an API key with trade permission only.
- Make sure withdrawals and transfers are disabled.
- Copy the API key, API secret and passphrase.
- In PIPFORGE Trading connections choose Bitget and paste the three values.
- Leaving live endpoints off lets you practise before using real funds.
Bybit
- In Bybit, create an API key with Unified Trading Account permissions.
- Allow trade. Do not allow withdrawal.
- Paste the API key and secret into PIPFORGE's Bybit connection form.
- Optional: add a sub-account name.
OKX
- Create an API key in OKX with trade permission only.
- Copy the API key, API secret and passphrase.
- Paste all three into PIPFORGE's OKX connection form.
- Withdrawal permission must be OFF.
Deriv
- Deriv supports OAuth 2.0 or a personal access token (PAT).
- Create an integration token in your Deriv account with trade-only scope.
- Paste the token and your account ID into PIPFORGE.
- Your Deriv login password is never asked for or stored.
cTrader
- Use a cTrader Open API application token with trade permission.
- Enter your cTrader ID, application client ID and the access token.
- This authorises trades without sharing your broker password.
MetaTrader 5 (MT5) bridge — no password needed
Retail MT5 accounts do not have a public web API. PIPFORGE talks to a small Expert Advisor (EA) that lives inside your MT5 terminal. Because the terminal is already logged in to your broker, you do not give PIPFORGE your broker password.
- In PIPFORGE Trading connections choose MetaTrader 5.
- Enter a label (for example 'My Exness MT5') and optionally your account number and broker name.
- Save. PIPFORGE shows a long connection code like br_xxxxxxxx… and a download link for PipforgeBridgeEA.mq5.
- Copy the code, download the EA, and follow the install steps in /help/mt5-bridge.
- Keep the chart with the EA open. PIPFORGE will send trades to that MT5 account.
TradingView alerts (signal source)
A TradingView webhook is a signal source, not a broker. It sends alert messages to PIPFORGE so your TradingView strategies can also create copy-trades.
- In Trading connections, choose TradingView.
- Give it a label and save. Copy the generated webhook URL.
- In TradingView, open the alert and enable the Webhook URL option.
- Paste the PIPFORGE webhook URL into the alert.
- The alert message must be JSON with fields such as ticker, action, close, stopLoss and takeProfit.
- PIPFORGE will then forward the alert to your connected execution account (MT5, Binance, etc.).
Telegram and custom webhooks (signal sources)
Telegram and custom webhooks are also signal sources. Use them to feed alerts from private channels, bots or your own software into PIPFORGE. They do not execute trades directly; they only create copy-trades that are routed to your execution account.
What happens next
When a signal arrives, PIPFORGE runs your guardrails and sends a real order to your chosen execution account. Real execution is live today for Binance and MetaTrader 5. Bitget, Bybit, OKX, Deriv and cTrader execution accounts can be saved but are not yet placing live orders; they will be enabled in an upcoming release. MT5 orders are queued for the EA, which places them in your terminal and reports the broker ticket ID back. 'Executed' means the broker confirmed the order.