Webhook to Binance — trade crypto from any system via JSON

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.

Unlike a TradingView-only integration, this route is source-agnostic. Any program, script, backtester, cron job or bot that can make an HTTPS POST can drive Binance Futures the same way, because PipSync only cares about the JSON body, not where it came from. Server-side risk controls and SL/TP mapping run before any order reaches Binance, and a reduce-only flag lets you close positions safely without flipping direction.

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 wire up the full webhook flow before deciding on a paid tier.

2. 2

   Create a trade-only Binance API key

   In your Binance account, create an API key with futures trading enabled and withdrawals disabled. Add the key and secret to PipSync so it can place USD-M and COIN-M orders on your behalf without ever being able to move funds.

3. 3

   Configure your custom webhook source

   In PipSync, add a custom JSON webhook source. PipSync generates a unique URL containing a secret token; treat that token as the credential and rotate it from the dashboard if it is ever exposed.

4. 4

   Build the JSON payload

   Have your system POST flat JSON with action (buy, sell or close), symbol matching Binance's exact contract name, and optional price, sl, tp, lots and comment. Use absolute prices for sl and tp, set 0 to omit, and omit lots to let server-side sizing decide.

5. 5

   Set server-side risk rules

   Configure fixed-lot or percent-risk sizing, max open trades, symbol filters and optional manual approval. These rules are enforced before any order reaches Binance, so they apply even when your computer is off.

6. 6

   Verify in Test Mode, then go live

   Enable Test Mode to confirm PipSync parses each incoming payload correctly without executing. Once the interpretation looks right, switch to live and your webhook starts placing real Binance Futures orders 24/7.

Typical setup time: about 11 minutes.

A webhook to Binance Futures needs a single flat JSON object that PipSync maps to a Binance order. There are no nested structures and no Binance-specific fields to learn; you send a small, predictable body and PipSync handles the broker translation.

The core fields are straightforward, and most are optional so you only send what a given trade needs.

• action: "buy", "sell" or "close" (close flattens the open position on that symbol)
• symbol: must match Binance's exact contract name for USD-M or COIN-M
• price: optional, set 0 for a market order
• sl and tp: absolute prices, set 0 to omit either
• lots: overrides your configured sizing for that trade; omit to let server-side sizing run
• comment: optional free-text label for your own records

The difference is that this route is source-agnostic: any system that can make an HTTPS POST can drive Binance Futures, not just TradingView alerts. PipSync reads the JSON body and does not care whether it came from a Python script, a backtester, a cron job, a no-code automation or a custom bot.

TradingView webhooks also require a paid TradingView plan, whereas a custom webhook has no such dependency. If your strategy lives in your own code or in another platform, a custom JSON webhook is usually the cleaner fit, and the payload format is identical so you can migrate either way without rewriting your logic.

Leverage and liquidation are governed by Binance, not by PipSync. PipSync places orders against your account, but your leverage setting, margin mode and liquidation price are determined by Binance's futures engine and the contract you trade.

Because Binance Futures is a leveraged product, losses can exceed your initial margin and positions can be liquidated. Server-side SL/TP mapping and sizing help you express risk per trade, but they do not remove the underlying liquidation risk. Size positions conservatively and treat stop-losses as risk controls, not guarantees of an exact exit price during fast or illiquid markets.

To close a position, send action "close" for the symbol and PipSync flattens the open position on Binance using a reduce-only order, so it reduces or closes rather than opening a new opposite trade. This keeps your intent unambiguous when you are flat-versus-open logic is driven by an external system.

For execution feedback, 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. A REST read API (GET /v1/signals and GET /v1/trades, documented in the OpenAPI 3.1 spec) is available on the Enterprise plan, and 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 requests per minute on the entry tier up to a custom limit on Enterprise. This protects your account and Binance from runaway or duplicated alerts.

When you exceed the limit, PipSync returns HTTP 429 with a Retry-After header. Your sender should back off for the indicated interval and add jitter so retries do not all arrive at the same instant. For high-frequency strategies, batch or debounce signals upstream and choose a plan whose limit matches your expected throughput.