Webhook to Binance — send crypto signals from any system via JSON

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.

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 send signals the same way, because PipSync reads the JSON body whatever system sent it. Where it came from matters only for auto-trade, which your own system can never trigger.

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

   Create a trade-only Binance API key

   For Telegram and Discord signals, create an API key with futures trading enabled and withdrawals disabled and add it under Trading Accounts → Add account in PipSync. Binance accounts are gateway-connected, so for now the risk of a crypto trade cannot be measured on them: an alert is not auto-traded there; it is only recorded as a signal and cannot be placed there from PipSync for now.

3. 3

   Generate your webhook URL

   In PipSync, 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; treat that token as the credential and keep it secret: with auto-trade on, anyone who has the URL can trigger trades. Regenerate it if you suspect a leak.

4. 4

   Build the JSON payload

   Have your system POST flat JSON with instrument (for example BTCUSDT), direction (buy or sell), entry, sl and tp1. Use absolute prices above 0 for entry, sl and tp1; other fields such as lots are ignored.

5. 5

   Set server-side risk rules

   Sizing, min/max lots and max open positions apply to signals that are executed (Telegram and Discord), even when your computer is off; webhook signals wait for your review.

6. 6

   Verify with Recent alerts

   Check Recent alerts under Settings → Advanced → TradingView Alerts to confirm PipSync parses each incoming payload correctly. Once the interpretation looks right, your webhook feeds real signals 24/7.

Typical setup time: about 11 minutes.

A webhook to Binance Futures needs a single flat JSON object that PipSync turns into a signal. There are no nested structures and no Binance-specific fields to learn; you send a small, predictable body.

The core fields are straightforward, and all five are required.

• instrument: the contract name for USD-M or COIN-M, e.g. BTCUSDT (crypto spellings such as BTCUSD or XBTUSD are normalised to BTCUSDT)
• 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

The difference is that this route is source-agnostic: any system that can make an HTTPS POST can send signals to PipSync, 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. Both TradingView and custom webhooks use PipSync's webhook integration, which needs a plan that includes it (the Advanced plan), and the payload format is identical. What differs is auto-trade: only alerts that TradingView itself sends, from its published sender addresses, can auto-trade, and only after you opt in; a webhook from your own system always becomes a signal for your approval.

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. Binance accounts are gateway-connected, so for now the risk of a crypto trade cannot be measured on them: an alert is not auto-traded there; it is only recorded as a signal and cannot be placed there from PipSync for now. Telegram and Discord signals still execute on Binance Futures.

Keep the webhook URL secret: with auto-trade on, anyone who has it can trigger trades. Regenerate it if you suspect a leak.

Leverage and liquidation are governed by Binance, not by PipSync. For Telegram and Discord signals executed on your account, 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 sizing and min/max lots 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.

PipSync does not close positions from webhooks or alerts: there is no close action, and a direction other than buy or sell is rejected. Exits happen by stop loss, take profit or by you.

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, which protects your account and Binance from runaway or duplicated alerts.

On HTTP 429, your sender should back off and add jitter so retries do not all arrive at once. For high-frequency strategies, batch or debounce signals upstream.