Indian Stock Exchange API — Try the interactive demo
A guided live test. Prefer the raw endpoints? See the API reference & playground →
Enter an API key from your Dashboard to enable the examples below. Requests send it to this platform for authentication.
Log in / Sign up · Dashboard →
Please paste your API key first.
Endpoints
Your API key is attached automatically to each call.
/api/project/indian-stock-exchange-api/bse-most-active BSE Most Active Stocks by Trading Volume
Details
Returns the latest most active stocks on the Bombay Stock Exchange (BSE), ranked by trading volume, as a JSON array of stock quote objects. The endpoint is a plain GET on /BSE_most_active and accepts no query, path or body parameters, so every call returns the same kind of snapshot. In the observed response (HTTP 200) the array held 10 records in descending volume order, and each record carried 19 fields with no null values: ticker (string with a .BO suffix) and company (name); price, percent_change, net_change, open, high, low, close, bid and ask (numbers); volume (integer); 52_week_high and 52_week_low; low_circuit_limit and up_circuit_limit; and the text labels short_term_trend, long_term_trend and overall_rating. The source documentation only illustrates six of these fields (ticker, company, price, percent_change, net_change, volume) with sample values that are illustrative rather than live data; the other thirteen fields come from the observed response. The result is an informational market snapshot, not a licensed tick feed, and the response carries no currency or timestamp field.
Request cost is temporarily unavailable. No price is assumed.
/api/project/indian-stock-exchange-api/nse-most-active NSE Most Active Stocks by Trading Volume
Details
Returns the latest most active stocks on the National Stock Exchange of India (NSE), ranked by trading volume, as a JSON array of stock quote objects. The endpoint is a plain GET on /NSE_most_active and accepts no query, path or body parameters. In the observed response (HTTP 200) the array held 10 records in descending volume order, and each record carried 19 fields with no null values: ticker (string with a .NS suffix) and company (name); price, percent_change, net_change, open, high, low, close, bid and ask (numbers); volume (integer); 52_week_high and 52_week_low; low_circuit_limit and up_circuit_limit; and the text labels short_term_trend, long_term_trend and overall_rating. The observed trend labels were Bearish, Bullish and Neutral for short_term_trend, and Bearish, Bullish and Moderately Bullish for long_term_trend and overall_rating. The source documentation only illustrates six of these fields (ticker, company, price, percent_change, net_change, volume) with sample values, such as a RELIANCE.NS row, that are illustrative rather than live data; the other thirteen fields come from the observed response. The result is an informational market snapshot, not a licensed tick feed, and the response carries no currency or timestamp field.
Request cost is temporarily unavailable. No price is assumed.
/api/project/indian-stock-exchange-api/commodity-futures-data-api Active Commodity Futures Contracts Snapshot
Details
Returns a snapshot of market data for currently active commodity futures contracts as a JSON array with one object per contract, covering prices, trading volume, open interest, expiry and contract month. The endpoint is a plain GET on /commodities and accepts no query, path or body parameters. No live probe call was recorded for this endpoint, so everything below comes from the source documentation and its bundled example records and has not been verified against a live response. The documentation table names 20 camelCase fields: contractId, dataTimestamp, commoditySymbol, expiryDate, lastTradedPrice, lastTradeQuantity, lastTradeTime, averageTradedPrice, totalVolume, openInterest, openingPrice, highPrice, lowPrice, closingPrice, totalTradedValue, priceUnit, contractSize, contractMonth, priceChange and percentageChange. The bundled example records instead use 26 snake_case keys: id, messageTime, product, expiry, product_month, last_traded_price, last_traded_quantity, last_traded_time, average_traded_price, total_quantity_traded, open_interest, open_price, high_price, low_price, close_price, total_traded_value, price_quotation_unit, quotation_lot, change, per_change, buy_price, buy_quantity, sell_price, sell_quantity, option_type and strike_price. In those records most numeric values are quoted strings, and the sample rows are dated 21 Jun 2024 with AUG2024 and SEP2024 contract months, so they illustrate the shape rather than current data. The result is an informational snapshot, not an execution or licensed tick feed.
Request cost is temporarily unavailable. No price is assumed.
/api/project/indian-stock-exchange-api/corporate-actions Get dividends, splits, bonus issues, rights and board meetings for an Indian listed company by name
Details
Returns the corporate-action record of one Indian listed company, looked up by company name through the required stock_name query parameter (for example infosys). The response is a JSON object with five sections: board_meetings, dividends, splits, bonus and rights. In the observed probe call for stock_name=infosys (HTTP 200), every section carried a title and a msg string. Sections with history also carried a header array of column names and a data array of rows: board_meetings used the columns Date and Agenda, dividends used Record Date, Ex-Date, Dividend Percentage and Details, and bonus used Record Date, Ex-Date and Ratio. Sections with nothing to report (splits and rights in the probe) omitted header and data and returned only a plain-language msg, such as a note that no stock split has been announced for the last few years. In the sampled rows every cell was a string and dates were formatted DD-MM-YYYY. No formal response schema is published, so the section layout above is observed behaviour from one probe rather than a guaranteed contract. The data is informational and is not a substitute for the official exchange filing.
| Parameter | In | Value |
|---|---|---|
| query |
Request cost is temporarily unavailable. No price is assumed.
/api/project/indian-stock-exchange-api/fetch-52-week-high-low-data List BSE and NSE stocks at their 52-week highs and lows in a single parameterless call
Details
Returns the stocks that are trading at their highest and lowest prices of the last 52 weeks on both the BSE and NSE. The endpoint takes no parameters. According to the endpoint documentation and its example response, the JSON object has two top-level keys, BSE_52WeekHighLow and NSE_52WeekHighLow. Each contains a high52Week array and a low52Week array. Entries in the high lists carry ticker, company, price and 52_week_high; entries in the low lists carry ticker, company, price and 52_week_low. In the example, tickers use the .BO suffix for BSE and the .NS suffix for NSE, and numeric fields are JSON numbers. The documentation warns that the response may be an empty list when the market is closed, so an empty result outside trading hours is expected rather than an error. No live probe call was recorded for this endpoint, so every field above comes from the documented example and has not been verified against a live response. The example also shows list lengths that differ between exchanges and sections, and no pagination or refresh interval is documented. The data is an informational snapshot, not a licensed tick feed.
Request cost is temporarily unavailable. No price is assumed.
/api/project/indian-stock-exchange-api/historical-data Get NSE price history, 50 and 200 day moving averages and volume for an Indian stock by name
Details
Returns historical series for one Indian stock, looked up by company name. stock_name is required (for example tcs), period is optional and accepts 1m, 6m, 1yr, 3yr, 5yr, 10yr or max with a documented default of 5yr, and filter is optional with a documented default of default. The documented filter values are price, pe, sm, evebitda, ptb, mcs and default; only price has been exercised in a probe. The observed probe call (stock_name=tcs, period=1m, filter=price) returned HTTP 200 with a JSON object whose single key, datasets, held four objects, each with label, meta, metric and values. The datasets were Price on NSE (metric Price, meta is_weekly=false), 50 DMA (metric DMA50), 200 DMA (metric DMA200) and Volume (metric Volume). In the probe, every values entry was an array starting with an ISO date (YYYY-MM-DD); price and moving-average values were strings with two decimals, while volume values were integers followed by an object with a delivery field that held a whole number or null. The 1m probe returned 20 data points per dataset. Longer periods, the max period and the other filter values were not probed, so their dataset lists and spacing are unverified. The endpoint documentation's example request uses symbol, but the declared parameter is stock_name, which is what the probe used. The data is informational and not an execution-grade tick feed.
| Parameter | In | Value |
|---|---|---|
| query | ||
| query | ||
| query |
Request cost is temporarily unavailable. No price is assumed.
/api/project/indian-stock-exchange-api/historical-stats Get quarterly results, yearly results, balance sheet, cash flow, ratios and shareholding history for an Indian stock by company name
Details
Returns historical financial statistics for one Indian listed company, looked up by company name. stock_name is required (for example TCS, or TATAMOTORS as in the endpoint documentation). stats is optional and names the statistic groups to return; its documented default is the comma-separated list quarter_results, yoy_results, balancesheet, cashflow, ratios, shareholding_pattern_quarterly and shareholding_pattern_yearly, while the documentation's example request uses a single value, quarter_results. No probe call was made for this endpoint, so every response detail below comes from an unverified source example: a JSON object keyed by line item (Sales, Expenses, Operating Profit, OPM %, Other Income, Interest, Depreciation, Profit before tax, Tax %, Net Profit and EPS in Rs), where each item maps period labels such as Jun 2021, Sep 2021 and Mar 2024 to numbers. That example holds 13 quarterly periods per line item and resembles the quarter_results group; the labels appear in alphabetical rather than chronological order, and no currency units are stated beyond the EPS in Rs and percentage labels. The response layouts of the other six groups, how several groups are combined in one response and the behavior for an unknown company name are not verified. The figures are informational and not audited filings or investment advice.
| Parameter | In | Value |
|---|---|---|
| query | ||
| query |
Request cost is temporarily unavailable. No price is assumed.
/api/project/indian-stock-exchange-api/industry-search Search Indian stocks and funds by name or industry term and get NSE symbol, BSE scrip code, RIC codes, sector and trend labels
Details
Searches Indian listed instruments for a text term and returns a JSON array of match objects. query is required (for example tata). The endpoint documentation describes it as a search within an industry; the observed probe (query=tata) returned HTTP 200 with a JSON array of 17 objects, every one with the same ten keys: id (an internal identifier such as S0003051), commonName, stockType, exchangeCodeBse (the BSE numeric scrip code as a string), exchangeCodeNsi (the NSE symbol), bseRic, nseRic (Reuters-style codes such as TCS.BO and TCS.NS), mgIndustry, mgSector and activeStockTrends, an object with shortTermTrends, longTermTrends and overallRating. In the probe, stockType was Equity for 12 rows, Fund for 3 ETF rows and null for 2 rows; exchangeCodeNsi was null for one row and exchangeCodeBse was an empty string for one fund. Also in the probe, mgIndustry and mgSector were null in all 17 rows and all three trend fields held the text NA. The unverified source example shows these fields populated (for instance Software & Programming, Technology, Bearish and Bullish), and it lists TATAMOTORS and Tata Motors DVR where the probe returned TMCV and TMPV, so treat the example values as illustrative. No pagination or filter parameter is declared, and the maximum number of matches is unverified. The data is informational, not investment advice.
| Parameter | In | Value |
|---|---|---|
| query |
Request cost is temporarily unavailable. No price is assumed.
/api/project/indian-stock-exchange-api/ipo Get upcoming, active, closed and listed Indian IPOs with price band, lot size, SME flag, bidding dates and listing details
Details
Returns the Indian IPO feed with no input parameters. The endpoint documentation describes it as the latest upcoming, listed, active and closed IPO data. No probe call was made for this endpoint, so the response details come from a truncated, unverified source example dated September 2024. In that example the response is a JSON object whose keys are status groups, with active and closed arrays visible, and each array item is an issue object with name, symbol, status, is_sme, min_price, max_price, issue_price, lot_size, bidding_start_date, bidding_end_date, listing_date, listing_price, listing_gains, additional_text and document_url. Dates are ISO YYYY-MM-DD strings. In the sampled active rows the bidding dates, price band, lot size and a status note such as IPO closes today at 4:50 PM were filled, while issue_price, listing_date, listing_price, listing_gains and document_url were null. The sampled closed rows carried a listing_date and a document_url, with bidding_end_date and lot_size null. Whether upcoming and listed groups use those exact keys, how fields fill as an issue moves between states, and any limit on list size are unverified. The data is informational and does not support applying for or bidding in an issue.
Request cost is temporarily unavailable. No price is assumed.
/api/project/indian-stock-exchange-api/mutual-fund-search Search Indian mutual fund schemes by name and get the scheme id, ISIN, scheme type and category id of each match.
Details
Searches Indian mutual fund schemes with one required free-text query parameter, for example nippon, and returns a JSON array of matching schemes. Each documented item carries id (an internal scheme identifier such as MF000063), schemeName (the full plan name, including the plan variant such as Direct Plan - Growth Option or Payout Income Dist cum Cap Wdrl), isin (for example INF204KA1W02), schemeType (the sample shows Open Ended Investment Company) and categoryId (a category code such as MFCAT002 or MFCAT003). These fields come from the published documentation and a stored sample response for query=nippon; no live probe of this endpoint has been run in this catalog, so the matching rules for multi-word queries, the result cap and the ordering are unverified. The endpoint identifies schemes only. It returns no NAV, returns or ratings, which the mutual funds listing endpoint provides by fund name.
| Parameter | In | Value |
|---|---|---|
| query |
Request cost is temporarily unavailable. No price is assumed.
/api/project/indian-stock-exchange-api/mutual-funds List Indian mutual funds grouped by asset class and category with latest NAV, daily change, asset size, 1 month to 5 year returns and star rating.
Details
Returns the mutual fund overview in a single call with no input parameters. The response is one JSON object keyed by asset class, then by category name, and each category holds an array of funds. The documented example shows Equity with a Large Cap category; the stored sample response shows Debt with categories such as 10 yr Government Bond, Banking & PSU and Corporate Bond. Each fund entry has fund_name, latest_nav, percentage_change, asset_size, 1_month_return, 3_month_return, 6_month_return, 1_year_return, 3_year_return, 5_year_return and star_rating, all as JSON numbers. In the sample, 3_year_return, 5_year_return and star_rating are null for some funds, so parse them as nullable. The evidence does not state the unit of asset_size, the as-of date of the NAV or whether returns are annualised, and no live probe of this endpoint has been run in this catalog. Entries carry no ISIN or scheme id; use the mutual fund search endpoint when you need identifiers.
Request cost is temporarily unavailable. No price is assumed.
/api/project/indian-stock-exchange-api/price-shockers List Indian stocks showing sudden price moves, with price, net and percent change, OHLC, volume, circuit limits, deviation from average price and trend ratings.
Details
Returns the current price shocker list for Indian equities in one call with no input parameters. The documentation shows a flat array of entries with ticker (for example BPCL.NS), company, price, percent_change, net_change, high, low, open and volume as numbers. The stored sample response has a different shape: an object with two arrays, BSE_PriceShocker and NSE_PriceShocker, where every value is a string. In that sample the BSE array is empty and the NSE array holds entries dated 2024-06-21 with ric, tickerId, displayName, exchangeType, price, netChange, percentChange, open, high, low, close, volume, bid, ask, bidSize, askSize, yhigh, ylow, upCircuitLimit, lowCircuitLimit, lotSize, averagePrice, noOfDaysForAverage, deviation, actualDeviation, shortTermTrends, longTermTrends, overallRating, priceArrow, date, time and a logo imageUrl. Because the documented and sample shapes disagree and no live probe of this endpoint has been run in this catalog, parse defensively and convert string values to numbers yourself. From the sample numbers, percentChange compares price with the previous close, while actualDeviation is the signed percent gap between price and averagePrice over noOfDaysForAverage days and deviation is its absolute value.
Request cost is temporarily unavailable. No price is assumed.
/api/project/indian-stock-exchange-api/get-stock-data-by-name Get a full Indian stock detail record by company name: BSE and NSE prices, financials, key metrics, analyst view, shareholding and recent news.
Details
Looks up one Indian listed company by name and returns a single JSON object with its detail record. The only input is the required query parameter name, which takes a full company name, a shortened name or a common name for the stock; the documented sample request uses Reliance and the catalog default is tata steel. No ticker or BSE scrip code is needed. Observed in a live probe for name=tata steel (HTTP 200): companyName, industry, currentPrice with BSE and NSE values (returned as strings), percentChange, yearHigh and yearLow, stockTechnicalData (six rows for 5, 10, 20, 50, 100 and 300 days, each with bsePrice and nsePrice), companyProfile (companyDescription, mgIndustry, isInId, exchangeCodeBse, exchangeCodeNse, officers and peerCompanyList), financials (19 period entries with stockFinancialMap keyed CAS, BAL and INC, FiscalYear, EndDate and an Annual or Interim Type), keyMetrics (eight groups: mgmtEffectiveness, margins, financialstrength, valuation, incomeStatement, growth, persharedata, priceandVolume), analystView (rating rows from Strong Buy to Strong Sell plus a Total row, with analyst counts now and 1 week, 1, 2 and 3 months ago), recosBar (rating bands, noOfRecommendations, meanValue, tickerPercentage), riskMeter (categoryName and stdDev), shareholding (four holder categories with dated percentages), stockCorporateActionData (bonus, dividend, rights, splits, annualGeneralMeeting, boardMeetings), stockDetailsReusableData (a quote block with date, time, price, marketCap and valuation ratios), stockFinancialData and recentNews (ten articles with headline, date, summary and url). In that probe futureExpiryDates, futureOverviewData and initialStockFinancialData were null, and the refresh-status fields inside companyProfile were present but null. The documentation also shows a top-level tickerId and numeric prices, but the probe response had no top-level tickerId and its prices were strings, so treat those documented sample details as unverified. The data is an informational market snapshot, not an execution or licensed tick feed.
| Parameter | In | Value |
|---|---|---|
| query |
Request cost is temporarily unavailable. No price is assumed.
/api/project/indian-stock-exchange-api/stock-forecasts Get Indian stock analyst estimates and reported actuals for one measure such as EPS, filtered by period type, data type and data age.
Details
Returns forecast data for one Indian stock and one financial measure. All five query parameters are required: stock_id (the stock identifier; the catalog default is TCS and the documented sample request writes it as tcs), measure_code (one of EPS, CPS, CPX, DPS, EBI, EBT, GPS, GRM, NAV, NDT, NET, PRE, ROA, ROE or SAL; the documentation labels only EPS as earnings per share and DPS as dividends per share), period_type (Annual or Interim), data_type (Actuals or Estimates) and age (Current, OneWeekAgo, ThirtyDaysAgo, SixtyDaysAgo or NinetyDaysAgo). The documented sample request is stock_id=tcs, measure_code=EPS, period_type=Annual, data_type=Actuals, age=ThirtyDaysAgo. Documented statuses are 200 with forecast data matching the query, 404 when no forecasts exist for the stock_id or measure code, and 500 for an unexpected processing error. The stored sample response (a documentation example; this endpoint has not been probed live in this catalog) is a JSON object with measureCode, measureName and a periods array. Each period has ActualReportDate, CalendarMonth, CalendarYear, a FiscalPeriod object (Type and Year) and a RelativePeriod object (Number and Type). In the Actuals sample, each period carries an Actuals.Actual list whose rows include CurrencyCode (INR), NumberOfEstimates, Reported, ReportedDate, Restated, RestatedDate, StandardizedUnexpectedEarnings, SurpriseMean, SurprisePercent, Surprise60DayPercent and PostReport30DayPriceChangePercent. The field layout for data_type=Estimates is not shown in the supplied evidence and is unverified. The prefilled parameter values list every accepted name for that parameter, whereas the documented request sends a single value per parameter.
| Parameter | In | Value |
|---|---|---|
| query | ||
| query | ||
| query | ||
| query | ||
| query |
Request cost is temporarily unavailable. No price is assumed.
/api/project/indian-stock-exchange-api/analyst-recommendations Get analyst price targets and the buy-to-sell recommendation consensus for one Indian stock, with one-week to 90-day snapshots.
Details
Returns analyst target price statistics and recommendation consensus for one Indian listed stock as a single JSON object. The only input is the required query parameter stock_id; the catalog default and probe value is TCS, and the documentation describes it only as the unique identifier of the stock. The response has four sections: priceTarget (the current consensus target), priceTargetSnapshots, recommendation (the current consensus rating) and recommendationSnapshots. Observed in a live probe for stock_id=TCS (HTTP 200): priceTarget had nine members (CurrencyCode, UnverifiedMean, PreliminaryMean, Mean, High, Low, NumberOfEstimates, Median, StandardDeviation) with CurrencyCode INR. priceTargetSnapshots.PriceTargetSnapshot held four entries with Age values OneWeekAgo, ThirtyDaysAgo, SixtyDaysAgo and NinetyDaysAgo, each carrying CurrencyCode, Mean, High, Low, NumberOfEstimates, Median and StandardDeviation. recommendation had Mean, High, Low, NumberOfRecommendations, UnverifiedMean, PreliminaryMean and a Statistics.Statistic list of five rows pairing a Recommendation code from 1 to 5 with NumberOfAnalysts; the five analyst counts added up to NumberOfRecommendations in that probe. recommendationSnapshots.RecommendationSnapshot held the same four Age values, each with Mean, High, Low, NumberOfRecommendations and Statistics. The documented scale reads 1 Buy, 2 Outperform, 3 Hold, 4 Underperform and 5 Sell, so a lower Mean is more bullish, and High is the most bullish code (1) while Low is the most bearish (5). The documentation also describes a 404 body with the text Stock target price not found and a 500 body starting An error occurred; neither was observed in the probe, and only TCS was probed, so the figures in the documentation example and the behaviour for other identifiers are unverified. The data is an informational market snapshot, not investment advice or a licensed feed.
| Parameter | In | Value |
|---|---|---|
| query |
Request cost is temporarily unavailable. No price is assumed.
/api/project/indian-stock-exchange-api/get-trending-stocks Get the current top gaining and top losing Indian stocks with price, percent change, circuit limits, trend labels and 52-week range.
Details
Returns a snapshot of the top gaining and top losing Indian stocks as one JSON object. The request takes no parameters, and no exchange, count or sector filter is documented. The body has a single trending_stocks container with two arrays, top_gainers and top_losers. Observed in a live probe (HTTP 200): each array held 10 rows, every value inside a row was a string, and the rows in a list shared the same keys: ticker_id, company_name, price, percent_change, net_change, open, high, low, close, bid, ask, bid_size, ask_size, volume, low_circuit_limit, up_circuit_limit, year_low, year_high, date, time, lot_size, exchange_type, ric, overall_rating, short_term_trends, long_term_trends and total_share_outstanding. In that probe every row had exchange_type NSI and a ric ending in .NS, top_gainers started with the largest positive percent_change, top_losers started with the most negative one, and the trend fields carried labels such as Bullish, Moderately Bullish, Neutral, Moderately Bearish and Bearish. The documentation differs from the probe in three ways that should be treated as unverified: it says each list has the top 3 stocks, its sample rows are BSE rows with ric values ending in .BO, and it lists the extra fields average_price, average_volume, deviation, actual_deviation and no_of_days_for_average, which did not appear in the probed rows. The documentation also says null values are removed from the response, so optional fields may be absent. The data is an informational market snapshot, not an execution or licensed tick feed.
Request cost is temporarily unavailable. No price is assumed.