Filings History API: Get a filer's complete filing history from our 4M-row historical index — SEC EDGAR
Get a filer's complete filing history from our 4M-row historical index — accession, form, date and URL per filing, form- and date-filterable, coverage stated. Use when the live 'recent' shard is too shallow and paginating EDGAR is too slow.
Free — no key, no signup, rate-limited to 60 calls per minute per client.
How do you call it?
GET /v1/sec/filings/history — product id
sec_filings_history. Over MCP, call answerpool_get with
product_id=sec_filings_history.
curl "https://answerpool.io/v1/sec/filings/history?ticker=NVDA&form=10-K"Live call: https://answerpool.io/v1/sec/filings/history?ticker=NVDA&form=10-K · JSON sample: /v1/samples/sec_filings_history
What does the answer look like?
A representative response, the same static sample served at /v1/samples/sec_filings_history.
as_of | 2026-08-31T16:30:00Z |
|---|---|
index_from | 2021-07-01 |
index_to | 2026-08-28 |
cik | 0000320193 |
count | 1 |
refresh_after | 2026-09-17T11:15:00.000Z |
filings
| accession | form | filed | company | url |
|---|---|---|---|---|
| 0001437749-26-028920 | 8-K | 2026-08-29 | APPLE INC | https://www.sec.gov/Archives/edgar/data/320193/000143774926028920-index.htm |
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",
"count": 1,
"filings": [
{
"accession": "0001437749-26-028920",
"form": "8-K",
"filed": "2026-08-29",
"company": "APPLE INC",
"url": "https://www.sec.gov/Archives/edgar/data/320193/000143774926028920-index.htm"
}
],
"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?
Per-filer history beyond the recent shard.
What you skip building
- EDGAR pagination
- full-index downloads
- URL construction
When should you not use it?
Pre-2021 history (not yet indexed) or full documents.
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