/moneycontrol/news/search

POST /api/moneycontrol/news/search

Price: 20 credits

Search Moneycontrol business and markets news by headline words and by the stock an article is tagged with: headline, intro, full text, URL, image, publish and update time, author, categories, tags, tagged stock ids and the AI summary

How to use it

With neither keywords nor stock it returns the latest articles across the site. Find a stock id with moneycontrol/stocks/search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keywords string nullable — Words that must all appear in the headline (examples: "reliance jio")
• stock string nullable — Moneycontrol stock id or stock page URL the article is tagged with (examples: "RI")
• count integer required — Max number of articles, newest first (min: 1; max: 1000)

Response

• @type string (default: "MoneycontrolNewsArticle")
• id string required
• description string nullable
• text string nullable
• url string nullable
• image string nullable
• published_at integer nullable
• updated_at integer nullable
• author string nullable
• byline string nullable
• author_designation string nullable
• author_organization string nullable
• agency string nullable
• post_type string nullable
• is_breaking boolean (default: false)
• categories array (default: [])
• sub_categories array (default: [])
• tags array (default: [])
• keywords array (default: [])
• stock_ids array (default: [])
• summary string nullable
• summary_points array (default: [])
• audio_url string nullable
• youtube_id 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 — 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.