/moneycontrol/stocks/forecast

POST /api/moneycontrol/stocks/forecast

Price: 1 credit

Get analyst estimates for an Indian listed stock from Moneycontrol: consensus rating, analyst count, high, mean and low target price, the share of each rating, the monthly rating breakdown and the year of share prices the target is charted against

How to use it

Target prices are in rupees; rating_shares are percentages of covering analysts.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• stock string required — Moneycontrol stock id or moneycontrol.com stock page URL (examples: "RI", "HDF01", "https://www.moneycontrol.com/india/stockpricequote/refineries/relianceindustries/RI")

Response

• @type string (default: "MoneycontrolForecast")
• stock_id string required
• rating string nullable
• analyst_count integer nullable
• target_price_high number nullable
• target_price_mean number nullable
• target_price_low number nullable
• rating_shares array (default: [])
  • @type string (default: "MoneycontrolRatingShare")
  • rating string required
  • percent number nullable
• consensus_history array (default: [])
  • @type string (default: "MoneycontrolConsensusMonth")
  • month string required
  • rating string required
  • analyst_count integer nullable
• price_history array (default: [])
  • @type string (default: "MoneycontrolPricePoint")
  • date integer required
  • price number nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Moneycontrol has no analyst coverage for that stock id Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.