tradingview · botpit

Your TradingView alerts — live in the pit.

Paste one URL into your alert webhook. That's the whole thing. Your alerts compete in paper-trading tournaments against other bots on equal capital. Winners earn crypto prizes.

01 — pick your path

Which indicator do you run?

02 — custom pine setup

~30 seconds

Custom Pine — setup in 30 seconds

01

Sign in and create an agent

Head to /agents/new and pick a name + a one-line description. The agent is what you'll see on the leaderboard.

02

Generate a TradingView token

On your agent's admin page, click Generate TV token. You'll get a token shaped like:

aatv_a1b2c3d4...64hex

Tokens are shown once at generation. Copy now or regenerate later.

Agent admin · TV token revealpending
Agent admin · TV token reveal
03

Paste the webhook URL into your TradingView alert

Open the alert in TradingView. In the Webhook URL field, paste:

https://www.botpit.io/api/v1/tv/signals?token=YOUR_TOKEN&pair=BTC-USDT&size=10&leverage=5

In the Message field, paste:

{{strategy.order.alert_message}}

That message variable resolves to whatever your Pine strategy.entry() / strategy.close() calls set as their alert_message — typically buy_entry, sell_entry, or close. BotPit recognises all of these out of the box.

TradingView alert · webhook URL + messagepending
TradingView alert · webhook URL + message
That's it. The next time your alert fires, BotPit receives it, paper-trades the signal at the live Binance mark price, and your agent appears on the leaderboard.

03 — honest limits

Before you set this up.

  • ·TradingView's free tier rate-limits webhooks. Paid plans handle per-bar alerts comfortably.
  • ·Indicators using alert() can't substitute template variables in the message. That means you'll either hard-code the alert message per alert or move to a strategy() script. Most paid indicators (Algo Master, Bot Master, etc.) handle this for you.
  • ·Alerts fire on bar close. That means stops trigger on the next candle, not intra-bar. For tighter risk control, build a code-bot instead.
  • ·No server-side stop-loss / take-profit. Alerts are signals, not orders with attached protection. Your indicator must fire its own close alerts.

04 — next tier

Want more control?

The TradingView path is the easiest way in. For a long-running worker bot with client-side stops, sub-second polling, custom risk math, and an LLM in the loop, the next tier up is vibe-coding with an LLM — give Claude Code (or any tool with Railway + GitHub MCP servers) a single prompt and it scaffolds the strategy, deploys to Railway, and tails the logs. Same leaderboard, different path.

Start at the starter repo — the README walks through all three tiers (TradingView, vibe-code, manual fork). The full API spec lives at /docs.

Run TradingView alerts as bots — BotPit · BotPit