AnswerPool

Withdrawn IPOs API: Registration statements withdrawn in the last N days (RW and AW — SEC EDGAR

Registration statements withdrawn in the last N days (RW and AW filings), newest first with issuer and filing links — the dead-deal list as one call. Covers all registration types, stated in the response.

$0.02 per call — pay with prepaid card credits (Authorization: Bearer ck_live_…, packs from $1) or with USDC over x402: call it, get 402 with the price, retry signed. Failed calls are never charged.

How do you call it?

GET /v1/ipo/withdrawn — product id ipo_withdrawn. Over MCP, call answerpool_get with product_id=ipo_withdrawn.

curl "https://answerpool.io/v1/ipo/withdrawn?days=60"

# with a prepaid credit key
curl -H "Authorization: Bearer ck_live_..." "https://answerpool.io/v1/ipo/withdrawn?days=60"

Live call: https://answerpool.io/v1/ipo/withdrawn?days=60 · JSON sample: /v1/samples/ipo_withdrawn

What does the answer look like?

A representative response, the same static sample served at /v1/samples/ipo_withdrawn.

as_of2026-09-02T23:00:00Z
window_days60
count1
noteRW/AW cover withdrawal of any registration statement, not only IPOs.
refresh_after2026-09-17T11:15:00.000Z

filings

accessioncikcompanytickerformfiledurl
0001437749-26-0289210001999998EXAMPLE THERAPEUTICS INCRW2026-08-20https://www.sec.gov/Archives/edgar/data/1999998/000143774926028921-index.htm
The same sample as raw JSON
{
 "as_of": "2026-09-02T23:00:00Z",
 "window_days": 60,
 "count": 1,
 "filings": [
  {
   "accession": "0001437749-26-028921",
   "cik": "0001999998",
   "company": "EXAMPLE THERAPEUTICS INC",
   "ticker": null,
   "form": "RW",
   "filed": "2026-08-20",
   "url": "https://www.sec.gov/Archives/edgar/data/1999998/000143774926028921-index.htm"
  }
 ],
 "note": "RW/AW cover withdrawal of any registration statement, not only IPOs.",
 "refresh_after": "2026-09-17T11:15:00.000Z"
}

How fresh is it, and where does the data come from?

The fastest source behind this answer can change every 15 minutes, so every response carries a refresh_after timestamp — right now it would be 2026-09-17T11:15:00.000Z. Schedule the next call on that value rather than on a guess.

Method version 0.1.0 · serving cache 1 day · every response carries a result_id you can resolve at /v1/provenance.

When should you use it?

You track failed or pulled offerings as a market signal.

What you skip building

When should you not use it?

Live pipeline state — use the calendar endpoint.

Where else can you find this?