/nseindia/indices/constituents

POST /api/nseindia/indices/constituents

Price: 10 credits

List the member stocks of an NSE index with the latest session's quote: last price, change, open, high, low, previous close, 52-week range, traded volume and value, free-float market cap and 30-day and 1-year change

How to use it

Index names come from nseindia/indices.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• index string required — NSE index name (examples: "NIFTY 50", "NIFTY BANK"; minLength: 2)
• count integer required — Max number of constituents to return (min: 1; max: 1000)

Response

• @type string (default: "NseindiaConstituent")
• symbol string required
• index_name string required
• series string nullable
• last_price number nullable
• change number nullable
• change_percent number nullable
• open number nullable
• day_high number nullable
• day_low number nullable
• previous_close number nullable
• year_high number nullable
• year_low number nullable
• traded_volume number nullable
• traded_value number nullable
• free_float_market_cap number nullable
• change_percent_30d number nullable
• change_percent_365d number nullable
• percent_from_year_high number nullable
• percent_from_year_low 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 — No NSE index under that name 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.