# Webhook to Binance — send crypto signals from any system via JSON Source: https://pipsync.io/en/webhook-to-binance Last updated: 2026-06-08 To send a webhook to Binance Futures, POST a flat JSON payload from any system to your unique PipSync webhook URL: PipSync reads the instrument, direction, entry, sl and tp1 fields and saves a signal for you to review — fully cloud-based and running 24/7. 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; Binance accounts are not auto-traded for now, because they are gateway-connected and the risk of a crypto trade cannot be measured on them — the alert is only recorded as a signal and cannot be placed there from PipSync for now. Telegram and Discord signals still execute on Binance Futures. 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. ## Webhook to Binance Futures at a glance | | | |---|---| | Source | Any system that can HTTPS POST flat JSON (scripts, bots, backtesters, cron, no-code tools) | | Destination | Telegram and Discord signals execute on Binance Futures; a webhook from your own system is saved as a signal for your approval | | Authentication | Your own trade-only API key with withdrawals disabled | | Payload | Flat JSON: instrument, direction (buy/sell), entry, sl and tp1 — all required | | Order flags | Not applied: a webhook signal always waits for your approval | | Infrastructure | Fully cloud-based, runs 24/7, no VPS, EA, bot or terminal required | | Auto-trade | Never for a webhook from your own system; only TradingView's own alerts can auto-trade (opt-in, Advanced plan), and not on Binance accounts for now: crypto risk cannot be measured there | | Price | Webhook integration needs a plan that includes it (the Advanced plan) | ## How do I set up a webhook to Binance Futures? Send JSON from any HTTPS-capable source to PipSync, which saves it as a signal for your approval; a webhook from your own system is never traded automatically. Verify the interpretation under Recent alerts. 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. **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. **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. **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. **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. **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. ## What JSON does a webhook to Binance Futures need? 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 ## How is this different from a TradingView-to-Binance webhook? 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. ## Can a webhook to Binance 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. 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. ## How are leverage and liquidation handled on Binance Futures? 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. ## How do I close positions and get execution feedback? 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. ## What are the rate limits for inbound webhooks? 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. ## FAQ ### What is a webhook to Binance Futures? It is an HTTPS POST that sends a flat JSON instruction to a service. With PipSync you POST instrument, direction, entry, sl and tp1 to a unique URL and it saves a signal for your approval; a webhook from your own system is never traded automatically. ### Can any system send a webhook to Binance, or only TradingView? Any system that can make an HTTPS POST can send the webhook. PipSync is source-agnostic and reads only the JSON body, so scripts, backtesters, cron jobs, no-code tools and custom bots all work. TradingView is just one possible source, and it additionally requires a paid TradingView plan. 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. ### Do I need to give PipSync withdrawal access to my Binance account? No. For Telegram and Discord signals executed on Binance Futures, you create a trade-only API key with withdrawals disabled, so PipSync can place futures orders but can never move funds out of your account. ### Does the webhook support both USD-M and COIN-M contracts? For Telegram and Discord signals, yes: PipSync supports both USD-M and COIN-M Binance Futures contracts. A webhook from your own system is saved as a signal for your approval. ### How do I close a position with a webhook? You cannot, from a webhook: there is no close action, and a direction other than buy or sell is rejected. PipSync does not close positions from alerts or webhooks: exits happen by stop loss, take profit or by you. ### Can a webhook from my own system trade on Binance 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 Binance Futures? Not for now. Auto-trade is opt-in and needs the Advanced plan, but Binance accounts are gateway-connected, so 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. ### Is PipSync a signal provider or giving trading advice? No. PipSync is execution infrastructure that turns the alerts you or your system send into signals; it does not provide signals, strategies or investment advice. Trading leveraged products like Binance Futures involves substantial risk of loss, and you remain responsible for your own decisions. ### Do I need a VPS or a bot running on my computer? No. PipSync is fully cloud-based and runs 24/7, so your webhook keeps working even when your computer is off. There is no VPS, EA, cBot, plugin or terminal to keep open. ## Related - [Webhook to Bybit — send crypto signals from your own code](https://pipsync.io/en/webhook-to-bybit) - [TradingView to Binance — alerts become signals you review](https://pipsync.io/en/tradingview-to-binance) - [Telegram crypto signals to Binance — executed 24/7](https://pipsync.io/en/telegram-to-binance) - [Discord crypto signals to Binance — executed 24/7](https://pipsync.io/en/discord-to-binance) - [Crypto signal copier — automate signals on Binance Futures and Bybit](https://pipsync.io/en/crypto-signal-copier) - [Server-side risk management — trading rules enforced before your broker](https://pipsync.io/en/server-side-risk-management) --- 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.