Get Indian stock analyst estimates and reported actuals for one measure such as EPS, filtered by period type, data type and data age.

View all Indian Stock Exchange API endpoints →

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.

API Features

Fifteen selectable measure codes measure_code takes EPS, CPS, CPX, DPS, EBI, EBT, GPS, GRM, NAV, NDT, NET, PRE, ROA, ROE or SAL, so one route covers earnings per share, dividends per share and a dozen other forecast lines.
Actuals and estimates on one route data_type switches between Actuals and Estimates for the same stock and measure, which lets you pair what analysts expected with what the company reported using two identical calls.
Annual or interim fiscal periods period_type selects Annual or Interim, and every period in the response carries a FiscalPeriod (Type and Year), a RelativePeriod (Number and Type), CalendarMonth and CalendarYear for aligning rows.
Five data ages for revision tracking age accepts Current, OneWeekAgo, ThirtyDaysAgo, SixtyDaysAgo and NinetyDaysAgo, giving earlier readings of the same data so the Current value can be compared with the 90-day-old one.
Surprise statistics on reported actuals The Actuals sample rows include Reported, SurpriseMean, SurprisePercent, StandardizedUnexpectedEarnings and NumberOfEstimates, which describe how a reported figure compared with analyst expectations.
Report dates and currency on every period Each period exposes ActualReportDate and each actual row has ReportedDate and CurrencyCode (INR in the sample), so timing and units are explicit instead of implied.

Live API Demo

GET /api/project/indian-stock-exchange-api/stock-forecasts

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
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'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

Which values can each parameter take?

measure_code accepts EPS, CPS, CPX, DPS, EBI, EBT, GPS, GRM, NAV, NDT, NET, PRE, ROA, ROE and SAL. period_type is Annual or Interim, data_type is Actuals or Estimates, and age is Current, OneWeekAgo, ThirtyDaysAgo, SixtyDaysAgo or NinetyDaysAgo. stock_id is a free string whose documented example is TCS. All five parameters are required.

Why does the form prefill a long comma-separated value?

The catalog prefill lists every accepted name for age, data_type, measure_code and period_type. The documented sample request sends one value for each, for example EPS, Annual, Actuals and ThirtyDaysAgo. The evidence does not say whether the service accepts a comma-separated list, and this endpoint has not been probed live, so replace the prefilled lists with single values.

What does the response look like?

The stored documentation sample is an object with measureCode, measureName and a periods array. Each period has ActualReportDate, CalendarMonth, CalendarYear, FiscalPeriod and RelativePeriod, and in the Actuals sample an Actuals.Actual list with Reported, NumberOfEstimates, SurpriseMean, SurprisePercent and related fields. This comes from the sample, not from a live probe.

Does the sample show Estimates data?

No. The supplied sample is an Actuals response for the EPS measure. The layout returned for data_type=Estimates is not shown in the evidence, so inspect a real Estimates response before writing a parser that depends on specific field names.

What do the age values mean?

The documentation describes age only as the age of the data to be retrieved, with the options Current and one week, 30, 60 and 90 days ago. It is natural to read them as earlier readings of the same data for comparing how a figure changed, but the exact snapshot semantics are not spelled out.

What do the measure codes other than EPS and DPS stand for?

The documentation labels only EPS as earnings per share and DPS as dividends per share. The remaining codes are listed without descriptions, and in the EPS sample measureName simply repeats the code. Confirm what a code measures by checking its measureName and values for a stock you know before relying on it.

What errors can I expect?

The documentation lists 200 for matching forecast data, 404 when no forecasts can be found for the stock_id or measure code, and 500 for an unexpected processing error. Handle 404 as a normal no-data outcome, because not every stock is likely to have every measure.

Can I use these forecasts for trading decisions?

Treat them as informational analyst data for research, dashboards and screens. Estimates and surprise figures are snapshots that can be revised, so confirm important numbers with the company filings or a licensed data source before acting on them.

Related operations

Guides

View Subscription Plans →