AnswerPool

8-K Watch API: Watch 8-K filings with a since cursor — SEC EDGAR

Watch 8-K filings with a since cursor — returns only events newer than your cursor, optional item filter, plus the next cursor to store. Use as the cheap poll loop for current-report monitoring.

Free — no key, no signup, rate-limited to 60 calls per minute per client.

How do you call it?

GET /v1/sec/8k/since — product id sec_8k_since. Over MCP, call answerpool_get with product_id=sec_8k_since.

curl "https://answerpool.io/v1/sec/8k/since?since=2026-08-30T00%3A00%3A00Z"

Live call: https://answerpool.io/v1/sec/8k/since?since=2026-08-30T00%3A00%3A00Z · JSON sample: /v1/samples/sec_8k_since

What does the answer look like?

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

as_of2026-09-16T21:48:22.717Z
index_started_at2026-08-30T19:10:24.500Z
since2026-09-15T00:00:00
count3
next_cursor2026-09-16
refresh_after2026-09-17T11:15:00.000Z

events

event_idaccessionciktickercompanyformevent_typeoccurred_atflagsscorepayload.itemspayload.labels
ev_f699bd66d60f4b2cac550001104659-26-1083200001282648BATLBATTALION OIL CORP8-Kform_8k2026-09-16delisting_notice0.83.01delisting_notice
ev_2ff77bb74c784946b9b40001193125-26-3932560001467760ARIApollo Commercial Real Estate Finance, Inc.8-Kform_8k2026-09-16other_event0.18.01other_event
ev_2855b751f71142999f6f0001104659-26-1082450002074176VNOMViper Energy, Inc.8-Kform_8k2026-09-16leadership_change, officer_or_director_change0.65.02officer_or_director_change
The same sample as raw JSON
{
 "as_of": "2026-09-16T21:48:22.717Z",
 "index_started_at": "2026-08-30T19:10:24.500Z",
 "since": "2026-09-15T00:00:00",
 "count": 3,
 "events": [
  {
   "event_id": "ev_f699bd66d60f4b2cac55",
   "accession": "0001104659-26-108320",
   "cik": "0001282648",
   "ticker": "BATL",
   "company": "BATTALION OIL CORP",
   "form": "8-K",
   "event_type": "form_8k",
   "occurred_at": "2026-09-16",
   "flags": [
    "delisting_notice"
   ],
   "score": 0.8,
   "payload": {
    "items": [
     "3.01"
    ],
    "labels": [
     "delisting_notice"
    ]
   },
   "filing_url": "https://www.sec.gov/Archives/edgar/data/1282648/000110465926108320/0001104659-26-108320-index.htm"
  },
  {
   "event_id": "ev_2ff77bb74c784946b9b4",
   "accession": "0001193125-26-393256",
   "cik": "0001467760",
   "ticker": "ARI",
   "company": "Apollo Commercial Real Estate Finance, Inc.",
   "form": "8-K",
   "event_type": "form_8k",
   "occurred_at": "2026-09-16",
   "flags": [
    "other_event"
   ],
   "score": 0.1,
   "payload": {
    "items": [
     "8.01"
    ],
    "labels": [
     "other_event"
    ]
   },
   "filing_url": "https://www.sec.gov/Archives/edgar/data/1467760/000119312526393256/0001193125-26-393256-index.htm"
  },
  {
   "event_id": "ev_2855b751f71142999f6f",
   "accession": "0001104659-26-108245",
   "cik": "0002074176",
   "ticker": "VNOM",
   "company": "Viper Energy, Inc.",
   "form": "8-K",
   "event_type": "form_8k",
   "occurred_at": "2026-09-16",
   "flags": [
    "leadership_change",
    "officer_or_director_change"
   ],
   "score": 0.6,
   "payload": {
    "items": [
     "5.02"
    ],
    "labels": [
     "officer_or_director_change"
    ]
   },
   "filing_url": "https://www.sec.gov/Archives/edgar/data/2074176/000110465926108245/0001104659-26-108245-index.htm"
  }
 ],
 "next_cursor": "2026-09-16",
 "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 checks; store next_cursor between calls.

What you skip building

When should you not use it?

One-off reads — use the feed.

Where else can you find this?