SETTINGS · INTEGRATIONS · SERVICES

Settings.

LIVE

Setup guide · connect QuantSentinel to your brokers

Read this once before pasting API keys in the Integrations card below. The order matters: allowlist the static IP first, then create the API credentials, then paste them into QuantSentinel.

Step 0 · the static IP
do this first
34.131.22.192QuantSentinel's outbound IP · GCP · asia-south2

This is the IP every outbound call from QuantSentinel originates from. Add it to the API-allowlist in Groww, Upstox, and any other API that gates by IP. If you skip this step the broker will silently reject every API call with a 403 — confusing if you've never seen it before.

Groww is the broker that QuantSentinel uses to place orders. (Note: order execution is currently in dry-run mode — see the safety note at the bottom of this guide. Setting up Groww keys is still needed so the order pipeline runs end-to-end.)

Keys you'll paste into Integrations below
  • API keyGROWW_API_KEY· public identifier
  • API secretGROWW_API_SECRET· private key
  • TOTP secretGROWW_TOTP_SECRET· seed used to auto-refresh sessions
  • TOTP tokenGROWW_TOTP_TOKEN· current 6-digit code (one-time)
How to get them
  1. Sign in at https://groww.in with the trading account you want QuantSentinel to use.
  2. Open the Profile → Trading APIs section (or go to groww.in/user/profile/trading-apis).
  3. Create a new API app. Groww will issue an API key and API secret — save both. The secret is shown only once.
  4. In the same API-app settings, find IP allowlist and add 34.131.22.192.
  5. Enable TOTP-based session refresh. Groww will show a QR or a base-32 secret — that secret string is GROWW_TOTP_SECRET. Save it.
  6. Generate the current 6-digit code from your authenticator app — that's GROWW_TOTP_TOKEN. It refreshes every 30 seconds; paste a fresh one when you save below.
Once GROWW_TOTP_SECRET is saved, the system regenerates fresh TOTPs automatically and you never need to paste a TOTP token again. Adding it the first time only is enough.

Upstox is the data feed — spot, VIX, option chains, margin calculator, FII/DII flows. It is required even if you do not trade through Upstox: most of the Intelligence and Prep pages read from this feed.

Keys you'll paste into Integrations below
  • Access tokenUPSTOX_ACCESS_TOKEN· expires daily at ~3:30 AM IST
How to get it
  1. Sign in at account.upstox.com/developer/apps and create a new app (any redirect URL is fine — Upstox needs one but QuantSentinel does not use it).
  2. In the app settings, add 34.131.22.192 to the API allowlist.
  3. Run Upstox's OAuth flow to exchange your client ID + secret for an access token. The token is a long opaque string starting with eyJ....
  4. Paste it into the Upstox row in the Integrations card below and click Save.
Daily refresh. Upstox expires every access token at ~3:30 AM IST. You need to repeat the OAuth step each morning and paste the new token here. (We are not currently configured to refresh tokens server-side.)

Gemini is the LLM behind the copilot. It generates the Verdict narrative, Prep synthesis, and answers in the Help drawer. Without this key, copilot panels show placeholder text but the quantitative engines all still work.

Keys you'll paste into Integrations below
  • API keyGEMINI_API_KEY
How to get it
  1. Open aistudio.google.com/apikey in a logged-in Google account.
  2. Click Create API key and copy the value (starts with AIza...).
  3. Paste it into the Gemini row in Integrations below.
Free tier covers QuantSentinel's typical usage (~200 short copilot calls per day). No IP allowlist required — Google does not gate the AI Studio API by IP.
Security & safety — read me
Keys are encrypted. Saved values go into a Redis-backed secrets store under the secrets: namespace. They are never displayed back in the UI, never logged, and never sent to anywhere other than the integration that owns them.
Your site password protects everything. Anyone who logs in with the site's basic-auth credentials can change the broker keys here. Use a strong unique password and do not share it.
No live order execution. The system runs in dry-run mode — orders are computed, gated, logged, but never sent to Groww. Going to live is a deliberate operator action, not a UI toggle. If you ever see execution mode · live on the Ops page without having authorised it, treat that as a real incident and switch back to dry-run immediately.
Degrades gracefully. Missing optional keys (NewsAPI, Telegram) reduce features but do not break the system. A missing Gemini key disables copilot narration but the quantitative engines continue to work.

Integrations · brokers, data feeds & ML

checking integrations…
Keys are written to the encrypted secrets store and read by the services at runtime — never shown back here. Groww applies on a broker reload (automatic); Upstox, Gemini, NewsAPI and Telegram apply on the next call.

Engines & services · polled live

checking…
checking services…