గుండెల్లో భారత్, పెదవులపై జై హింద్!

Indian Stock Market Data API

Stock market EOD prices, financials, shareholding, screener & more — the data infrastructure behind India's next fintech products.

BharatStock is a REST API for Indian stock market data — EOD stock prices, quarterly & annual financials, corporate actions, shareholding patterns, a stock screener, mutual-fund holdings, and index data. Clean, normalized, and developer-ready, delivered through a fast, well-documented API.

0
Indian equities covered
0
REST endpoints
0
Indian market coverage
GET /v1/stocks/RELIANCE
curl https://bharatstockapi.com/v1/stocks/RELIANCE -H "X-API-Key: •••"
{
  "symbol": "RELIANCE",
  "company_name": "Reliance Industries Limited",
  "sector": "Oil Gas & Consumable Fuels",
  "exchange": "NSE",
  "latest_price": {
    "trade_date": "2026-08-12",
    "close": 1421.35,
    "prev_close": 1408.90,
    "volume": 8452110,
    "delivery_pct": 42.6
  }
}
RELIANCE+0.88%
COVERAGE / EOD PRICES & OHLCV / FINANCIALS / CORPORATE ACTIONS / SHAREHOLDING PATTERNS
FII / DII Cash Market Activity
Live institutional-flow figures are temporarily undergoing corporate data-licensing maintenance. The full FII/DII activity view will return following our upcoming authorized exchange data-feed deployment.
₹39,777
Crores in MF
302 schemes · 31 AMCs
New

Mutual Fund Holdings

Sample: Reliance Industries

See exactly which mutual fund schemes hold any stock, how much they've invested, and how positions changed month-over-month — plus daily scheme NAVs and trailing returns. Compiled straight from the fund houses' own official monthly portfolio disclosures.

Only in India

The only self-serve developer API in India for mutual fund scheme holdings — 44+ AMCs, first-party from each fund house's monthly disclosures.

Plus daily NAV for every scheme across every AMC. Others stop at NAV; we give you both the NAV and what each scheme actually holds.

Direct from 44+ AMCs' statutory disclosures 20 years of daily NAVs from AMFI & trailing returns
Nippon India MF
₹15,359 Cr
38.6%
Aditya Birla SL MF
₹5,801 Cr
14.6%
Axis MF
₹4,373 Cr
11.0%
Bandhan MF
₹2,924 Cr
7.3%
Others (26 more)
₹11,320 Cr
28.5%
Daily scheme NAV & returns · sourced from AMFI
Parag Parikh Flexi Cap Fund
Direct · Growth
₹92.34
▲ +0.8% today
+21.4%
1Y
+18.2%
3Y
+22.6%
5Y
Illustrative figures — 20 years of daily NAVs (from AMFI, since 2006) & computed trailing returns via the API.
New · Smart Money

Follow the money nobody else exposes programmatically.

Bulk deals, block deals, and insider & promoter (SEBI PIT) disclosures — the trades that move stocks, now one API call away. Per-ticker and market-wide.

Bulk Deals
>0.5% of equity in a day
GET /v1/deals/bulk
ALPHA FUND BUY
2,00,000 sh · ₹105.25
Block Deals
Large-ticket window
GET /v1/deals/block
BANDHAN MF BUY
5,18,919 sh · ₹925.00
Insider & Promoter
SEBI PIT disclosures
GET /v1/insider-trades
Bajaj Holdings PROMOTER
Acq · 20.9L sh · 38.28% → 38.41%
Platform

Everything a market-data pipeline needs, already built.

One versioned API instead of stitching together and maintaining multiple market-data sources yourself.

EOD prices

Daily open/high/low/close/volume for every listed Indian equity, normalized and delivery-adjusted.

Split & bonus-adjusted prices

An adjusted_close field with a transparent multiplier, so charts don't show a fake crash on a bonus ex-date.

Deep financials

Quarterly and annual P&L, balance sheet, and cash flow — normalized from official company disclosures, including bank/NBFC formats.

Corporate actions

Dividends, bonus issues, splits, and rights issues, with parsed ratios and per-share amounts.

Shareholding patterns

Quarterly promoter / public / FII / DII breakdowns from official shareholding-pattern disclosures.

Valuation ratios

P/E, P/B, ROE, ROCE, dividend yield, and 52-week high/low — computed on read, always current.

Technical indicators

SMA, EMA, RSI, and MACD, computed server-side so you don't have to ship a charting math library.

Movers & price shockers

Top gainers, losers, and most-active lists, plus a threshold-based screen for outsized daily moves.

Stock screener

Filter 5,000+ stocks by 72 pre-computed metrics — P/E, ROE, EBITDA margin, EV/EBITDA, PEG ratio, debt/equity, returns (1w to 5y), FII/DII/MF holdings, volatility, moving averages, and more — with sub-second response times.

Index data

NIFTY 50, sectoral, and broad-market indices — historical daily EOD levels.

FII/DII daily flows

Daily aggregate FII and DII cash market activity — buy, sell, and net values in ₹ Crores. Track institutional money flow and market sentiment.

Mutual fund holdings & NAVs

See which MF schemes hold any stock, their position size, and month-over-month quantity changes — plus 20 years of daily scheme NAVs (since 2006) and trailing returns. Holdings compiled directly from the AMCs' official statutory disclosures; NAVs sourced daily from AMFI.

Bulk deals

Bulk deals — single-day trades exceeding 0.5% of a company's equity, with client name, buy/sell, quantity, and weighted-average price. Per-ticker and market-wide.

Block deals

Block deals — large trades executed in the exchange's dedicated block window, tracked daily. The institutional footprint quant traders watch.

Insider & promoter trades

Insider & promoter trades from SEBI PIT disclosures: who acquired or disposed, quantity, value, before/after shareholding, and mode. Promoter buying, flagged.

Peer comparison

Compare valuation ratios (PE, PB, ROE, ROCE) across every stock in a sector in one call — sorted, with nulls at the bottom.

Batch quotes

Get the latest price for up to 50 tickers in one request — one round trip instead of fifty, built for watchlists and dashboards.

Redis-cached responses

Every endpoint is backed by Redis caching with automatic invalidation on new data. Sub-50ms p95 latency on repeated queries.

10-year price history

Daily OHLCV data going back 10 years for 2,900+ Indian stocks — split/bonus-adjusted and consistent across the archive.

MCP server for AI agents

Query BharatStock as native tools inside Claude, Cursor, and other AI assistants via our official Model Context Protocol server (bharatstock-mcp) — no code required. A Developer/Pro feature. Setup →

Public data-trust status

A live status page proving every pipeline's freshness and internal-consistency checks are passing — most market-data APIs never publish this.

OpenAPI & Postman

An interactive Swagger explorer at /docs and a ready-to-import Postman collection — so you can try every endpoint before writing a line of code.

In-dashboard API Playground

Run any endpoint live from your dashboard — fields come pre-filled with working samples, hit Send and see the real JSON. It uses your own key automatically (no pasting), and copies the exact request as curl, Python, or JS. The fastest path from signup to your first successful call.

5,000+
Stocks tracked daily
<50ms
p95 response time
11+ yrs
of price history
72
screener metrics
Developers

Designed to feel obvious from the first request.

No OAuth dance, no session tokens, no surprise pagination. One key, one header, plain JSON.

  • Single X-API-Key header on every request — no OAuth flow to implement.
  • Consistent { data, pagination } envelope on every list endpoint.
  • Predictable 429s that tell you your plan's limit and when it resets.
  • Versioned under /v1 — fields won't shift under you between releases.
  • Official typed clients — pip install bharatstock or npm install bharatstock.
  • Official MCP server — use BharatStock as tools in Claude, Cursor & other AI assistants (bharatstock-mcp). A Developer/Pro feature.
curl https://bharatstockapi.com/v1/stocks/RELIANCE \ -H "X-API-Key: YOUR_KEY"
pip install bharatstock from bharatstock import BharatStock client = BharatStock(api_key="YOUR_KEY") stock = client.stocks.get("RELIANCE") print(stock.company_name, stock.metrics.pe_ratio)

Published on PyPI →

npm install bharatstock import { BharatStock } from "bharatstock"; const client = new BharatStock({ apiKey: "YOUR_KEY" }); const stock = await client.stocks.get("RELIANCE"); console.log(stock.companyName, stock.metrics?.peRatio);

Published on npm →

import requests resp = requests.get( "https://bharatstockapi.com/v1/stocks/RELIANCE", headers={"X-API-Key": "YOUR_KEY"}, ) print(resp.json())
const res = await fetch( "https://bharatstockapi.com/v1/stocks/RELIANCE", { headers: { "X-API-Key": "YOUR_KEY" } } ); console.log(await res.json());
// Add to your AI host's MCP config (Claude, Cursor, ...) { "mcpServers": { "bharatstock": { "command": "npx", "args": ["-y", "bharatstock-mcp"], "env": { "BHARATSTOCK_API_KEY": "YOUR_KEY" } } } } // or a hosted URL: https://bharatstockapi.com/v1/mcp // with header Authorization: Bearer YOUR_KEY

Developer/Pro feature. Published on npm →

Authentication

Send your key as X-API-Key. No login endpoint, no expiring tokens.

Rate limits

Enforced per calendar day (UTC) per key. Exceeding it returns a 429.

Versioning

Every endpoint lives under /v1, kept stable for existing integrations.

Response format

Plain JSON. List endpoints share one pagination shape across the whole API.

MCP server

Use the API as tools in AI assistants via bharatstock-mcp or the hosted /v1/mcp endpoint. Developer/Pro. Learn more →

Trusted by builders

Products already run on BharatStock.

Live fintech products use our API in production for prices, financials, and market data.

“BharatStock gives us clean, reliable Indian market data behind one simple key. It replaced a brittle in-house data stack and lets us focus on our product instead of babysitting data pipelines.”
I Investory investory.win — investing insights, powered by BharatStock API
Security

Security controls you can check.

Automated scanning every day, hashed credentials and off-host backups. No audit badge, just a list of what we run.

Code scanning every day

Semgrep, Bandit, Gitleaks, pip-audit, Trivy and OSV-Scanner run every day across our code, git history, dependencies and container image, and Dependabot proposes dependency updates every month. A finding fails the scan.

Hashed API keys

Only a SHA-256 hash of each key is stored. The full key is shown once, and you can rotate it from the dashboard at any time.

bcrypt passwords and safe sessions

Passwords are salted bcrypt hashes. The session cookie is signed, HttpOnly, SameSite=Lax and Secure in production.

HTTPS and security headers

HSTS for one year including subdomains, plus nosniff, X-Frame-Options DENY and a strict referrer policy on every response.

Off-host backups

The database is backed up twice a day to separate object storage, so a host problem cannot take the backups with it.

Responsible disclosure

Found something? Email [email protected]. Our contact is also published in /.well-known/security.txt (RFC 9116).

See the full security details →

Pricing

One API. No feature paywalls.

Every plan — including Free — gets the full API: prices, financials, shareholding, corporate actions, indices, bulk/block deals, insider trades, FII/DII activity, mutual-fund holdings, and the screener. Plans differ only in daily request limits and history depth.

Free
₹0/month
60 requests/day

  • Full API access, every endpoint
  • 60 requests/day
  • 1 year of history (prices, financials & MF data)
  • Community support
Get a free API key
Starter
₹500/month
1,000 requests/day

  • Full API access, every endpoint
  • 1,000 requests/day
  • Full history — 11+ yrs prices, 20 yrs MF NAV
  • Email support
Upgrade to Starter
Growth
₹700/month
5,000 requests/day

  • Full API access, every endpoint
  • 5,000 requests/day
  • Full history — 11+ yrs prices, 20 yrs MF NAV
  • Email support
Upgrade to Growth
Pro
₹5,000/month
40,000 requests/day

  • Full API access, every endpoint
  • 40,000 requests/day
  • Full history — 11+ yrs prices, 20 yrs MF NAV
  • MCP server for AI agents
  • Model evaluation & backtesting included
  • Priority email support
Upgrade to Pro

Prices shown are exclusive of tax. Any applicable taxes (such as GST for India) are added at checkout, so the total you pay may be higher than the plan price above.

Paid plans are sold and billed by our authorised resellers acting as Merchant of Record, both accepting international card and PayPal payments: Paddle (cards & PayPal worldwide, Apple Pay & Google Pay on supported devices, plus UPI in India) and Lemon Squeezy (cards & PayPal). They handle billing, receipts, tax, refunds, and subscription management for your purchase.

Your price and request limit are locked in. If we later change a plan's advertised price, your recurring charge stays the price you signed up at — the new price applies only to new sign-ups. Likewise, your daily request limit is grandfathered: changing a plan's limit only affects keys created (or plan-changed) after the change, so a new limit never retroactively reduces an active subscriber's quota. The only time your price or limit changes is when you change plans.

FAQ

Questions, answered.

Yes. A free API key takes under a minute and needs no card. There's also an interactive playground on the landing page to see a live response before you commit.

Create an API key in your dashboard, then send it in an X-API-Key header to any data endpoint — for example GET /v1/stocks/RELIANCE. The API reference has copy-paste curl examples for every endpoint, and the official SDKs wrap it all in a few lines of code.

Yes — your dashboard has an interactive API Playground. Pick an endpoint, the fields come pre-filled with working sample values, hit Send, and see the live JSON response. It uses your own API key automatically (nothing to paste), so each call counts toward your plan's daily limit just like a real request, and you can copy the exact request as curl, Python, or JS. It's the quickest way from signing up to your first successful call.

Every request carries your key in an X-API-Key header — no OAuth dance, no signing. Create a key in the dashboard, drop it in the header, and you're calling data endpoints in minutes. Keep it server-side; it's a secret.

A 401 almost always means the key is being sent incorrectly. Check that: the header name is exactly X-API-Key (not Authorization or Bearer); you're sending the full bsk_live_… key with no extra spaces or quotes; and the key is still active (a rotated or deactivated key stops working immediately). Generate a fresh key in the dashboard if in doubt.

Use the /v1/search endpoint with a company name or partial symbol — it resolves names to the NSE/BSE ticker you pass to every other endpoint. Tickers are the exchange symbols (e.g. RELIANCE, TCS), uppercase and without the .NS/.BO suffixes some other providers use.

From official and statutory sources: recognised stock exchanges for prices, indices, and market data; companies' regulatory financial and shareholding disclosures and SEBI filings for fundamentals, corporate actions, and insider trades; and AMFI for mutual-fund NAVs and holdings. Each record we return carries its source and, where applicable, an as-of date. See our Data Sources page for the full provenance.

End-of-day. Prices, deals, and FII/DII activity are ingested after market close each trading day; financials, shareholding, and mutual-fund holdings refresh on their filing cadence (quarterly or monthly). This is not a tick-by-tick live feed. You can see live freshness for every pipeline on our status page.

No. BharatStock is a REST API for end-of-day and historical data — prices, financials, filings, deals, holdings, and more — not a tick-level streaming feed.

NSE and BSE listed equities (including the NSE SME/EMERGE universe for prices), market indices, and mutual funds (industry-wide AMFI NAVs plus first-party holdings from 40+ fund houses). Equities carry prices, financials, ratios, shareholding, corporate actions, and insider trades. We don't currently cover derivatives (F&O), commodities, or currencies.

Our mutual-fund data is built on AMFI's two public feeds — the daily NAV file and the monthly portfolio disclosures. Per scheme we provide: identity (name, AMC, plan, option, ISINs), category, daily NAV and full NAV history, trailing returns computed from NAV, and the monthly stock-level holdings (quantity, market value, % of AUM, month-over-month change). We do not currently provide fund manager, expense ratio, benchmark (or benchmark history), riskometer, exit load, scheme-level AUM in rupees, or net flows — those come from scheme SID/SAI documents, factsheets, or a licensed vendor we don't ingest. We don't store a scheme's total AUM, but each holding row carries its pct_of_aum. If one of these is a blocker for your use case, tell us — it helps us prioritise.

Yes, for share-count events. Every price row carries the raw close (as traded on the exchange, never altered) alongside an adjusted_close and the adjustment_factor applied. The adjustment covers bonus issues and face-value (stock) splits — the actions that change the share count — so charts and price-based CAGR stay continuous across them. It is not a dividend-reinvested total-return series, and does not currently adjust for rights issues or demergers. If adjusted_close equals close for a stock, that's expected: either it had no bonus/split in that range, or its history was already adjusted at source (we detect that and avoid double-adjusting). Note that volume and turnover are raw as-traded figures — they are not split/bonus adjusted; only close gets the adjusted_close companion. If you need share-count-consistent volume, adjust it yourself using the corporate-actions endpoint.

We serve financials exactly as the company filed them with the exchange (XBRL), labelled with their consolidation basis (consolidated vs standalone) and period. Third-party aggregators often differ because they mix bases, use trailing-twelve-month windows differently, or apply their own adjustments. A positive P/E on a loss-making year from a one-off exceptional gain, or a figure that differs from Screener.in, is usually the as-filed number being correct — not an error. Each row carries its source, period_end_date, and consolidation_type so you can see exactly what you're looking at.

Coverage follows what the exchanges and filers publish. Some BSE-only micro-caps and SME listings have prices but little or no structured financial history simply because it isn't filed in a machine-readable form. If you spot a gap on an actively traded, properly listed company, let us know the ticker and we'll check the pipeline — but we can't manufacture data a company never filed.

Dates are plain calendar dates in YYYY-MM-DD (ISO 8601) — a price's trade_date, a financial's period_end_date, a corporate action's ex_date, and so on. These are Indian-market trading/filing dates. Daily-limit resets are the one exception: they roll over at UTC midnight, not IST.

All prices and financial figures are in Indian Rupees (INR). Financial statement line items are stored in absolute rupees (not lakhs or crores), so you don't need to multiply by a scale factor — a revenue of ₹10 crore is returned as 100000000. Ratios like P/E and ROE are plain numbers, and percentages (dividend yield, shareholding) are returned as described in each endpoint's docs. One unit to watch on the screener/metrics: avg_turnover_30d is in INR lakhs (= ₹100,000), and the 30-day aggregates (avg_turnover_30d, avg_volume_30d, avg_delivery_pct_30d) average a 30-calendar-day trailing window — roughly 20–22 trading sessions, not a fixed 30-session count.

Prices only exist for trading days — there are no rows for weekends, exchange holidays, or a day a stock didn't trade. A gap on a single date is usually a market holiday rather than a missing record. For filings-based data (financials, shareholding, holdings), rows appear on the company's reporting cadence, so there's one per quarter/month, not per day.

Yes — the corporate-actions endpoint returns dividends, bonus issues, stock splits, rights issues, and buybacks with their ex-dates. Note that bonus and split events also feed the adjusted_close price series; dividends do not (our adjusted price is not a dividend-reinvested total-return series).

History stays attached to the stock through ticker changes, so you can still pull a renamed company's older prices and filings. Delisted stocks keep their historical record but stop getting new rows after they leave the exchange. If a company's ISIN was reissued or it merged, the series is consolidated under the surviving listing — search by the current name or ISIN to find it.

Each daily price row carries trade_date, open, high, low, close, and volume, plus the adjusted_close and adjustment_factor for split/bonus continuity. The raw close is always the as-traded exchange price; use adjusted_close when you need a continuous series across share-count events.

Yes. Records carry provenance so you can trace them: financials include a source (which filing/exchange feed) and consolidation_type, prices trace to the exchange bhavcopy, and mutual-fund data to AMFI or the fund house's own disclosure. Our Data Sources page lists every dataset's origin, and the status page shows how fresh each pipeline is.

Two things. First, the industry-wide scheme universe with daily NAVs for every AMC, sourced from AMFI. Second, per-stock portfolio holdings — which schemes hold a given stock — from AMFI plus the fund houses' own monthly disclosures (40+ first-party AMCs). You can list/search schemes, pull a scheme's NAV history and trailing returns, and look up which funds hold a particular stock. See the coverage page for the full list of fund houses.

Use the schemes list endpoint (/v1/mf/schemes) and filter by name (q), amc, category, plan (Direct/Regular), option (Growth/IDCW), or an exact isin. Each result is one AMFI scheme code — a specific (scheme, plan, option) variant with its own NAV — which you then pass to the NAV and returns endpoints. A fund typically has several codes (e.g. a Direct-Growth code separate from Regular-IDCW).

NAVs come from AMFI's daily publication, so there's one value per scheme per business day. The scheme-detail endpoint returns the latest NAV with its as-of date; the NAV-history endpoint returns the daily series (most recent first) with from/to filters. Free keys see a recent window (about one year); paid keys get the full archive back to the series' inception.

The returns endpoint gives trailing 1m / 3m / 6m / 1y / 3y / 5y plus since-inception, computed directly from the stored NAV series — never precomputed or stored, so they can't drift from the NAVs. Horizons under a year are a simple point-to-point percentage change; one year and longer are annualized (CAGR). For each horizon we use the latest NAV versus the NAV on-or-before that many days earlier. A horizon with not enough history returns null.

Because free keys only see a recent NAV window (~1 year), the longer horizons don't have enough history behind them and resolve to null — the multi-year return history is a paid feature. Upgrade to a paid plan to unlock the full NAV archive and the 3y/5y/since-inception figures.

Use the per-stock mutual-fund holdings lookup with the stock's ticker — it returns the schemes reporting a position in that company for the latest portfolio month (you can request an earlier month too). Holdings follow the funds' monthly disclosure cadence, so they update roughly once a month, not daily. Like other deep history, older months are a paid feature; free keys are limited to the recent window.

They answer different questions. NAV is a scheme's per-unit price, published daily by AMFI — use it for a fund's price history and returns. Holdings are the underlying portfolio (which stocks a scheme owns and how much), disclosed monthly by the fund houses — use it to see fund ownership of a stock. One is the fund's price, the other is what the fund is made of.

Every plan, including Free, can call every endpoint — no feature is locked behind a paywall. The difference is depth: Free covers the most recent year of history, while paid plans unlock the full archive (11+ years of prices, deep financials, and more), alongside higher daily request limits.

Paid plans reach back 11+ years for prices, with deep financials, shareholding, corporate actions, and holdings archives alongside. The Free tier covers the most recent year (annual financials get roughly two fiscal years so year-on-year comparisons work), which is plenty for prototyping before you upgrade.

Requests return a 429 with your plan's limit in the response body and a Retry-After header. The counter resets at UTC midnight, or you can upgrade any time to raise it immediately. The limit is a per-day request count, not per-minute, so there's no separate burst/throttle rate to worry about.

Paginated endpoints like historical /prices accept a page_size from 1 up to 1,000 records per page (default 100). Each response includes total_items and total_pages so you can page through a full history deterministically.

Yes. Each HTTP request to a data endpoint counts as one against your daily limit, regardless of how many records come back in the response. Paging through a long history uses one request per page, so a larger page_size fetches more data per request.

No. There's no per-minute, per-second, or burst rate limit, and no separate concurrency cap — the only limit is your plan's daily request quota (counted per UTC calendar day, resets at UTC midnight). Keep concurrency reasonable so a burst doesn't exhaust the day's quota early. If you do hit the cap you get an HTTP 429 with a Retry-After header, and the official SDKs auto-retry it for you.

It depends on the path. Upgrading from Free to a paid plan through checkout issues a new key, shown once on the confirmation screen — your old free key is retired, so switch your app to the new bsk_live_… (copy it then; it isn't shown again). Changing between paid plans (e.g. Starter → Developer) is an in-place swap: the same key stays, with just the new daily limit applied and nothing to re-deploy. Either way your account keeps one active key at a time. (Separately, the Rotate button regenerates a key's secret in place without touching your plan — use it if a key is exposed.)

No — the published self-serve tiers are Free, Starter, Developer, and Pro, with no in-between or bonus tier. The difference between Starter and Developer is daily request volume, not features, so pick the tier whose daily quota covers your usage. If none of the tiers fit, contact us from the dashboard and we can discuss options.

If your usage outgrows Pro, get in touch via the dashboard and tell us your use case and expected volume. We provision higher-volume access case by case rather than listing it as a self-serve tier.

Historical daily OHLCV lives at GET /v1/stocks/{ticker}/prices. The whole API is versioned under the /v1 prefix (e.g. https://bharatstockapi.com/v1/stocks/RELIANCE/prices). Pass the ticker as the exchange symbol in the path — RELIANCE, TCS — uppercase, with no .NS/.BO suffix.

No Bearer prefix. Send the key directly in an X-API-Key header — X-API-Key: bsk_live_… — not in an Authorization: Bearer … header. There's no OAuth and no request signing.

All query parameters are optional. from and to bound the date range (YYYY-MM-DD); page (default 1) and page_size (default 100, max 1,000) control pagination; and exchange (NSE or BSE) disambiguates a ticker that's listed on both. With no parameters you get the first page (100 most recent rows) of the full available history for your plan.

Yes — both bounds are inclusive. from=2024-01-01&to=2024-01-31 returns rows with trade_date from the 1st through the 31st, both ends included. Dates are plain calendar dates (YYYY-MM-DD, ISO 8601) representing Indian-market trading days; rows only exist for days the stock actually traded. On a Free key the lower bound is also clamped to your history window (about one year), so an older from is silently raised to the earliest date your plan can see.

The exchange parameter picks which listing to resolve when the same ticker exists on both venues — NSE returns the National Stock Exchange security, BSE the BSE one. The ticker in the path is matched to a security by its exchange symbol; if a symbol is unique you can omit exchange entirely, and the per-stock detail endpoint (GET /v1/stocks/{ticker}) tells you which exchanges carry it.

Yes, pages are 1-based — the first page is page=1 (not 0). page_size accepts a minimum of 1, defaults to 100, and caps at 1,000 records per page. Values outside that range are rejected with a 422 validation error.

A JSON object with two keys: a data array of price rows and a pagination object. Each row carries trade_date, open, high, low, close, prev_close, volume, turnover_lakhs, num_trades, delivery_qty, delivery_pct, plus the split/bonus-continuous adjusted_close and the adjustment_factor applied. Numeric fields can be null where the source didn't report them. See the API reference for a full example payload.

The prices response itself returns only data and pagination — it does not repeat the ticker or exchange, since you supplied them in the request path. If you need the resolved security's identity (name, exchange listings, ISIN), call GET /v1/stocks/{ticker}, which returns the full stock detail.

It carries page, page_size, total_items (total matching rows), and total_pages (ceil(total_items / page_size)). You're on the final page when page == total_pages; requesting a page beyond that returns an empty data array with the same totals, so you can also stop when data comes back empty.

Rows are ordered by trade_date descending — most recent first — and trade_date is unique per security, so paging straight through gives a clean, non-overlapping sequence with no duplicate rows across pages. (Pages are a snapshot in time: if a new trading day is ingested between two of your page requests, the window shifts by one row, so for a strictly stable walk pin the upper bound with to.)

Errors are standard JSON with a detail field and the matching HTTP status. 401 — missing or invalid/inactive X-API-Key (detail is a short message). 404 — the ticker (or ticker+exchange) didn't resolve to a security. 429 — daily limit reached; the detail is a structured object with the message plus reset info (retry_after_seconds, resets_at), and for Free keys an upgrade link. A 422 covers malformed parameters (e.g. a bad date or an out-of-range page_size).

There are no proactive X-RateLimit-Remaining-style headers on successful responses today. When you do hit the daily cap, the 429 carries a Retry-After header (seconds until the counter resets) and an X-Upgrade-URL header, and the same reset info is in the response body. To track usage proactively, read your live per-key counts in the dashboard. Limits reset at UTC midnight.

Each HTTP request counts as one, so paging through a long history uses one request per page — a larger page_size fetches more rows per request. Requests rejected before they run don't burn quota: a 401 (bad key) and a 429 (already over the limit) are not counted. A request that authenticates and is served does count even if the handler then returns a 404 (unknown ticker) or an empty page — so validate tickers (via /v1/search) to avoid spending calls on typos.

Yes, values can change after first publication. Prices are restated when a bonus/split is applied (the adjusted_close/adjustment_factor move while the raw close stays as-traded), and financials are updated if a company re-files or a better source (e.g. a consolidated filing) supersedes an earlier one — each financial row carries its source and consolidation_type so you can see the basis. We don't expose a point-in-time/as-of snapshot API: each call returns the current best-known values. If you need an immutable record for a given day, store the response on your side, and watch the status page for pipeline freshness and corrections.

Cards and PayPal worldwide, Apple Pay and Google Pay on supported devices, plus UPI and netbanking for Indian customers. Payments are processed by our authorised Merchant-of-Record resellers (Paddle and Lemon Squeezy), both of which accept international card and PayPal payments.

Yes. We accept international card and PayPal payments through two authorised Merchant-of-Record resellers: Paddle (cards & PayPal worldwide, plus UPI for customers in India) and Lemon Squeezy (cards & PayPal). At checkout you can pick either option — both work internationally and handle billing, tax, receipts, and refunds for your purchase.

Yes, any time. There's no lock-in contract — upgrade, downgrade, or cancel whenever your usage changes.

Paid plans renew automatically each billing cycle through the payment mandate you set up at checkout. A few payment paths are single-cycle (pay-per-period) rather than auto-renewing — your dashboard shows your plan's current status and renewal state either way. You can cancel before the next renewal to stop further charges.

Your subscription is marked past due and the payment gateway automatically retries the charge over a recovery window. During that window your access is unchanged — nothing is downgraded while a renewal is still being retried — so a temporary decline (an expired card or a one-off bank issue) usually resolves on its own once a retry succeeds or you update your payment method from the dashboard. If the charge can't be recovered, the subscription is cancelled and your key drops to the free tier. For UPI mandates specifically, a decline often means the mandate itself was closed or revoked, which isn't recoverable by retry; in that case we cancel a subscription that has stayed past due for more than about a week and your key falls to free — just start a fresh checkout to resubscribe. You're never charged for, or kept on, a plan whose renewal didn't go through.

No — you pay only the prorated difference for the days remaining in your current billing period. When you upgrade, we credit the unused value of your current plan for the rest of the cycle and charge just the difference to the new plan now; the full new-plan price then applies from your next renewal. For example, upgrading from Starter (₹500/mo) to Developer (₹1,000/mo) early in a monthly cycle works out to roughly ₹650 now (plus applicable tax), then ₹1,000/month thereafter. Your current plan stays active until the upgrade payment succeeds, so there's no gap in access, and if you don't complete the checkout nothing changes. The exact amount, including any tax, is shown on the checkout screen before you confirm.

A downgrade changes immediately with nothing to pay today — the lower price is simply collected at your next renewal. You keep access to your current plan's limits until the end of the already-paid period.

An upgrade activates as soon as the prorated payment succeeds. Payment confirmation can take a moment to propagate (UPI mandate debits in particular can take up to 24 hours on first setup), so refresh your dashboard — it reflects the live subscription state. If you started an upgrade checkout but didn't complete it, nothing changes and you stay on your current plan. If a confirmed payment still isn't applied after a refresh, contact support from the dashboard with your payment reference and we'll reconcile it.

Payment confirmation can take a moment to propagate (UPI mandate debits in particular can take up to 24 hours on first setup). Refresh your dashboard — it reflects the live subscription state. If a confirmed payment still isn't applied after that, contact support from the dashboard with your payment reference and we'll reconcile it.

Payment receipts are issued by the payment gateway (such as Paddle, Lemon Squeezy, or Razorpay) at checkout. Paddle and Lemon Squeezy are Merchants of Record and issue the tax invoice for your purchase. If you need a GSTIN or business name on the invoice, enter it in the gateway's checkout where supported, or contact us. Refunds follow our refund policy.

Yes. Individuals are welcome on every paid plan — for a personal project, a hobby, research, or a commercial product you're building — you don't need to be a registered business, and commercial use is fine (what the licence limits is redistributing the raw data to third parties, not whether your use makes money). GSTIN is optional; leave it blank. For the business website / domain field, the upgrade form has an "I don't have a business website" checkbox right under it — tick that and the field becomes optional so you can continue to payment. If you'd rather enter something, a link to your project (e.g. a GitHub repo) is fine too.

Plan prices are shown exclusive of tax. Applicable taxes (GST for India, roughly 18%) are added on top at checkout by our Merchant-of-Record, so the amount charged is a little higher than the listed price — e.g. a ₹600 plan is billed as about ₹600 + GST. That's the tax, not a markup, and it appears itemised on the gateway's tax invoice.

No. Both your price and your daily request limit are locked in when you subscribe. If we later change a plan's advertised price, your recurring charge stays the price you signed up at — the new price applies only to new sign-ups. Likewise, your daily request limit is grandfathered: changing a plan's limit only affects keys created (or plan-changed) after the change, so your existing key keeps the limit it already had. A new limit never retroactively reduces an active subscriber's quota. The only time your price or limit changes is when you change plans (upgrade or downgrade).

Yes. Your subscription is an internal-use licence: you can consume the data inside your own application and show the analysis you derive from it to your own users — including in a paid, commercial product. Commercial use is allowed; the boundary is redistribution. What you can't do is resell, re-serve, or bulk-redistribute the raw data to third parties, or stand up a competing data feed. See our Terms for the precise wording.

Yes — anything you compute is yours to display: relative-strength scores and rankings, sector-rotation / RRG coordinates, momentum and screening results, indicators, signals, and backtest outputs (equity curves, win rate, drawdown, trade stats). Showing your own derived analysis to your subscribers is fully within the internal-use licence. The only limit is a chart or field that effectively reproduces the underlying raw exchange price series itself (see the next question).

Stock and company names and identifiers (ticker, ISIN) — yes, display freely. Raw or adjusted NSE/BSE prices, OHLCV, price charts, and index values shown to your users are a different matter: that is treated as display/redistribution of exchange data and needs your own Exchange Display/Redistribution Licence from NSE and/or BSE, which our standard plans don't grant or pass through. The company-filing datasets (financials, shareholding, corporate actions, insider trades) and mutual-fund NAV/returns/holdings may be displayed with attribution, as they come from statutory SEBI/AMFI filings rather than the exchange price feed.

Yes — caching and storing responses server-side for your own backend, analytics, reproducibility, and backtesting is exactly the internal use the licence allows, and it's the recommended way to build (fetch once, compute, and serve your users from your own store). Note that storing the data in your own database doesn't change the rule above: displaying raw exchange prices to your users is still redistribution regardless of where you serve them from. When a subscription ends, so does the internal-use licence — you should stop processing and displaying the data; see our Terms for the post-termination detail.

Your user count doesn't drive the plan — your API request volume does. A well-built product fetches each data point once into its own backend and serves all its users from that cache, so 100 or 10,000 subscribers can run on the same request volume. Most subscriber-facing products of modest size fit comfortably within Pro (40,000 requests/day). There's no self-serve white-label or redistribution tier — if you expect to genuinely exceed Pro, contact us with your estimated peak daily request volume and we'll provision higher-volume access case by case.

Only if you intend to publicly display raw NSE/BSE price data (prices, OHLCV, price charts, index values) to your users — that requires your own Exchange Display/Redistribution Licence directly from the exchange, on the exchange's own fee schedule. We don't resell, bundle, or quote those fees. If your product only shows your own derived analytics plus the company-filing and mutual-fund datasets, you typically need no exchange licence at all. For specifics on a price-display licence, the exchange (NSE/BSE) is the authority; anything in this FAQ is a general summary and our Terms govern.

Yes, on the Developer and Pro plans. Using the data for your own personal and internal model evaluation, backtesting, and signal validation is included on those tiers by default — no separate approval needed. It is not included on Free or Starter; upgrade to Developer or Pro for model-evaluation use. The line is training: fine-tuning or training a model that you then distribute, license, sell, or embed in a commercial product — or any model trained on raw NSE/BSE Exchange Data — needs a separate written Model Training License from us. Evaluating and backtesting your own strategies is fully within a Developer/Pro subscription; see our Terms for the exact wording.

Yes — hand-written, typed clients for Python (pip install bharatstock) and JavaScript/TypeScript (npm install bharatstock). Both mirror the full public API. If you'd rather stay language-agnostic, the API is plain REST and JSON, so any HTTP client works.

Yes. We publish an official MCP (Model Context Protocol) server — npx bharatstock-mcp — that exposes the API as 31 tools to AI assistants like Claude Desktop, Cursor, and Kiro, covering the full consumer surface (quotes, prices, financials, fundamentals, deals, screener, indices, FII/DII, and mutual-fund schemes/NAVs/holdings/portfolios). See the MCP page for setup and the full tool list.

We recommend keeping your API key server-side and proxying requests through your own backend — your key is a secret, and exposing it in client-side code lets anyone read and reuse it against your daily limit. For client apps, put a thin server layer in between that holds the key.

Rotate a key from the dashboard — it regenerates the secret in place, so your plan, subscription, and usage history stay intact while the old secret stops working immediately. Rotate right away if a key is ever exposed. There's a small daily cap on rotations per key to prevent accidental churn.

Use the support/feedback option in your dashboard, or email us at [email protected] — include your API key prefix (bsk_live_…) and any error code or ticker so we can look into it quickly. Most questions are already answered here or in the API reference, which is the fastest way to get unblocked.

We store only what's needed to run your account and bill you, and we don't sell your data. Full detail is in our privacy policy and terms.

Start building on real Indian market data today.

Get a free API key in under a minute. No card, no sales call.