# Webhook to Match-Trader — send JSON signals for prop accounts Source: https://pipsync.io/en/webhook-to-match-trader Last updated: 2026-06-08 To send a webhook to Match-Trader, POST a flat JSON payload to your unique PipSync webhook URL: PipSync validates the secret token and saves the payload as a signal on the Signals page for you to review. No plugin, EA or VPS is required. A webhook from your own system is never traded automatically: it always becomes a signal for your approval. Only alerts that TradingView itself sends can auto-trade, and only after an opt-in on the Advanced plan; on Match-Trader accounts the risk of indices, gold or crypto cannot be measured for now, so such alerts are not auto-traded there. Telegram and Discord signals execute on Match-Trader. This route is source-agnostic. Any system that can make an HTTPS POST — a custom bot, a backtester, a spreadsheet macro, a backend service, or a charting platform — can send signals to PipSync through the same endpoint. The payload describes the instrument, direction and levels; PipSync handles authentication and sizing, so your own infrastructure never needs broker credentials or to stay online. ## Webhook to Match-Trader at a glance | | | |---|---| | Inbound source | Any system that can HTTPS POST flat JSON (source-agnostic, not only TradingView) | | Destination | Telegram and Discord signals execute on Match-Trader; a webhook from your own system is saved as a signal for your approval | | Payload | Flat JSON: instrument, direction, entry, sl, tp1 — all required | | Credential | Secret token inside your unique per-workspace webhook URL; keep it secret and regenerate under Settings → Advanced → TradingView Alerts if you suspect a leak | | Risk sizing | Not applied to webhook signals, which always wait for your approval; sizing and limits apply to Telegram and Discord signals | | Feedback | Signed outbound webhooks (HMAC-SHA256) + REST read API (Enterprise); dashboard on all plans | | Auto-trade | Never for a webhook from your own system; only TradingView's own alerts can auto-trade (opt-in, Advanced plan), and for now not indices, gold or crypto on Match-Trader accounts | | Price | Webhook integration needs a plan that includes it (the Advanced plan) | ## How do I connect a custom webhook to Match-Trader? Wire any system that can POST JSON to PipSync, which saves each payload as a signal for your approval; a webhook from your own system is never traded automatically. Your source only needs to send a flat payload. 1. **Create your PipSync account and subscribe to a plan** — Sign up at app.pipsync.io (the $0 Free plan needs no card but only parses signals), then subscribe to a plan that includes webhook integration (payment method required), so you can generate the webhook URL and check Recent alerts. 2. **Match-Trader for Telegram and Discord signals** — For Telegram and Discord signals, open Trading Accounts → Add account and choose Match-Trader; PipSync connects via REST and WebSocket with no plugin or EA. On Match-Trader accounts the risk of indices, gold or crypto cannot be measured for now, so such alerts are not auto-traded there. 3. **Generate your webhook URL** — Go to Settings → Advanced → TradingView Alerts and click Generate webhook URL. PipSync generates a unique URL containing a secret token and shows it only once; it is the credential your sending system uses to authenticate. Keep it secret: with TradingView auto-trade on, anyone who has the URL can trigger trades. Regenerate it if you suspect a leak. 4. **Send the flat JSON payload** — Configure your system to POST flat JSON: instrument, direction (buy/sell), entry, sl and tp1, with sl and tp1 above 0. Other fields such as lots are ignored, so server-side sizing always runs. 5. **Set server-side risk rules** — Define percent-risk or fixed-lot sizing, min/max lots and max open positions in the dashboard. These apply to signals that are executed (Telegram and Discord), which matters for drawdown-limited prop accounts. 6. **Verify with Recent alerts** — Check Recent alerts under Settings → Advanced → TradingView Alerts to confirm PipSync interprets each payload correctly. ## What payload does a webhook to Match-Trader use? A webhook to Match-Trader uses a flat JSON payload that any system can build without a library. The required fields are instrument, direction ("buy" or "sell"), entry, sl and tp1. Everything else is ignored. entry, sl and tp1 are absolute prices above 0 — a payload with 0 is rejected, not read as market. Use tp1 to tp5 for several take-profit targets. There is no close action, and lots and comment have no effect. - instrument: the symbol, e.g. EURUSD (upper-cased, letters and digits only) - direction: buy or sell (long and short also work); there is no close action - entry: absolute entry price, above 0 - sl: absolute stop-loss price, above 0 - tp1: at least one absolute take-profit price, above 0 - other fields: ignored, including lots and comment ## How is the webhook URL secured? Each custom source gets a unique webhook URL that contains a secret token, and that token is the only credential. Any system holding the URL can submit signals and, with TradingView auto-trade on, trigger trades, so treat it like a password: keep it out of public repositories, client-side code and shared logs. If you suspect a leak, regenerate it under Settings → Advanced → TradingView Alerts. Regenerating issues a new token and invalidates the old one immediately, so a leaked endpoint stops working as soon as you replace it. Your Match-Trader broker login is never sent in the payload and never leaves PipSync. ## Can a webhook to Match-Trader trade automatically? A webhook from your own system — a bot, a script or another tool — is never traded automatically: it always becomes a signal for your approval. Only alerts that TradingView itself sends, from its published sender addresses, can auto-trade, and only after you opt in. Auto-trade is opt-in and off by default. It needs the Advanced plan: you set it up under Settings → Advanced → TradingView Alerts with an explicit consent (Set up auto-trading), then link your accounts and switch auto-trade on under Accounts & auto-trade. On Match-Trader accounts the risk of indices, gold or crypto cannot be measured for now, so such alerts are not auto-traded there. Telegram and Discord signals execute on Match-Trader. Keep the webhook URL secret: with auto-trade on, anyone who has it can trigger trades. Regenerate it if you suspect a leak. ## How does PipSync reach Match-Trader without a plugin? PipSync connects to Match-Trader / Match-Trade through Match-Trade's direct REST and WebSocket interface for Telegram and Discord signals, so there is no plugin, EA, cBot or downloaded bridge to maintain. A webhook from your own system is saved as a signal for your approval and is never traded automatically. Because the connection is server-side, your sending system never needs to stay online after the POST. The webhook can fire from a backend cron job, a desktop script or a serverless function; once PipSync receives it, the signal is stored independently of your machine. ## Does the webhook set my position size? No. A lots value in the payload is ignored, and a webhook from your own system is never traded automatically. For Telegram and Discord signals, percent-risk sizing calculates the lot size from your account balance and the stop-loss distance. For those executed signals, sizing and risk logic run server-side, with min/max lots and a cap on max open positions. ## Can I receive feedback about my webhook signals? Yes. PipSync sends signed outbound webhooks for events such as trade.opened, trade.closed, tp_hit and sl_hit, each carrying an HMAC-SHA256 signature in the X-PipSync-Signature header and retried up to five times with backoff. This lets your own system reconcile state without polling. For pull-based access there is a REST read API (GET /v1/signals, GET /v1/trades, documented via OpenAPI 3.1 at /api/v1/openapi.json) available on the Enterprise plan, while the dashboard shows every parsed signal and order on all plans. Inbound webhooks are rate-limited; on an HTTP 429, back off with jitter and retry. ## FAQ ### Do I need TradingView to send a webhook to Match-Trader? No. This route is source-agnostic: any system that can make an HTTPS POST with flat JSON can send signals to PipSync. TradingView is one option, but custom bots, backtesters, backend services and scripts all work the same way through the same endpoint. Only alerts that TradingView itself sends can auto-trade, after an opt-in; a webhook from your own system always becomes a signal for your approval. ### Is PipSync a signal provider or giving trading advice? No. PipSync is cloud-based execution infrastructure that turns the alerts you or your system send into signals for your broker accounts. It does not provide signals, sell strategies or offer investment advice, and it never decides what to trade on your behalf. ### Can I run webhook-to-Match-Trader on a prop-firm account? A webhook from your own system never trades automatically: it becomes a signal for your approval. Telegram and Discord signals do execute on Match-Trader, and TradingView alerts auto-trade only if you opt in, so verify your prop firm permits automated or copy-traded execution first. Rules differ by firm and often differ between the evaluation and funded stages, so check your firm's terms before enabling live trading. ### Can a webhook close a Match-Trader position? PipSync does not close positions from webhooks or alerts. A direction other than buy or sell is rejected, so exits happen by the stop-loss and take-profit on the position, or by you on your Match-Trader platform. ### Can a webhook from my own system trade on Match-Trader automatically? No. A webhook from your own bot, script or tool is never traded automatically: it always becomes a signal for your approval. Only alerts that TradingView itself sends, from its published sender addresses, can auto-trade, and only after you opt in. ### Do TradingView alerts auto-trade on Match-Trader? Only if you opt in: auto-trade is off by default and needs the Advanced plan. On Match-Trader accounts the risk of indices, gold or crypto cannot be measured for now, so such alerts are not auto-traded there. ### Do I need a VPS or plugin to keep this running? No. PipSync connects to Match-Trader via direct REST and WebSocket entirely in the cloud, with no plugin, EA, cBot or terminal kept open. Once a webhook is received, the signal is stored even when your own computer is off. ### How do I control lot size from the webhook? You do not: a lots field in the payload is ignored. PipSync's server-side fixed-lot or percent-risk rules calculate the size, clamped between your min and max lots, which suits drawdown-limited accounts. ### What happens if I hit the inbound rate limit? Inbound webhooks are rate-limited. If you receive an HTTP 429, back off, ideally with added jitter, before retrying. ## Related - [Match-Trader copier — route Telegram and Discord signals to Match-Trader](https://pipsync.io/en/match-trader-copier) - [TradingView to Match-Trader — signals you review, or opt-in auto-trade](https://pipsync.io/en/tradingview-to-match-trader) - [Telegram to Match-Trader — copy signals automatically](https://pipsync.io/en/telegram-to-match-trader) - [Webhook to MT5 — send JSON signals from any system](https://pipsync.io/en/webhook-to-mt5) - [Webhook to cTrader — send your own alerts as signals](https://pipsync.io/en/webhook-to-ctrader) - [What is Match-Trader?](https://pipsync.io/en/what-is-match-trader) - [Prop firm signal copier — one source, every account](https://pipsync.io/en/prop-firm-signal-copier) --- PipSync is a signal execution tool. It does not provide trading signals, does not guarantee any trading results and is not investment advice. Trading leveraged products involves substantial risk of loss.