POST /api/nseindia/companies/insider_trades
Price: 20 credits
List insider trading disclosures (SEBI PIT) filed on NSE for one company: person and category, security type, buy or sell, mode, quantity and value, holdings before and after, derivative legs, transaction and intimation dates and the XBRL filing link
Newest disclosures first. Without dates it returns the company's full disclosure history.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)symbol string required — NSE trading symbol or quote page URL (examples: "RELIANCE", "https://www.nseindia.com/get-quotes/equity?symbol=TCS")date_from integer nullable — Earliest disclosure day, as unix seconds; day-granular (examples: 1767225600)date_to integer nullable — Latest disclosure day, as unix seconds; day-granular (examples: 1790812800)count integer required — Max number of trades to return (min: 1; max: 5000)@type string (default: "NseindiaInsiderTrade")id string requiredfiling_id string nullablesymbol string nullablecompany_name string nullableperson_name string nullableperson_category string nullableregulation string nullablesecurity_type string nullablesecurity_type_after string nullabletransaction_type string nullableacquisition_mode string nullablesecurities number nullablevalue number nullableshares_before number nullablepercent_before number nullableshares_after number nullablepercent_after number nullablederivative_type string nullablederivative_contract_type string nullablebuy_quantity number nullablebuy_value number nullablesell_quantity number nullablesell_value number nullableexchange string nullabletransaction_start_date integer nullabletransaction_end_date integer nullableintimation_date integer nullabledisclosed_at integer nullableremarks string nullablexbrl_url string nullable422 — date_to is before date_from or an invalid symbol 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.