Get upcoming, active, closed and listed Indian IPOs with price band, lot size, SME flag, bidding dates and listing details

View all Indian Stock Exchange API endpoints →

Returns the Indian IPO feed with no input parameters. The endpoint documentation describes it as the latest upcoming, listed, active and closed IPO data. No probe call was made for this endpoint, so the response details come from a truncated, unverified source example dated September 2024. In that example the response is a JSON object whose keys are status groups, with active and closed arrays visible, and each array item is an issue object with name, symbol, status, is_sme, min_price, max_price, issue_price, lot_size, bidding_start_date, bidding_end_date, listing_date, listing_price, listing_gains, additional_text and document_url. Dates are ISO YYYY-MM-DD strings. In the sampled active rows the bidding dates, price band, lot size and a status note such as IPO closes today at 4:50 PM were filled, while issue_price, listing_date, listing_price, listing_gains and document_url were null. The sampled closed rows carried a listing_date and a document_url, with bidding_end_date and lot_size null. Whether upcoming and listed groups use those exact keys, how fields fill as an issue moves between states, and any limit on list size are unverified. The data is informational and does not support applying for or bidding in an issue.

API Features

Issues grouped by IPO status The documentation covers upcoming, listed, active and closed IPOs. The source example groups issues into arrays by status, and every row also repeats its own status field.
Price band and lot size per issue Each issue row has min_price and max_price for the price band and a lot_size, so a calendar can show the minimum application amount without a second lookup.
SME flag on every row The boolean is_sme separates SME-platform issues from mainboard issues, which lets a client build two lanes or hide one segment entirely.
Bidding window and listing dates bidding_start_date, bidding_end_date and listing_date are ISO date strings in the source example, ready for sorting, week filters and countdown timers.
Listing outcome fields issue_price, listing_price and listing_gains are part of each row. They were null for the sampled active rows, so a gain tracker should expect them to fill only after listing.
Status note and prospectus link additional_text carries short notes such as when bidding closes or when listing happens, and document_url held a prospectus link on the sampled closed rows.
Whole feed in one request There are no inputs, so one call returns every status group at once, which keeps a scheduled IPO sync to a single request per run.

Live API Demo

GET /api/project/indian-stock-exchange-api/ipo

No parameters required. Click Query to call the API.

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/indian-stock-exchange-api/ipo?key=<API_KEY>'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

What does the IPO endpoint return?

A JSON object of IPO issues grouped by status. The supplied source example shows active and closed arrays, and each issue has name, symbol, status, is_sme, min_price, max_price, issue_price, lot_size, bidding_start_date, bidding_end_date, listing_date, listing_price, listing_gains, additional_text and document_url.

Does it need any parameters?

No. The IPO endpoint has no query, path or body parameters, so a plain GET returns the whole feed.

Which IPO statuses are covered?

The endpoint documentation names upcoming, listed, active and closed IPO data. The truncated source example only shows the active and closed arrays, so confirm the exact keys for upcoming and listed groups in a live response.

Has this endpoint been tested with a live call?

No probe call was made for the IPO endpoint. The field list comes from a source example dated September 2024, so verify field names, null handling and list sizes against a current response before depending on them.

How do I tell SME issues from mainboard issues?

Use the is_sme boolean on each issue. In the source example it was true for the SME rows and false for a mainboard row such as Manba Finance.

Are listing prices and gains included?

The fields listing_price and listing_gains exist on each row, but they were null in the sampled active and closed rows. Whether they are filled for the listed group is unverified, so treat null as not available yet.

Can I use it to apply for an IPO or get allotment status?

No. It returns informational issue data only. The example fields do not include subscription levels, grey market premium or allotment results, and the endpoint does not place bids.

Related operations

Guides

View Subscription Plans →