/moneycontrol/stocks/corporate_actions

POST /api/moneycontrol/stocks/corporate_actions

Price: 5 credits

Get an Indian listed company's corporate actions from Moneycontrol: exchange announcements with summary and filing link, board meetings, dividends with amount and ex-date, bonus issues, stock splits, rights issues and AGM/EGM dates

How to use it

An empty list means the company has no actions of that type on record.

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")
• action_type string required — Kind of corporate action (one of: "announcements", "board_meetings", "dividends", "bonus", "splits", "rights", "agm_egm")
• count integer required — Max number of results, newest first (min: 1; max: 500)

Response

• @type string (default: "MoneycontrolCorporateAction")
• stock_id string required
• action_type string required
• id string nullable
• summary string nullable
• text string nullable
• source string nullable
• url string nullable
• attachment_url string nullable
• published_at integer nullable
• announcement_date integer nullable
• event_date integer nullable
• ex_date integer nullable
• record_date integer nullable
• book_closure_start_date integer nullable
• book_closure_end_date integer nullable
• dividend_type string nullable
• dividend_amount number nullable
• dividend_percent number nullable
• ratio string nullable
• old_face_value number nullable
• new_face_value number nullable
• face_value number nullable
• premium number nullable
• ex_price number nullable
• remarks string 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 stock under that 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.