Filing Cadence API: Get a filer's year-by-year filing counts per form since 2021 — SEC EDGAR
Get a filer's year-by-year filing counts per form since 2021 — reporting rhythm, disclosure volume and gaps in one call from our historical index. Use to spot stopped reports or disclosure spikes without listing filings.
$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/filings/cadence — product id
sec_filing_cadence. Over MCP, call answerpool_get with
product_id=sec_filing_cadence.
curl "https://answerpool.io/v1/sec/filings/cadence?ticker=NVDA"
# with a prepaid credit key
curl -H "Authorization: Bearer ck_live_..." "https://answerpool.io/v1/sec/filings/cadence?ticker=NVDA"
Live call: https://answerpool.io/v1/sec/filings/cadence?ticker=NVDA · JSON sample: /v1/samples/sec_filing_cadence
What does the answer look like?
A representative response, the same static sample served at /v1/samples/sec_filing_cadence.
as_of | 2026-08-31T16:30:00Z |
|---|---|
index_from | 2021-07-01 |
index_to | 2026-08-28 |
cik | 0000320193 |
company | APPLE INC |
total_filings | 49 |
refresh_after | 2026-09-17T11:15:00.000Z |
years
| year | counts.4 | counts.8-K | total |
|---|---|---|---|
| 2026 | 40 | 9 | 49 |
The same sample as raw JSON
{
"as_of": "2026-08-31T16:30:00Z",
"index_from": "2021-07-01",
"index_to": "2026-08-28",
"cik": "0000320193",
"company": "APPLE INC",
"years": [
{
"year": "2026",
"counts": {
"4": 40,
"8-K": 9
},
"total": 49
}
],
"total_filings": 49,
"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?
Rhythm/volume questions per filer.
What you skip building
- aggregation over filing lists
- multi-year pagination
When should you not use it?
Individual filings — use history or list views.
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