AnswerPool

8-K History API: Get a filer's 8-K history with item codes — SEC EDGAR

Get a filer's 8-K history with item codes — filter by item (e.g. 5.02 officer changes, 2.02 earnings) and date; includes coverage note. Use instead of paginating submissions and mapping item codes yourself.

$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/8k/history — product id sec_8k_items_history. Over MCP, call answerpool_get with product_id=sec_8k_items_history.

curl "https://answerpool.io/v1/sec/8k/history?ticker=NVDA&items=5.02"

# with a prepaid credit key
curl -H "Authorization: Bearer ck_live_..." "https://answerpool.io/v1/sec/8k/history?ticker=NVDA&items=5.02"

Live call: https://answerpool.io/v1/sec/8k/history?ticker=NVDA&items=5.02 · JSON sample: /v1/samples/sec_8k_items_history

What does the answer look like?

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

as_of2026-08-31T14:00:00Z
cik0000320193
count1
coverage_noteSEC 'recent' window for this filer reaches back to 2026-08-29
refresh_after2026-09-17T11:15:00.000Z

filings

accessionformfiledreport_dateitemsdescriptionurl
0001437749-26-0289208-K2026-08-292026-08-281.03FORM 8-Khttps://www.sec.gov/Archives/edgar/data/320193/000143774926028920-index.htm
The same sample as raw JSON
{
 "as_of": "2026-08-31T14:00:00Z",
 "cik": "0000320193",
 "count": 1,
 "filings": [
  {
   "accession": "0001437749-26-028920",
   "form": "8-K",
   "filed": "2026-08-29",
   "report_date": "2026-08-28",
   "items": [
    "1.03"
   ],
   "description": "FORM 8-K",
   "url": "https://www.sec.gov/Archives/edgar/data/320193/000143774926028920-index.htm"
  }
 ],
 "coverage_note": "SEC 'recent' window for this filer reaches back to 2026-08-29",
 "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?

Per-company 8-K event history questions.

What you skip building

When should you not use it?

Market-wide 8-K feeds — those views run on our index.

Where else can you find this?