InvestorGain APIinvestorgain.com ↗
Access live IPO Grey Market Premium data from InvestorGain. Filter upcoming/open IPOs and future close-date IPOs by GMP percentage via 2 REST endpoints.
What is the InvestorGain API?
The InvestorGain GMP API provides live IPO Grey Market Premium data through 2 endpoints, covering upcoming and open IPOs as well as IPOs with future close dates. The get_gmp_badge_filtered endpoint returns IPOs tagged Upcoming or Open, sorted by GMP percentage descending, while get_gmp_by_close_date targets IPOs whose subscription window has not yet closed. Both endpoints accept an optional min_gmp filter to narrow results to higher-premium opportunities.
curl -X GET 'https://api.parse.bot/scraper/c1d0143b-268f-4141-8b27-85b4ca0368f8/get_gmp_badge_filtered?min_gmp=0' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace investorgain-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
from parse_apis.investorgain_ipo_gmp_api import InvestorGain
client = InvestorGain()
# List upcoming or open IPOs with GMP >= 5%
for ipo in client.ipos.upcoming_or_open(min_gmp=5):
print(ipo.name, ipo.gmp_percent, ipo.badge, ipo.price, ipo.lot_size)
# List IPOs with future close dates
for ipo in client.ipos.by_close_date(min_gmp=0):
print(ipo.name, ipo.gmp_percent, ipo.close_date, ipo.open_date)
Returns IPOs with badge 'U' (Upcoming) or 'O' (Open), optionally filtered by minimum GMP percentage, sorted by GMP descending. Returns an empty array when no IPOs match the filter criteria.
| Param | Type | Description |
|---|---|---|
| min_gmp | number | Minimum GMP percentage to include. Default 0 returns all upcoming/open IPOs. |
{
"type": "object",
"fields": {
"items": "array of IPO objects with badge U or O, each containing name, gmp_percent, badge, close_date, open_date, price, lot_size, ipo_size_cr"
},
"sample": {
"data": {
"items": [
{
"name": "Horizon Reclaim (India)",
"badge": "U",
"price": "103",
"lot_size": "1200",
"open_date": "2026-06-12",
"close_date": "2026-06-16",
"gmp_percent": 40.78,
"ipo_size_cr": ""
}
]
},
"status": "success"
}
}About the InvestorGain API
Endpoints and What They Return
The API exposes two endpoints. get_gmp_badge_filtered returns IPO objects carrying badge values of U (Upcoming) or O (Open), sorted by gmp_percent in descending order. The optional min_gmp parameter sets a floor on GMP percentage — passing 0 (the default) returns all matching IPOs regardless of premium. get_gmp_by_close_date returns IPOs whose close date lies in the future, again sorted by gmp_percent descending and filtered by the same min_gmp parameter. IPOs without a recorded close date are excluded from that endpoint's results.
Response Shape
Both endpoints return a JSON object with a status field (always 'success') and a data array of IPO objects. Each IPO object carries the GMP percentage (gmp_percent) and badge classification alongside other IPO-level fields. When no IPOs satisfy the filter criteria — for example, a min_gmp threshold higher than any current premium — the data array is empty rather than an error.
Filtering and Sorting
The min_gmp input is the only filter available across both endpoints. It accepts a numeric value and acts as an inclusive lower bound on gmp_percent. Sorting is fixed: both endpoints always return results ordered highest GMP percentage first. There are no pagination parameters; all matching IPOs are returned in a single response.
The InvestorGain API is a managed, monitored endpoint for investorgain.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when investorgain.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official investorgain.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Screen upcoming and open IPOs with GMP above a set percentage threshold before subscription closes
- Build a dashboard showing only positively-rated GMP IPOs sorted by premium for retail investors
- Alert users when new IPOs with badge 'O' (Open) exceed a target GMP percentage
- Compare GMP percentages across all future-close-date IPOs to rank subscription priority
- Track which IPOs are currently open versus upcoming using the badge field
- Filter out low-GMP or zero-GMP IPOs to surface only high-interest listings
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does InvestorGain have an official developer API?+
What is the difference between `get_gmp_badge_filtered` and `get_gmp_by_close_date`?+
get_gmp_badge_filtered restricts results to IPOs whose badge is U (Upcoming) or O (Open), regardless of whether a close date is recorded. get_gmp_by_close_date uses the close date field as its filter criterion — it returns any IPO whose close date is in the future and excludes IPOs without a recorded close date entirely. In practice the result sets often overlap, but the badge-based endpoint can include IPOs that lack a close date entry.Does the API cover historical GMP data or only current live data?+
What happens if I set `min_gmp` to a value higher than any current IPO's GMP?+
data array rather than an error. The status field still reads 'success'. Your application should check the length of data before attempting to process results.Does the API expose individual IPO detail pages, subscription quotas, or allotment status?+
gmp_percent and badge classification. Per-IPO detail pages, subscription quota figures, allotment status, and registrar information are not covered by these endpoints. You can fork this API on Parse and revise it to add an endpoint pulling from individual IPO detail pages.