Webhook to Match-Trader — send JSON signals for prop accounts

Risk warning: Trading CFDs and other leveraged products is complex and carries a high risk of losing money rapidly because of leverage. Industry data indicates that 70–80% of retail trading accounts lose money on these products. Risk disclosure · Past performance.

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.

1. 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. 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. 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. 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. 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. 6

   Verify with Recent alerts

   Check Recent alerts under Settings → Advanced → TradingView Alerts to confirm PipSync interprets each payload correctly.

Typical setup time: about 11 minutes.

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

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.

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.

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.

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.

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.