NSE doesn't offer a public API, so most data comes from third-party providers (Parse.bot, Apify actors, RapidAPI listings, or a paid vendor). One endpoint covers both data types this dashboard uses — 52-week highs/lows and advances/declines — as long as your Worker/proxy returns a combined JSON response for both. Enter it here and test it. Many providers block direct browser calls (CORS) even with a valid key — if the test fails, that's usually why, and manual entry above will keep working regardless.

Powers the Screener tab (quarterly Sales/Profit/EPS pulled straight from Screener.in for a single company code at a time).

Optionally store your logged data and fetched API results in a file in your own Google Drive instead of (or in addition to) this browser's local storage. This needs a one-time setup:

1. This page must be served over http:// or https:// — Google sign-in does not work when opened directly as a file:// path. Host it (GitHub Pages, Netlify, etc.) or run a local server (e.g. python3 -m http.server) and open it via http://localhost:<port>.
2. In Google Cloud Console, create an OAuth Client ID (type: Web application), enable the Google Drive API, and add this page's exact origin (e.g. https://yourname.github.io or http://localhost:8000) under "Authorized JavaScript origins".
3. Paste that Client ID below and click Connect. A file named nse-dashboard-data.json will be created in your Drive, visible to you, and only readable by this app (Drive's drive.file scope).

Nobody but you and your Google account can see this file — Anthropic and this dashboard's code never see your Drive contents directly; your browser talks to Google's API on its own.

By default, your data lives only in this browser's local storage, tied to this exact file — if you open a different copy of this dashboard (a fresh download, a different folder, browser, or computer) it will look empty, even though yesterday's entries are still sitting safely under the old copy. Connecting Google Drive above solves this: any browser signed into the same Google account can load the same saved file. Either way, exporting a backup after logging each day is good practice — import that spreadsheet into whichever copy you open next. Importing merges with what's already loaded — it won't overwrite a date you've already logged today.

Link this dashboard directly to one .xlsx file on your Mac (e.g. in your Downloads folder). Once linked, every refresh — clicking Refresh up top, or any "Fetch from API" button — rewrites that same file so it always mirrors what's on screen. No more downloading a new copy each day. If a live refresh ever fails (API down, no internet, CORS), the dashboard automatically re-reads that same file so your existing history still shows instead of going blank.

This uses your browser's File System Access API, which only works in Chrome or Edge on Mac — Safari and Firefox don't support it. If you're on Safari, keep using Export/Import backup above instead.

Data is stored locally in your web browser via localStorage, and optionally also in a private file in your own Google Drive if you connect it in the section above — either way it isn't shared with anyone else, and it isn't sent anywhere except the API endpoint you configure above (if any) and Google's own Drive API (if connected). Nothing here is financial advice; it's a tool for tracking numbers you choose to log.