Tradingview
🌌 Astrosinyal · AMI Docs
CHAPTER4 /11
Connect TradingView
One-time setup
- Fetch the bridge script with your key so your own webhook secret is embedded:
Anonymous requests in SaaS mode receive a placeholder instead of a secret — in that case paste yourcurl -H "X-API-Key: ami_YOUR_KEY" https://ami.astrosinyal.com/api/pine -o AMI_Alert.pinewhsec_...from the portal into the script’s AMI webhook secret field manually. - TradingView → open your chart → Pine Editor → paste the file → Add to chart.
- Create Alert (clock icon): Condition →
Any alert() function call · Webhook URL →
https://ami.astrosinyal.com/webhook· Message → leave empty (the script sends its own JSON).
Triggers (script settings)
- ☑ Trend change — on by default
- ☑ EMA20 × EMA50 cross — on by default
- ☐ Every bar close — off (heavy: one analysis per bar)
- Notify — request a Telegram report with each alert (default on)
What AMI does on each alert
It receives the payload (symbol, price, RSI, MACD, trend, volume, EMA20/50, ATR), runs the full pipeline, stores the signal in your history, replies with the analysis — and delivers a Telegram report if notify was on.
{
"secret": "whsec_...",
"symbol": "BBCA.JK",
"price": "{{close}}",
"rsi": "{{plot_0}}",
"macd": "bullish",
"trend": "uptrend",
"volume": "{{volume}}",
"notify": true
}
Symbol mapping: Indonesian tickers map to Yahoo
format automatically (BBCA → BBCA.JK, based on chart currency); crypto:
BTCUSDT; index: ^JKSE; gold: XAUUSD. Set the
script’s AMI symbol field to override.Alert not arriving?
1) secret mismatch → rotate the webhook secret in the portal and re-fetch the
script ·2) quota hit → HTTP429 (Free:200 webhooks/day) ·
3) TradingView fires alerts in real time only — it does not replay old bars ·
4) see the FAQ.
AMI provides calibrated probability, never certainty (model AUC ≈ 0.53) ·
Not financial advice · Vedic terms (tithi, nakshatra, Rasi, retrograde, Muhurta, Dasha, Pada)
stay untranslated in every language.