Webhook to Match-Trader — execute JSON signals on prop accounts

Risk warning: CFDs are complex instruments with a high risk of losing money rapidly due to leverage. 70–80% of retail investor accounts lose money when trading CFDs. 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 drive your Match-Trader prop account through the same endpoint. The payload describes the action, symbol and optional stops; PipSync handles authentication, sizing and execution on the broker side, so your own infrastructure never needs broker credentials or to stay online.

1. 1

   Create a free PipSync account

   Sign up at app.pipsync.io. The Free plan is EUR 0 and needs no credit card, so you can build and test the integration before paying.

2. 2

   Connect your Match-Trader account

   Add your Match-Trader / Match-Trade account in the dashboard. PipSync connects directly via REST and WebSocket using your broker login, with no plugin, EA or terminal to install.

3. 3

   Create a custom webhook source

   Add a custom JSON webhook source. PipSync generates a unique URL containing a secret token, which is the credential your sending system uses to authenticate.

4. 4

   Send the flat JSON payload

   Configure your system to POST flat JSON: action (buy/sell/close), symbol matching the broker's exact name, and optional price, sl, tp, lots and comment. Omit lots to let server-side sizing run.

5. 5

   Set server-side risk rules

   Define percent-risk or fixed-lot sizing, max open trades and symbol filters in the dashboard. These apply before any order reaches Match-Trader, which matters for drawdown-limited prop accounts.

6. 6

   Verify in Test Mode, then go live

   Use Test Mode to confirm PipSync interprets each payload correctly without executing, or run on a demo Match-Trader account first, then enable live execution.

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 action ("buy", "sell" or "close") and symbol, which must match your broker's exact symbol name. Everything else is optional and defaults sensibly.

Optional fields give you precise control over each order. Set price to 0 for a market order, or pass an absolute price for a pending order; sl and tp are absolute prices where 0 omits the level. The comment field is free text for your own tagging.

• action: "buy", "sell", or "close" (close flattens the open position on that symbol)
• symbol: must match the broker's exact symbol name
• price: 0 for market, or an absolute entry price
• sl / tp: absolute prices, 0 to omit
• lots: overrides configured sizing for that trade — omit to let server-side sizing run
• comment: optional free-text tag

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 orders, so treat it like a password: keep it out of public repositories, client-side code and shared logs.

If a URL is ever exposed, rotate it from the dashboard. Rotation 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.

PipSync connects to Match-Trader / Match-Trade through Match-Trade's direct REST and WebSocket interface, so there is no plugin, EA, cBot or downloaded bridge to maintain. Match-Trader is a common white-label backend for prop firms, and this direct integration means execution runs entirely in PipSync's cloud.

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, order placement and management continue independently of your machine.

Percent-risk sizing calculates the lot size from your account equity and the stop-loss distance, so each trade risks a defined percentage rather than a fixed lot. On prop accounts with daily and maximum drawdown limits, this keeps per-trade exposure proportional as equity moves, which matters when a single oversized order can breach a limit.

All sizing and risk logic runs server-side before any order reaches Match-Trader. You can also cap max open trades and apply symbol filters. If a payload includes an explicit lots value it overrides the configured sizing for that one trade, so omit lots whenever you want the server-side percent-risk rule to apply.

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 per minute and the limit scales by plan, from 10 per minute on the entry tier up to custom on Enterprise; a 429 returns Retry-After, so back off with jitter.