SEC Filing Volume API: Daily counts for any SEC form vs its 52-week average and last year's — SEC EDGAR
Daily counts for any SEC form vs its 52-week average and last year's same window, from our multi-year index — filing-volume anomalies in one call. Free, no key.
Free — no key, no signup, rate-limited to 60 calls per minute per client.
How do you call it?
GET /v1/sec/volume — product id
sec_filing_volume. Over MCP, call answerpool_get with
product_id=sec_filing_volume.
curl "https://answerpool.io/v1/sec/volume?form=8-K"
Live call: https://answerpool.io/v1/sec/volume?form=8-K · JSON sample: /v1/samples/sec_filing_volume
What does the answer look like?
A representative response, the same static sample served at /v1/samples/sec_filing_volume.
as_of | 2026-09-03T02:00:00Z |
|---|---|
form | 8-K |
window_days | 30 |
index_covers_since | 2021-07-01 |
index_covers_until | 2026-09-02 |
window_total | 4210 |
weekly_avg_52w | 982.4 |
same_window_last_year | 4102 |
disclaimer | Derived from public SEC EDGAR filings; not investment advice. |
refresh_after | 2026-09-17T11:15:00.000Z |
daily
| day | filings |
|---|---|
| 2026-09-02 | 214 |
The same sample as raw JSON
{
"as_of": "2026-09-03T02:00:00Z",
"form": "8-K",
"window_days": 30,
"index_covers_since": "2021-07-01",
"index_covers_until": "2026-09-02",
"window_total": 4210,
"weekly_avg_52w": 982.4,
"same_window_last_year": 4102,
"daily": [
{
"day": "2026-09-02",
"filings": 214
}
],
"disclaimer": "Derived from public SEC EDGAR filings; not investment advice.",
"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?
You need volume context — surge or lull detection — for a form type.
What you skip building
- counting EDGAR pages
- building your own baseline history
When should you not use it?
The filings themselves — /v1/sec/filings/latest or /v1/sec/8k.
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