Get answers to common questions about setting up and using Cwebhook
Looking for deeper walkthroughs? Browse all guides →
Automation & setup
Cwebhook automates cTrader by receiving webhook alerts and placing orders via the cTrader Open API. You do not install a cBot on a VPS. Open an account, authorise cTrader, copy your webhook key, then point TradingView at https://cwebhook.com/alerts.
Cwebhook is a cloud webhook bridge for cTrader. It turns alerts from TradingView, TrendSpider, or any HTTP POST source into real broker orders: market and limit entries, stop-loss and take-profit, position closes, partial exits, and stop modifications — all driven by JSON webhooks.
All customers use the same endpoint: https://cwebhook.com/alerts. Your account is identified by the key field inside the JSON body (unique per account). Find your key in the dashboard under Alert Code. Never share your key publicly.
cTrader does not expose a native TradingView webhook. Cwebhook acts as the middleware: TradingView POSTs JSON to Cwebhook; Cwebhook uses your authorised OAuth tokens to trade on cTrader. No cBot, no MetaTrader bridge, no self-hosted server required.
cTrader OAuth access tokens expire. When refresh fails or you change broker permissions, the dashboard shows Reauthorise Account. Use Reauthorise demo or Reauthorise live and select the same trading account as your Cwebhook login — tick exactly one account on the consent screen.
No — not to a different broker account type. Each Cwebhook login stays tied to one cTrader account. Many prop firm challenges (and some funded accounts) use demo-type cTrader accounts, so a paid demo Cwebhook subscription is correct for those — you do not need to “upgrade” to live unless your broker login is actually live.
If you do need a genuine live broker account, open a separate live Cwebhook account. If you already paid on demo, support can transfer the subscription.
TradingView & integrations
In TradingView: create alert → enable Webhook URL → URL https://cwebhook.com/alerts → paste JSON in the message box. Use separate alerts for buy (tradeSide 1) and sell (2), and set symbolId plus a strategy label.
Yes. Any platform that can send an HTTP POST with a JSON body works with Cwebhook — TrendSpider, custom scripts, other charting tools, or your own backend. The payload format is the same as documented at cwebhook.com/docs.
Yes. Each alert must set tradeSide to 1 (buy) or 2 (sell). Create one TradingView alert for long entries and another for short entries, each with the correct JSON.
Cwebhook features
Version 2 is a rebuilt platform with faster execution, richer order types, and better tooling:
/stats via @CwebhookBot.Read what’s new in V2.
Set label when you open a trade (e.g. "label": "tv-strategy-01"). Use the same label on later webhooks with closePosition or modifyPosition so only those positions are affected. Essential for multi-strategy accounts.
Add limitOrder: true and limitPrice with your entry price. Use the dashboard Alert generators → Entry execution → Limit to build the JSON automatically.
Send a webhook with modifyPosition: true, the matching label, and new relativeStopLoss / relativeTakeProfit (pips) or absolute prices.
On a close webhook, set closePosition: true and closePercent between 1 and 100 (e.g. 50 closes half of each matched position). Omit closePercent to close 100%. Combine with label to target one strategy only.
In the dashboard Notifications tab, generate a link and open @CwebhookBot. Opt in to trade fills, closes with P&L, errors, and reauth warnings. Send /stats for live balance, equity, and webhook P&L summary.
Built-in dashboard tools under Alert Code that build open, close, and modify JSON for you — symbol picker, volume, SL/TP, labels, and limit price included. Copy the result straight into TradingView with your key already filled in.
Yes. Under Trading restrictions in the dashboard you can set a daily time window, timezone, and maximum trades per rolling period. Webhooks received outside the window or over the limit are logged as rejected (HTTP 429) without placing orders.
Webhook JSON & order parameters
key is always required. Open orders need symbolId, tradeSide, and volume fields; closes use closePosition; modifies use modifyPosition plus a label.
relativeStopLoss and relativeTakeProfit are in pips, not points or price. Example: 5 pip SL and 10 pip TP:
{
"relativeStopLoss": 5,
"relativeTakeProfit": 10
}Set relativeStopLoss (initial distance in pips) and trailingStopLoss: true on the opening webhook.
{
"relativeStopLoss": 5,
"trailingStopLoss": true
}When closeOpenPosition is true on an entry webhook, Cwebhook closes the current open position on that symbol/side (if any) before opening the new one. Best when you only run one position at a time per symbol.
Use closePosition: true on exit-only webhooks (no new entry). Filter by symbolId, tradeSide, and/or label. Ideal for TradingView strategy exit alerts.
{
"key": "YOUR_CWEBHOOK_KEY",
"closePosition": true,
"label": "tv-strategy-01"
}volumeType 1 — fixed lot size via volume (e.g. 0.01).
volumeType 2 — percentage of account balance via volumePercent (e.g. 1 = 1% of balance allocated using margin calculation). Common on demo accounts for risk-based sizing.
Typical limits: demo 30 requests/minute and 100/day; live 120/minute. Valid JSON can still return HTTP 429 if you exceed limits or hit dashboard trading restrictions. See errors & limits.
Accounts, pricing & hosting
Yes. Prop firm challenge and funded accounts on cTrader are supported. Many challenges — and with some firms even funded accounts — run as demo-type accounts, so use a demo Cwebhook login and subscribe if you need more than the free 30-day trial. Only open a live Cwebhook account when the firm gives you a genuine live broker login.
Free demo — $0 for 30 days on one demo Cwebhook login. Monthly — £9.99/month for one Cwebhook login (live or demo, not both) with unlimited signals. Annual — £99.99/year (save ~17%). Payments via FastSpring. View pricing.
Cwebhook runs on Hetzner cloud infrastructure in their Oregon data centre — the same region TradingView uses for its web application. That keeps webhook round-trip times low when alerts fire from TradingView. The endpoint is https://cwebhook.com/alerts.
Troubleshooting
Check your dashboard activity log for the rejection reason — common causes include a bad key, expired OAuth (reauthorise), trading restrictions / rate limits, expired demo, or malformed JSON.
After connecting cTrader, open the dashboard symbol list (or Alert generators market dropdown). Each instrument shows its numeric symbolId for your broker. IDs differ between brokers — always use the value from your account.
Email support via cwebhook.com/support. Check status page for incidents. For API field reference use full documentation.
Can't find the answer you're looking for? Our support team is here to help you get the most out of Cwebhook.