TV-native
Designed around TradingView’s ~3s timeout and limited resubmission — the failure mode bot operators actually hit.
TradingView · bot-first · reliability
HookWatch sits between TradingView and your bot. We ACK inside the ~3 second window, then queue, retry, and DLQ so alerts still land when your bot is slow or down. Built for bots — not generic enterprise webhooks.
One simple ladder. Yearly = pay 10, get 12. Soft-launch · card (Stripe test) or crypto (USDT/USDC invoice) — same product.
| Tier | Monthly | Yearly | Limits | Best for | |
|---|---|---|---|---|---|
| Free | €0 | — | 7-day · 10 alerts total · 1 dest | Smoke-test your bot | Start free |
| Lite | €9 | €90 | ~200/day · 2 dest | Single-strategy bot | Subscribe |
| Starter | €19 | €190 | ~500/day · 5 dest · DLQ | Solo operators | Subscribe |
| Ops Popular | €49 | €490 | ~2,000/day · 15 dest · Replay | Active multi-bot setups | Try sandbox |
| Scale | €79 | €790 | ~5,000/day · 40 dest | Heavier volume | Subscribe |
| Partner | €199 | €1,990 | ~10k/day · 100 dest · API | Bot builders (Door B) | Subscribe |
| White-label | €399 | €3,990 | Fair use · unbranded | Platforms (Door B) | Subscribe |
Free hard-stops after 10 alerts or day 7. Paid caps are soft for soft-launch.
Point TradingView at your HookWatch URL instead of your bot.
We answer TradingView inside the window so the alert isn’t cancelled.
Queue → retry → DLQ + Replay until your bot actually gets it.
Those tools are excellent generic webhook infrastructure. HookWatch is narrower on purpose.
Designed around TradingView’s ~3s timeout and limited resubmission — the failure mode bot operators actually hit.
Two doors: connect one bot yourself, or partner/white-label if you route many end users. No enterprise sales theater.
ACK · queue · retry · DLQ · Replay. We don’t sell signals, execution, or “alpha.” Delivery only.
Official docs beat slogans. HookWatch is built around what TradingView actually does.
The remote server must finish within about three seconds or TradingView cancels the request.
Source: How to configure webhook alerts
Resubmits on HTTP 500–599 except 504, after 5 seconds, up to 3 resends (max 4 sends). A plain timeout is not that path.
Source: Webhook resubmission
If your bot does heavy work inside TradingView’s request, you race the clock. ACK fast, deliver asynchronously.
TV Basic: webhooks need a TradingView plan that includes them. Basic often cannot send real webhooks.
Webhook URL points at HookWatch. We ACK so TV doesn’t cancel.
Alert is queued and forwarded to your bot or hosted inbox.
Temporary outages don’t drop the alert — we keep trying.
Persistent failures land in a pile you can inspect and resend.
Alert webhook → your HookWatch URL. Destination defaults to hosted inbox or your bot URL.
Watch ACK, delivery, and DLQ in the app at api.gethookwatch.com/app.
No. HookWatch only delivers alerts reliably. We don’t place trades or sell signals.
Webhooks require a TradingView plan that includes them. Basic often cannot send real webhooks — upgrade TV or test with a manual POST.
Card checkout is Stripe test/sandbox until founder flips live keys. Crypto (USDT/USDC on TRON, Solana, Ethereum, BSC) is a parallel invoice rail to founder wallets — open unified checkout (card or crypto).
Partner = bot builders routing many users (API). White-label = branded / unbranded portal for platforms. See pricing Door B cards.