Webhook to Bybit — send crypto signals from your own code

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 Python script, a backtesting bot, a serverless function or a no-code automation — can send signals through the same JSON contract. PipSync runs the layer in the cloud with signed outbound webhooks for feedback, so you keep your own strategy logic.

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 Bybit API key

   For Telegram and Discord signals, generate a trade-only Bybit API key (withdrawals disabled) and paste it into PipSync under Trading Accounts → Add account. Bybit 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 issues a unique URL, shown only once, whose secret token is the credential — keep it secret: with auto-trade on, anyone who has the URL can trigger trades. Regenerate it if you suspect a leak.

4. 4

   Configure server-side risk rules

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

5. 5

   POST your first JSON payload

   From your script or automation, send a flat JSON body with instrument, direction, entry, sl and tp1 to the webhook URL, using real prices above 0. Other fields such as lots are ignored.

6. 6

   Verify with Recent alerts, then start small

   Check Recent alerts under Settings → Advanced → TradingView Alerts to confirm PipSync interprets your payloads correctly, and start with small size before scaling up.

Typical setup time: about 11 minutes.

The payload is a single flat JSON object — no nesting — that becomes a signal. It has five required fields: instrument, which should be Bybit's contract name, direction ("buy" or "sell"), entry, sl and tp1.

Prices are absolute values above 0 — a 0 is rejected, not read as market or omit. Other fields such as lots and comment are ignored.

• instrument: the Bybit contract name (e.g. a USDT perpetual; 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

A trade-only API key lets PipSync use your Unified Trading Account without ever being able to move funds off the exchange. You create the key in Bybit with withdrawals disabled, so even if the credential were exposed it could not initiate a transfer.

Your own code never has to embed Bybit keys either — you POST to a PipSync webhook URL whose secret token is the only credential your scripts hold. PipSync stores the exchange key server-side, separating your strategy code from your account access.

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. Bybit 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 Bybit.

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

Not through the webhook: 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.

This matters on the Unified Trading Account, where unified margin and perpetuals make exposure easy to flip: keep sl and tp1 realistic in every payload, because they are what protects the position.

PipSync gives you three feedback channels so your system always knows what happened. Signed outbound webhooks fire on trade.opened, trade.closed, tp_hit and sl_hit events, 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 via OpenAPI 3.1) lets you poll state on demand, and the dashboard shows every parsed signal and order on all plans.

Inbound webhooks are rate-limited. If you receive an HTTP 429, back off with jitter and retry, and your bursts will settle cleanly. The read API is part of the Enterprise plan.

Yes. PipSync's webhook is fully cloud-based and runs 24/7, which matches crypto markets that never close. There is no VPS, no plugin and no terminal to keep open — once your webhook URL is generated, it keeps working whether your laptop is on or off.

Because the route is source-agnostic, the same setup works for a cron-driven script, a hosted bot or an event-driven function. Your job is to POST valid JSON; PipSync handles authentication and saves the signal.