APAC IPO Calendar Sweep — Pan-Asia New Listings (Live, 5 Exchanges)

The Asian IPO pipeline from five exchanges in one pull — fetched live, never curated. APAC IPO Calendar Sweep pulls the IPO pipeline and recent listings across Hong Kong, Singapore, Taiwan, India and Japan directly from each exchange's own public disclosure backend on every run, with a real source_url / prospectus_url on every row. It does not ship a curated or hardcoded database, it is not a fabricated forward subscription calendar, and it never invents dates, prices or proceeds — you get exactly what each exchange publishes.

Live coverage (what this actor actually fetches)

Exchange	Code	Live source backend	What you get
Hong Kong — HKEX	HK	HKEXnews application-proof JSON feeds (appactive_app, appactive_appphip, applisted)	Active Main Board applicants (Application Proof), PHIP-stage deals, and recently listed names with stock codes — each with real per-document PDF URLs on www1.hkexnews.hk
Singapore — SGX	SG	SGX ipoperformance + ipoprospectus JSON APIs	Recently listed IPOs (offer price, market segment, issue manager, performance) and the lodged-prospectus register — real links.sgx.com document URLs
Taiwan — TWSE	TW	TWSE OpenAPI company/newlisting	New + pipeline listings with application / committee / approval / listing dates, underwriter and underwriting price
India — NSE	IN	NSE all-upcoming-issues JSON API	Forthcoming / active / closed issues with price band, issue size and open/close dates
Japan — TSE	JP	JPX new-listing notice page (server-rendered table)	Approved upcoming listings with listing date, code, market segment, price band and shares offered

Not covered live (deliberately omitted — never back-filled with curated data)

These exchanges are not fetched because their portals are bot-walled or expose no clean public IPO API. Rather than fabricate or hardcode rows, this actor simply omits them:

• Korea (KRX KIND) — serves a JavaScript shell with no clean public JSON
• Indonesia (IDX) — behind Cloudflare bot protection
• Malaysia (Bursa) — behind Cloudflare bot protection
• Thailand (SET) — behind Incapsula bot protection
• Vietnam (HOSE) — no open public IPO API
• Philippines (PSE) — openApi is not openly queryable without registration

Use cases

• APAC equity research / ECM — one comparable view of the new-listing pipeline and recent listings across five Asian primary markets, each row carrying the real exchange document URL.
• Cross-border investors — stagger primary-allocation work by watching the forward pipeline (HK Application Proof / PHIP, TW committee dates, IN price bands, JP approved listings) in a single dataset.
• Compliance / allocators — screen by exchange and listing status before book close, using only source-published fields (no invented figures).
• Offshore-China watcher — track HK applicants alongside the wider Asian calendar without paying for global coverage you don't need.

Input

• exchanges (array, default ["HK","SG","TW","IN","JP"]) — which live-supported exchanges to fetch. Selecting an unsupported code has no effect.
• country (string, legacy) — single-market filter; ALL, ASEAN (→ SG only), or a supported ISO-2 code.
• status (string) — all / proof (upcoming/early filings) / approved (book-build / pricing) / listed (already trading).
• lookbackDays (int, default 90) — window for already-listed dated rows.
• lookaheadDays (int, default 90) — window for forward-dated pipeline rows.
• limit (int, default 50) — max rows returned (each row = one billed item).

Output (per row)

Only fields the live source actually provides are populated; everything else is null.

• country, country_iso, exchange
• company_name, stock_code
• listing_status (Upcoming / Pricing / Trading), filing_stage
• filing_date, issue_open_date, issue_date, listing_date (ISO-8601)
• offer_price, offer_price_range, currency, shares_offered
• market_segment, issuer_manager, sponsors
• business_description
• prospectus_url / source_url — the real exchange document / endpoint this row was fetched from
• data_source

Sample input

{
  "exchanges": ["HK", "SG", "TW", "IN", "JP"],
  "status": "all",
  "lookbackDays": 90,
  "lookaheadDays": 90,
  "limit": 100
}

FAQ

Which markets are covered live? Hong Kong (HKEX), Singapore (SGX), Taiwan (TWSE), India (NSE) and Japan (TSE) — fetched directly from each exchange's public backend on every run.

Is the data scraped live or curated? Live. Every row is fetched at request time and tagged with the real source_url / prospectus_url; there is no hardcoded or curated database.

Why aren't Korea, Indonesia, Malaysia, Thailand, Vietnam or the Philippines included? Their portals are bot-walled or have no clean public IPO API. Rather than fabricate rows, the actor omits them and reports which exchanges were attempted in a STATUS record.

Do rows include offer price, proceeds, sponsors or cornerstones? Only when the live source publishes them. Fields the source does not provide are returned as null — nothing is invented.

How is this different from the HK-only calendar? This is the pan-APAC sweep across five markets; hkex-ipo-calendar is the Hong-Kong-specific feed.

Billing

Pay-per-event: a small actor-start charge plus one charge per IPO row returned. If a run matches no rows, no per-row charge is incurred — a STATUS record is written to the run's key-value store listing which exchanges were attempted, which returned rows, and which are not covered live.

Related actors — APAC Disclosure family

• hkex-ipo-calendar
• apac-disclosure-monitor
• hkex-news-announcements
• hkex-insider-short-tracker