Settings · Connectors
Credentials are encrypted with AES-256-GCM. Master key lives in .env only.
First-Run Wizard Progress
Required for live Pine Screener scraping. Your sessionid cookie lets the headless browser act as you on TradingView. No password, no SSO — just the cookie.
How to get your sessionid cookie
- Log into tradingview.com in your normal browser
- Open DevTools (F12) → Application tab → Cookies →
https://www.tradingview.com - Find the row where Name =
sessionid - Double-click the Value column → Ctrl+C
- Paste below and click Save
Kite Connect requires a daily access-token refresh via Zerodha login (SEBI 2FA requirement). Your api_key and api_secret are stored encrypted; the access_token expires at 06:00 IST each morning.
Step 1 · API credentials
Where to get them
- Go to developers.kite.trade/apps and create (or open) an app on the Connect plan
- Set Redirect URL to
http://localhost:8080/api/v1/identity/kite/callbackfor the auto-flow, or any URL likehttp://localhostfor the manual paste flow - Copy the API key and API secret from the app detail page. The secret is shown only once — save it before closing the page.
- Paste both below and click Save
Step 2 · Daily access-token refresh
Run this every morning before market open. If your Kite app's Redirect URL is set to our callback, the flow completes automatically (browser tab will show "Kite Connected" then close) — do not also paste the request_token from the URL bar, because Kite tokens are single-use and the auto-flow already consumed it. Use the paste field only as a fallback when your Kite app's Redirect URL is something other than our callback.
Once configured, intraday signals, earnings alerts, and target-hit notifications can be routed to your Telegram. Bot token and chat ID are stored encrypted in the vault.
Step 1 · Create a bot + get your chat ID
How (one minute)
- Open Telegram, message @BotFather, run
/newbot - Pick a display name (anything) and a username ending in
bot(e.g.tradesmith_user_bot) - Copy the HTTP API token BotFather sends back — looks like
123456789:ABCdef-GhIJklMnOp... - Open a chat with your new bot and run
/start(the bot must hear from you at least once before it can message you) - Get your chat ID: message @userinfobot — it replies with your numeric ID, e.g.
123456789 - Paste both values below and click Save
Step 2 · Verify by sending a test message
Calls Telegram's getMe to verify the token, then sends a "AJTradeMaster is connected" message to your chat. If the bot is configured correctly, you'll see it in your Telegram app within seconds.
Route your Table-3 / Table-4 breakout alerts to WhatsApp via Meta's Cloud API (free for personal use). Access token, phone-number ID and recipient are stored encrypted in the vault.
Step 1 · Meta WhatsApp Cloud API credentials
How (a few minutes)
- Go to developers.facebook.com/apps → Create app → add the WhatsApp product
- On the WhatsApp → API Setup page, copy the temporary access token and the Phone number ID (the test number works for personal use)
- Under "To", add + verify your own phone number (test numbers allow up to 5 recipients)
- Paste your number as the recipient in international format (digits only, e.g.
919812345678) - Save → Test. Note: the temporary token expires every 24h — generate a permanent System-User token for always-on alerts.
Step 2 · Table-3 breakout routing
Platform kill switch for live NC-breakout alerts. The actual per-table / per-symbol opt-ins live on each agent page (Table 3). When a subscribed symbol crosses NC High / NC Low, the alert is delivered to your preferred channel.
Step 3 · Table-4 re-scan routing
Platform kill switch for Table-4 re-scan alerts (a symbol flagged by the 7 daily-confirmation 2H scans, or re-triggering across the fresh NC High). Per-symbol opt-ins live on each agent page (Table 4).
Powers every AI feature — the screener's "Claude predictive analysis", fundamentals summaries, market narration, earnings digests, and anomaly flags. Stored encrypted in the vault and fetched by ai-service over the internal network. Without it, those features show clearly-badged fixtures.
Step 1 · Get a key + save it
Where to get one
- Open console.anthropic.com → API Keys
- Create a key — it looks like
sk-ant-api03-… - Paste it below and click Save (it's shown only once on Anthropic's side, so copy it carefully)
Step 2 · Verify the key works
ai-service fetches the saved key from the vault and lists available models (no token cost) to confirm it authenticates. On success the key is marked verified and the AI features go live.
The breakout panel's put-selling section (a safer out-of-the-money put to sell plus the 3 highest open-interest strikes, each with POP and profit) is computed nativelyfrom your Kite-linked option chain — no separate Sensibull login is required. Lot sizes come from Kite's instrument cache and the spot from your live Kite quote, so everything refreshes the moment you refresh your Kite token in Settings → Kite (your existing daily flow).
Why not Sensibull?
Sensibull has no public API to integrate with — it's a platform brokers embed, not one you can call programmatically. Reverse-engineering its authenticated web surface would be fragile and against its terms. Every number you'd want from it (OTM put to sell, highest-OI strikes, POP, profit) is computed here directly from your Kite chain with the platform's own Black-Scholes engine, with no extra login to maintain.
Open Swagger UI, switch to Identity API, then POST to /api/v1/identity/vault/connectors/{name}.