πŸ“Š

Indian Stock Exchange API

Look up Indian listed companies by name, then compare NSE and BSE market lists, read price history and corporate actions, and check analyst views, IPOs, mutual funds and MCX futures. Read-only research data, not brokerage execution, investment advice or a licensed tick feed.

Open the standalone Indian stock demo

Look up a company record by name

Replace <API_KEY> with your authorized platform API key from the dashboard. The request URL contains your key, so keep it out of shared links, screenshots, source control and logs, and make production calls server-side.

The example calls the company lookup with name=tata steel, a full, shortened or common company name rather than a ticker. Check the returned company name and exchange codes before reusing them, because the documentation does not say how ambiguous or unmatched names are handled. Prices, financials and news change over time, so a populated response is not guaranteed. Opening this page, switching endpoints, expanding panels or copying the example sends no data request; a call is made only when you choose to run it.

Base URL https://api.opendata-api.com

curl -X GET 'https://api.opendata-api.com/api/project/indian-stock-exchange-api/get-stock-data-by-name?key=<API_KEY>&name=tata+steel'
Company names, stock identifiers and selector values
  • Identifiers are not interchangeable: the stock record lookup uses name, history, statistics and corporate actions use stock_name, forecasts and ratings use stock_id, and the searches use query. Spelling, letter case and the handling of ambiguous or unmatched names are not fully documented, so check the returned company name, NSE code and BSE code before reusing them in the next step.
  • Send one value per selector. period, filter, measure_code, period_type, data_type and age each take a single documented name, and the full list prefilled in a form only shows the options, not a value to send together. stats can combine several statistic groups with commas. Data age, history window, reporting period and your request time are different clocks, so record them separately.
  • An empty 52-week list while the market is closed, or a corporate-action section that reports no announcement, is a result and not a reason to retry. Judge the HTTP status, the gateway's code and message, and the empty or no-record content inside data as separate layers. Treat a missing field as unknown, not as zero.

Check status and message before reading market data

Read the HTTP status separately from the gateway's code, message and data business result. Gateway code 200 means business success, but HTTP 200 alone does not prove usable data. Inside data, a list can be empty (the 52-week list is documented to come back empty while the market is closed) and a corporate-action section can report no announcement. Keep a failed request, an empty list and a populated list as three different states.

Choose the research task before entering identifiers
Look up a company and find its codes

The stock record lookup takes one required name, which can be a full, shortened or common company name, and returns BSE and NSE prices, financials, key metrics and recent news. The search operation takes one required query and returns matching stocks and funds with their exchange codes, so use it when you need a code you do not already hold. Check the returned company name and codes before passing them to another operation.

Compare the market lists

Five lists need no inputs but answer different questions: BSE and NSE most-active rank volume per exchange, trending nests top gainers and top losers, price shockers flag sudden moves, and the 52-week list shows yearly highs and lows. The most-active and trending lists were checked live and returned ten rows per list; the price shocker and 52-week shapes are documented but not verified against a live response, and the 52-week list is documented to come back empty when the market is closed. Save each list separately with your own request time instead of treating them as one ranking.

Read history, statistics and corporate actions

All three operations require stock_name. History adds optional period and filter selectors, statistics adds an optional stats list of statistic groups, and corporate actions takes no other input. Send one selector value at a time, and keep the five corporate-action sections separate because a section can report that nothing was announced.

Read forecasts and analyst ratings

Both operations require a stock_id, and the documentation does not list every accepted form, so verify an identifier before building on it. Analyst recommendations need only that identifier. Forecasts also require measure_code, period_type, data_type and age, and each must be a single documented value.

Browse mutual funds, IPOs and commodity futures

Mutual fund search requires one query, a fragment of a scheme name. The fund overview, the IPO feed and the commodity futures snapshot take no inputs. The IPO and futures shapes are documented but not verified against a live response, so parse them defensively and keep issue status groups and contract months distinct.

Market Movers

GET /api/project/indian-stock-exchange-api/bse-most-active

BSE Most Active Stocks by Trading Volume

Full docs β†’
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.

Explicitly send this Indian stock request 0 required Β· 0 optional

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/indian-stock-exchange-api/bse-most-active?key=<API_KEY>'
GET /api/project/indian-stock-exchange-api/nse-most-active

NSE Most Active Stocks by Trading Volume

Full docs β†’
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.

Explicitly send this Indian stock request 0 required Β· 0 optional

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/indian-stock-exchange-api/nse-most-active?key=<API_KEY>'
GET /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

Full docs β†’
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.

Explicitly send this Indian stock request 0 required Β· 0 optional

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/indian-stock-exchange-api/fetch-52-week-high-low-data?key=<API_KEY>'
GET /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.

Full docs β†’
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.

Explicitly send this Indian stock request 0 required Β· 0 optional

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/indian-stock-exchange-api/price-shockers?key=<API_KEY>'

Commodity Futures

GET /api/project/indian-stock-exchange-api/commodity-futures-data-api

Active Commodity Futures Contracts Snapshot

Full docs β†’
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.

Explicitly send this Indian stock request 0 required Β· 0 optional

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/indian-stock-exchange-api/commodity-futures-data-api?key=<API_KEY>'

Corporate Actions

GET /api/project/indian-stock-exchange-api/corporate-actions

Get dividends, splits, bonus issues, rights and board meetings for an Indian listed company by name

Full docs β†’
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.

Explicitly send this Indian stock request 1 required Β· 0 optional
ParameterInValue
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/indian-stock-exchange-api/corporate-actions?key=<API_KEY>&stock_name=infosys'

Historical Data

GET /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

Full docs β†’
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.

Explicitly send this Indian stock request 1 required Β· 2 optional
ParameterInValue
query
query
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/indian-stock-exchange-api/historical-data?key=<API_KEY>&filter=default&period=5yr&stock_name=tcs'
GET /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

Full docs β†’
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.

Explicitly send this Indian stock request 1 required Β· 1 optional
ParameterInValue
query
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/indian-stock-exchange-api/historical-stats?key=<API_KEY>&stats=quarter_results%2Cyoy_results%2Cbalancesheet%2Ccashflow%2Cratios%2Cshareholding_pattern_quarterly%2Cshareholding_pattern_yearly&stock_name=TCS'

IPO

GET /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

Full docs β†’
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.

Explicitly send this Indian stock request 0 required Β· 0 optional

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/indian-stock-exchange-api/ipo?key=<API_KEY>'

Mutual Funds

GET /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.

Full docs β†’
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.

Explicitly send this Indian stock request 0 required Β· 0 optional

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/indian-stock-exchange-api/mutual-funds?key=<API_KEY>'

Stock Data

GET /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.

Full docs β†’
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.

Explicitly send this Indian stock request 1 required Β· 0 optional
ParameterInValue
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/indian-stock-exchange-api/get-stock-data-by-name?key=<API_KEY>&name=tata+steel'

Analyst Forecasts

GET /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.

Full docs β†’
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.

Explicitly send this Indian stock request 5 required Β· 0 optional
ParameterInValue
query
query
query
query
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/indian-stock-exchange-api/stock-forecasts?key=<API_KEY>&age=Current%2COneWeekAgo%2CThirtyDaysAgo%2CSixtyDaysAgo%2CNinetyDaysAgo&data_type=Actuals%2CEstimates&measure_code=EPS%2CCPS%2CCPX%2CDPS%2CEBI%2CEBT%2CGPS%2CGRM%2CNAV%2CNDT%2CNET%2CPRE%2CROA%2CROE%2CSAL&period_type=Annual%2CInterim&stock_id=TCS'
GET /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.

Full docs β†’
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.

Explicitly send this Indian stock request 1 required Β· 0 optional
ParameterInValue
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/indian-stock-exchange-api/analyst-recommendations?key=<API_KEY>&stock_id=TCS'

Company lookup, market lists, history, corporate actions, analyst research, funds, IPOs and MCX futures

Indian stock market data by company name: BSE and NSE prices, fundamentals, market movers, history, analyst research, IPOs, mutual funds and MCX commodity futures from one JSON API.

  • Look up a full stock record by company name with BSE and NSE prices, financials, key metrics, analyst view, shareholding and recent news.
  • Rank the market with BSE and NSE most-active lists, top gainers and losers, price shockers and 52-week highs and lows.
  • Pull price history with moving averages and volume, plus quarterly and yearly results, balance sheet, cash flow, ratios and shareholding history.
  • Read analyst price targets, buy-to-sell consensus and estimates against reported actuals.
  • Keep dividends, splits, bonus issues, rights and board meetings as separate corporate-action sections.
  • Search stocks and mutual fund schemes by name, browse fund NAV and returns by category, and follow IPO status groups and commodity futures contracts.

Read-only market information for dashboards, alert bots, spreadsheets and research tools; not brokerage execution, investment advice or a licensed tick feed. Check response dates, units and identifiers before analysis.

Guides