Auditor Changes API: List 8-Ks reporting an auditor change (Item 4.01) market-wide — SEC EDGAR
List 8-Ks reporting an auditor change (Item 4.01) market-wide — a standing accounting red flag with company, time and links. Use for accounting-risk monitoring instead of filtering 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/auditor-change — product id
sec_8k_auditor_change. Over MCP, call answerpool_get with
product_id=sec_8k_auditor_change.
curl "https://answerpool.io/v1/sec/8k/auditor-change?limit=25"
# with a prepaid credit key
curl -H "Authorization: Bearer ck_live_..." "https://answerpool.io/v1/sec/8k/auditor-change?limit=25"
Live call: https://answerpool.io/v1/sec/8k/auditor-change?limit=25 · JSON sample: /v1/samples/sec_8k_auditor_change
What does the answer look like?
A representative response, the same static sample served at /v1/samples/sec_8k_auditor_change.
as_of | 2026-09-16T21:47:49.613Z |
|---|---|
index_started_at | 2026-08-30T19:10:24.500Z |
since | 2026-08-31T00:00:00 |
count | 3 |
next_cursor | 2026-09-16 |
refresh_after | 2026-09-17T11:15:00.000Z |
events
| event_id | accession | cik | ticker | company | form | event_type | occurred_at | flags | score | payload.items | payload.labels |
|---|---|---|---|---|---|---|---|---|---|---|---|
| ev_55fbb86d09d04f7ba0b5 | 0001437749-26-030517 | 0000884269 | APT | ALPHA PRO TECH LTD | 8-K | form_8k | 2026-09-16 | accounting_red_flag, auditor_change | 1.0 | 4.01, 9.01 | auditor_change, exhibits |
| ev_5ffadd8a01da4cc8b891 | 0001640334-26-001562 | 0001794942 | SKFG | Stark Focus Group, Inc. | 8-K | form_8k | 2026-09-16 | accounting_red_flag, auditor_change | 1.0 | 4.01, 9.01 | auditor_change, exhibits |
| ev_03ce1026f76440f18126 | 0001493152-26-042938 | 0001392694 | SURG | SurgePays, Inc. | 8-K | form_8k | 2026-09-16 | accounting_red_flag, auditor_change | 1.0 | 4.01 | auditor_change |
The same sample as raw JSON
{
"as_of": "2026-09-16T21:47:49.613Z",
"index_started_at": "2026-08-30T19:10:24.500Z",
"since": "2026-08-31T00:00:00",
"count": 3,
"events": [
{
"event_id": "ev_55fbb86d09d04f7ba0b5",
"accession": "0001437749-26-030517",
"cik": "0000884269",
"ticker": "APT",
"company": "ALPHA PRO TECH LTD",
"form": "8-K",
"event_type": "form_8k",
"occurred_at": "2026-09-16",
"flags": [
"accounting_red_flag",
"auditor_change"
],
"score": 1.0,
"payload": {
"items": [
"4.01",
"9.01"
],
"labels": [
"auditor_change",
"exhibits"
]
},
"filing_url": "https://www.sec.gov/Archives/edgar/data/884269/000143774926030517/0001437749-26-030517-index.htm"
},
{
"event_id": "ev_5ffadd8a01da4cc8b891",
"accession": "0001640334-26-001562",
"cik": "0001794942",
"ticker": "SKFG",
"company": "Stark Focus Group, Inc.",
"form": "8-K",
"event_type": "form_8k",
"occurred_at": "2026-09-16",
"flags": [
"accounting_red_flag",
"auditor_change"
],
"score": 1.0,
"payload": {
"items": [
"4.01",
"9.01"
],
"labels": [
"auditor_change",
"exhibits"
]
},
"filing_url": "https://www.sec.gov/Archives/edgar/data/1794942/000164033426001562/0001640334-26-001562-index.htm"
},
{
"event_id": "ev_03ce1026f76440f18126",
"accession": "0001493152-26-042938",
"cik": "0001392694",
"ticker": "SURG",
"company": "SurgePays, Inc.",
"form": "8-K",
"event_type": "form_8k",
"occurred_at": "2026-09-16",
"flags": [
"accounting_red_flag",
"auditor_change"
],
"score": 1.0,
"payload": {
"items": [
"4.01"
],
"labels": [
"auditor_change"
]
},
"filing_url": "https://www.sec.gov/Archives/edgar/data/1392694/000149315226042938/0001493152-26-042938-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.
- SEC EDGAR (US federal public domain) — upstream:
https://efts.sec.gov
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?
Accounting-quality screens.
What you skip building
- item filtering
- polling
When should you not use it?
Restatements — the non-reliance view is Item 4.02.
Where else can you find this?
- Catalog entry (JSON, free)
- OpenAPI schema — input and output types, prices, the 402 flow
- llms.txt — every product in one plain-text document