POST /api/nseindia/financial_results/search
Price: 20 credits
Search financial result filings on NSE by company symbol, filing window, reporting period and market segment: the period covered, fiscal year, audited, consolidated and cumulative flags, accounting standard, filing times, and the XBRL and detailed-results links
With symbol and no dates it returns every filing of the company for the period; without symbol the window defaults to the last 30 days. A date_to alone ends the window; a window with no filings returns an empty list.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)symbol string nullable — NSE trading symbol of one company (examples: "RELIANCE", "INFY")date_from integer nullable — Earliest day, as unix seconds; day-granular (examples: 1788220800)date_to integer nullable — Latest day, as unix seconds; day-granular (examples: 1790812800)period string — Reporting period of the results (default: "quarterly"; one of: "quarterly", "half_yearly", "annual")segment string — Market segment of the issuers (default: "equities"; one of: "equities", "sme", "debt", "mutual_funds", "invits_reits", "municipal_bonds", "social_stock_exchange")count integer required — Max number of result filings to return (min: 1; max: 5000)@type string (default: "NseindiaFinancialResult")id string requiredsymbol string nullablecompany_name string nullableisin string nullableperiod string nullablerelating_to string nullableperiod_start_date integer nullableperiod_end_date integer nullablefiscal_year_start_date integer nullablefiscal_year_end_date integer nullableis_audited boolean nullableis_consolidated boolean nullableis_cumulative boolean nullableis_bank boolean nullableaccounting_standard string nullablefiling_format string nullablefiled_at integer nullablebroadcast_at integer nullabledisseminated_at integer nullablexbrl_url string nullabledetails_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.