AnswerPool

SEC Watchlist API: Get flagged SEC events for up to 25 tickers in one call — SEC EDGAR

Get flagged SEC events for up to 25 tickers in one call — 8-K items, insider trades and raises since your cursor, with a next cursor to store. Use instead of running one EDGAR poll per portfolio name.

$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/sec/watchlist — product id sec_watchlist_events. Over MCP, call answerpool_get with product_id=sec_watchlist_events.

curl "https://answerpool.io/v1/sec/watchlist?tickers=JEF%2CNVDA%2CAAPL"

# with a prepaid credit key
curl -H "Authorization: Bearer ck_live_..." "https://answerpool.io/v1/sec/watchlist?tickers=JEF%2CNVDA%2CAAPL"

Live call: https://answerpool.io/v1/sec/watchlist?tickers=JEF%2CNVDA%2CAAPL · JSON sample: /v1/samples/sec_watchlist_events

What does the answer look like?

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

as_of2026-08-31T14:00:00Z
index_started_at2026-08-27T00:00:00Z
since2026-08-24T00:00:00
count1
next_cursor2026-08-28T21:53:58
refresh_after2026-09-17T11:15:00.000Z

events

event_idaccessionciktickercompanyformevent_typeoccurred_atflagsscorepayload.buy_usdpayload.sell_usd
ev_10001214659-26-0111000000096223JEFJEFFERIES FINANCIAL GROUP INC.4insider_transaction2026-08-28T21:53:58large_insider_buy0.71500000.00.0
The same sample as raw JSON
{
 "as_of": "2026-08-31T14:00:00Z",
 "index_started_at": "2026-08-27T00:00:00Z",
 "since": "2026-08-24T00:00:00",
 "count": 1,
 "events": [
  {
   "event_id": "ev_1",
   "accession": "0001214659-26-011100",
   "cik": "0000096223",
   "ticker": "JEF",
   "company": "JEFFERIES FINANCIAL GROUP INC.",
   "form": "4",
   "event_type": "insider_transaction",
   "occurred_at": "2026-08-28T21:53:58",
   "flags": [
    "large_insider_buy"
   ],
   "score": 0.7,
   "payload": {
    "buy_usd": 1500000.0,
    "sell_usd": 0.0,
    "n_buys": 1,
    "n_sells": 0
   },
   "filing_url": "https://www.sec.gov/Archives/edgar/data/96223/000121465926011100-index.htm"
  }
 ],
 "next_cursor": "2026-08-28T21:53:58",
 "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?

Recurring portfolio monitoring; store next_cursor between calls.

What you skip building

When should you not use it?

Market-wide screens or a single company — cheaper views exist.

Where else can you find this?