Filings Watch API: Watch one filer's SEC filings with a date cursor — SEC EDGAR
Watch one filer's SEC filings with a date cursor — returns only filings newer than your cursor plus the next cursor, optional form filter. Use as the per-company poll loop instead of refetching submissions JSON.
Free — no key, no signup, rate-limited to 60 calls per minute per client.
How do you call it?
GET /v1/sec/filings/since — product id
sec_filings_since. Over MCP, call answerpool_get with
product_id=sec_filings_since.
curl "https://answerpool.io/v1/sec/filings/since?ticker=NVDA&since=2026-08-01"
Live call: https://answerpool.io/v1/sec/filings/since?ticker=NVDA&since=2026-08-01 · JSON sample: /v1/samples/sec_filings_since
What does the answer look like?
A representative response, the same static sample served at /v1/samples/sec_filings_since.
as_of | 2026-08-31T14:00:00Z |
|---|---|
cik | 0000320193 |
count | 1 |
next_cursor | 2026-08-29 |
refresh_after | 2026-09-17T11:15:00.000Z |
filings
| accession | form | filed | report_date | items | description | url |
|---|---|---|---|---|---|---|
| 0001437749-26-028920 | 8-K | 2026-08-29 | 2026-08-28 | 1.03 | FORM 8-K | https://www.sec.gov/Archives/edgar/data/320193/000143774926028920-index.htm |
The same sample as raw JSON
{
"as_of": "2026-08-31T14:00:00Z",
"cik": "0000320193",
"count": 1,
"filings": [
{
"accession": "0001437749-26-028920",
"form": "8-K",
"filed": "2026-08-29",
"report_date": "2026-08-28",
"items": [
"1.03"
],
"description": "FORM 8-K",
"url": "https://www.sec.gov/Archives/edgar/data/320193/000143774926028920-index.htm"
}
],
"next_cursor": "2026-08-29",
"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?
Recurring per-company checks; store next_cursor.
What you skip building
- submissions refetching
- cursor bookkeeping
When should you not use it?
Multi-ticker portfolios — the watchlist view batches 25.
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