AnswerPool

Officer Changes API: List 8-Ks reporting officer or director changes (Item 5.02) market-wide — SEC EDGAR

List 8-Ks reporting officer or director changes (Item 5.02) market-wide — the most filed 8-K item, with company, time and links. Use for leadership-change monitoring without polling and mapping the tape.

$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/officer-change — product id sec_8k_officer_change. Over MCP, call answerpool_get with product_id=sec_8k_officer_change.

curl "https://answerpool.io/v1/sec/8k/officer-change?limit=25"

# with a prepaid credit key
curl -H "Authorization: Bearer ck_live_..." "https://answerpool.io/v1/sec/8k/officer-change?limit=25"

Live call: https://answerpool.io/v1/sec/8k/officer-change?limit=25 · JSON sample: /v1/samples/sec_8k_officer_change

What does the answer look like?

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

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

events

event_idaccessionciktickercompanyformevent_typeoccurred_atflagsscorepayload.itemspayload.labels
ev_2855b751f71142999f6f0001104659-26-1082450002074176VNOMViper Energy, Inc.8-Kform_8k2026-09-16leadership_change, officer_or_director_change0.65.02officer_or_director_change
ev_f7e2d76bd70b4f17b7ab0000899923-26-0000790000899923MYGNMYRIAD GENETICS INC8-Kform_8k2026-09-16leadership_change, officer_or_director_change, regulation_fd0.75.02, 7.01, 9.01officer_or_director_change, regulation_fd, exhibits
ev_dc3bc7a907f442d995f40001104659-26-1082550000868857ACMAECOM8-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:47:52.314Z",
 "index_started_at": "2026-08-30T19:10:24.500Z",
 "since": "2026-08-31T00:00:00",
 "count": 3,
 "events": [
  {
   "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"
  },
  {
   "event_id": "ev_f7e2d76bd70b4f17b7ab",
   "accession": "0000899923-26-000079",
   "cik": "0000899923",
   "ticker": "MYGN",
   "company": "MYRIAD GENETICS INC",
   "form": "8-K",
   "event_type": "form_8k",
   "occurred_at": "2026-09-16",
   "flags": [
    "leadership_change",
    "officer_or_director_change",
    "regulation_fd"
   ],
   "score": 0.7,
   "payload": {
    "items": [
     "5.02",
     "7.01",
     "9.01"
    ],
    "labels": [
     "officer_or_director_change",
     "regulation_fd",
     "exhibits"
    ]
   },
   "filing_url": "https://www.sec.gov/Archives/edgar/data/899923/000089992326000079/0000899923-26-000079-index.htm"
  },
  {
   "event_id": "ev_dc3bc7a907f442d995f4",
   "accession": "0001104659-26-108255",
   "cik": "0000868857",
   "ticker": "ACM",
   "company": "AECOM",
   "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/868857/000110465926108255/0001104659-26-108255-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?

Leadership and governance monitoring.

What you skip building

When should you not use it?

Named-person detail — we serve the filing event, not parsed names yet.

Where else can you find this?