/moneycontrol/markets/movers

POST /api/moneycontrol/markets/movers

Price: 1 credit

Get Indian market movers from Moneycontrol for NSE or BSE: top gainers and losers, only buyers and sellers, 52-week highs and lows, price and volume shockers and most active stocks, with price, change, OHLC, VWAP, volume against its average, traded value, market cap and one- and three-month returns

How to use it

market_cap and traded_value are in INR crores; symbol is the NSE ticker on NSE and the BSE code on BSE. Feed a stock_id to moneycontrol/stocks for the full quote.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• category string required — Market statistics list (one of: "top-gainers", "top-losers", "only-buyers", "only-sellers", "52-week-high", "52-week-low", "price-shockers", "volume-shockers", "most-active-stocks")
• exchange string — Exchange (default: "nse"; one of: "nse", "bse")
• index_id string nullable — Moneycontrol index id to rank within; NIFTY 50 or SENSEX by default (examples: "7", "9")
• count integer required — Max number of stocks (min: 1; max: 500)

Response

• @type string (default: "MoneycontrolMover")
• rank integer required
• category string required
• exchange string required
• stock_id string required
• name string nullable
• symbol string nullable
• instrument_type string nullable
• url string nullable
• price number nullable
• change number nullable
• change_percent number nullable
• open number nullable
• high number nullable
• low number nullable
• previous_close number nullable
• vwap number nullable
• volume number nullable
• average_volume number nullable
• volume_multiplier number nullable
• volume_change_percent number nullable
• traded_value number nullable
• market_cap number nullable
• return_1m number nullable
• return_3m 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 — The entity was not found, or a precondition failed 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.