/bseindia/companies

POST /api/bseindia/companies

Price: 1 credit

Get a BSE-listed security by scrip code: name, security id, ISIN, group, index, face value, settlement type, sector and industry classification, standalone and consolidated EPS, P/E, P/B, ROE and margins, and the latest price, change and day range, and the NAV for ETFs

How to use it

Find a scrip code with bseindia/companies/search. Money values are in Indian rupees.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• scrip_code string required — BSE scrip code or quote page URL (examples: "500325", "https://www.bseindia.com/stock-share-price/reliance-industries-ltd/RELIANCE/500325/")

Response

• @type string (default: "BseindiaCompany")
• scrip_code string required
• security_id string nullable
• name string nullable
• url string nullable
• isin string nullable
• category string nullable
• group string nullable
• index string nullable
• face_value number nullable
• settlement_type string nullable
• sector string nullable
• industry_group string nullable
• industry string nullable
• sub_industry string nullable
• eps number nullable
• cash_eps number nullable
• pe number nullable
• pb number nullable
• roe number nullable
• operating_margin number nullable
• net_margin number nullable
• consolidated_eps number nullable
• consolidated_cash_eps number nullable
• consolidated_pe number nullable
• consolidated_pb number nullable
• consolidated_roe number nullable
• consolidated_operating_margin number nullable
• consolidated_net_margin number nullable
• last_price number nullable
• change number nullable
• change_percent number nullable
• previous_close number nullable
• open number nullable
• high number nullable
• low number nullable
• price_as_of integer nullable
• nav number nullable
• nav_as_of integer 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 BSE-listed security under that scrip code 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.