APAC IPO Calendar Sweep — Pan-Asia New Listings API
Pricing
from $50.00 / 1,000 ipos
APAC IPO Calendar Sweep — Pan-Asia New Listings API
Monitor Asia-Pacific IPOs across 10+ markets in one call — clean JSON for analysts and AI agents.
APAC IPO Calendar Sweep — Pan-Asia New Listings API
Pricing
from $50.00 / 1,000 ipos
Monitor Asia-Pacific IPOs across 10+ markets in one call — clean JSON for analysts and AI agents.
You can access the APAC IPO Calendar Sweep — Pan-Asia New Listings API programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in API & Integrations in Apify Console.
{ "openapi": "3.0.1", "info": { "version": "0.0", "x-build-id": "08RGZbnZrDwOYSSlY" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/nexgendata~apac-ipo-calendar-sweep/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-nexgendata-apac-ipo-calendar-sweep", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for its completion, and returns Actor's dataset items in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } }, "/acts/nexgendata~apac-ipo-calendar-sweep/runs": { "post": { "operationId": "runs-sync-nexgendata-apac-ipo-calendar-sweep", "x-openai-isConsequential": false, "summary": "Executes an Actor and returns information about the initiated run in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/runsResponseSchema" } } } } } } }, "/acts/nexgendata~apac-ipo-calendar-sweep/run-sync": { "post": { "operationId": "run-sync-nexgendata-apac-ipo-calendar-sweep", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for completion, and returns the OUTPUT from Key-value store in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } } }, "components": { "schemas": { "inputSchema": { "type": "object", "properties": { "exchanges": { "title": "Exchanges to fetch live", "type": "array", "description": "Which APAC exchanges to fetch LIVE this run. Default = all live-supported exchanges: HK (HKEX), SG (SGX), TW (TWSE), IN (NSE India), JP (TSE Japan). Each is fetched directly from the exchange's own public disclosure backend on every run and tagged with a real source_url. NOTE: KR/ID/MY/TH/VN/PH are NOT covered live by this aggregator (their portals are bot-walled or have no open API) — selecting them has no effect; use the dedicated country-specific NexGenData actors for those markets.", "items": { "type": "string", "enum": [ "HK", "SG", "TW", "IN", "JP" ], "enumTitles": [ "Hong Kong (HKEX)", "Singapore (SGX)", "Taiwan (TWSE)", "India (NSE)", "Japan (TSE)" ] }, "default": [ "HK", "SG", "TW", "IN", "JP" ] }, "country": { "title": "Country / region filter (legacy)", "enum": [ "ALL", "ASEAN", "HK", "SG", "TW", "IN", "JP", "KR", "ID", "MY", "TH", "VN", "PH" ], "type": "string", "description": "Legacy single-market filter, kept for backward compatibility. Prefer the 'exchanges' input. 'ALL' fetches every live-supported exchange (HK, SG, TW, IN, JP). 'ASEAN' resolves to SG only (the only ASEAN market covered live). An ISO-2 code drills into one supported jurisdiction. Codes for exchanges not covered live (KR/ID/MY/TH/VN/PH) return no rows by design — this actor never fabricates curated data for unreachable exchanges.", "default": "ALL" }, "status": { "title": "Listing-pipeline status", "enum": [ "all", "proof", "approved", "listed" ], "type": "string", "description": "Which slice of the IPO lifecycle to return. 'proof' = early-stage / upcoming filings (HKEX Application Proof, NSE forthcoming issue, JPX approved new listing, TWSE applied-not-yet-listed). 'approved' = book-build / pricing-stage (HKEX PHIP, NSE active/closed issue). 'listed' = already-trading recent IPOs (SGX performance feed, HKEX listed feed, TWSE with a listing date). 'all' (default) = full lifecycle. Status semantics are normalised across exchanges from the live source data — never inferred or fabricated.", "default": "all" }, "lookbackDays": { "title": "Lookback window (days, for already-listed rows)", "minimum": 1, "maximum": 1825, "type": "integer", "description": "How many days of already-trading recent IPOs (dated rows) to include. Default 90 = the recent quarter. Applies to rows that carry a real listing date in the past (e.g. SGX performance feed, HKEX/TWSE listed entries).", "default": 90 }, "lookaheadDays": { "title": "Lookahead window (days, for forward pipeline rows)", "minimum": 1, "maximum": 730, "type": "integer", "description": "How many days of forward pipeline (dated upcoming rows) to include. Default 90 = next-quarter pipeline. Applies to rows carrying a real future date (e.g. JPX approved listing dates, NSE issue close dates). Undated pipeline rows (e.g. HKEX Application Proofs without a fixed listing date) are included when status is all/proof/approved.", "default": 90 }, "limit": { "title": "Max IPO records returned", "minimum": 1, "maximum": 500, "type": "integer", "description": "Hard cap on total IPO records returned (1-500). Each IPO is one dataset row and one billed item. Records are sorted upcoming-first by date ascending, then recently-listed by date descending.", "default": 50 } } }, "runsResponseSchema": { "type": "object", "properties": { "data": { "type": "object", "properties": { "id": { "type": "string" }, "actId": { "type": "string" }, "userId": { "type": "string" }, "startedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "finishedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "status": { "type": "string", "example": "READY" }, "meta": { "type": "object", "properties": { "origin": { "type": "string", "example": "API" }, "userAgent": { "type": "string" } } }, "stats": { "type": "object", "properties": { "inputBodyLen": { "type": "integer", "example": 2000 }, "rebootCount": { "type": "integer", "example": 0 }, "restartCount": { "type": "integer", "example": 0 }, "resurrectCount": { "type": "integer", "example": 0 }, "computeUnits": { "type": "integer", "example": 0 } } }, "options": { "type": "object", "properties": { "build": { "type": "string", "example": "latest" }, "timeoutSecs": { "type": "integer", "example": 300 }, "memoryMbytes": { "type": "integer", "example": 1024 }, "diskMbytes": { "type": "integer", "example": 2048 } } }, "buildId": { "type": "string" }, "defaultKeyValueStoreId": { "type": "string" }, "defaultDatasetId": { "type": "string" }, "defaultRequestQueueId": { "type": "string" }, "buildNumber": { "type": "string", "example": "1.0.0" }, "containerUrl": { "type": "string" }, "usage": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "integer", "example": 1 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 }, "PROXY_UNBLOCKER_UNITS": { "type": "integer", "example": 0 } } }, "usageTotalUsd": { "type": "number", "example": 0.00005 }, "usageUsd": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "number", "example": 0.00005 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 }, "PROXY_UNBLOCKER_UNITS": { "type": "integer", "example": 0 } } } } } } } } }}OpenAPI is a standard for designing and describing RESTful APIs, allowing developers to define API structure, endpoints, and data formats in a machine-readable way. It simplifies API development, integration, and documentation.
OpenAPI is effective when used with AI agents and GPTs by standardizing how these systems interact with various APIs, for reliable integrations and efficient communication.
By defining machine-readable API specifications, OpenAPI allows AI models like GPTs to understand and use varied data sources, improving accuracy. This accelerates development, reduces errors, and provides context-aware responses, making OpenAPI a core component for AI applications.
You can download the OpenAPI definitions for APAC IPO Calendar Sweep — Pan-Asia New Listings API from the options below:
If you’d like to learn more about how OpenAPI powers GPTs, read our blog post.
You can also check out our other API clients: