Filing Calendar API: Get a filer's reporting cadence — SEC EDGAR
Get a filer's reporting cadence — fiscal year end, last 10-K/10-Q dates and naive next-report estimates from historical spacing. Use to time monitoring windows without deriving cadence from raw 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/calendar — product id
sec_filing_calendar. Over MCP, call answerpool_get with
product_id=sec_filing_calendar.
curl "https://answerpool.io/v1/sec/calendar?ticker=NVDA"
# with a prepaid credit key
curl -H "Authorization: Bearer ck_live_..." "https://answerpool.io/v1/sec/calendar?ticker=NVDA"
Live call: https://answerpool.io/v1/sec/calendar?ticker=NVDA · JSON sample: /v1/samples/sec_filing_calendar
What does the answer look like?
A representative response, the same static sample served at /v1/samples/sec_filing_calendar.
as_of | 2026-08-31T14:00:00Z |
|---|---|
cik | 0000320193 |
fiscal_year_end | 0927 |
last_10k_filed | 2025-11-01 |
last_10q_filed | 2026-08-01 |
recent_10q_dates | 2026-08-01, 2026-05-02, 2026-01-31 |
expected_next_10q | 2026-10-31 |
expected_next_10k | 2026-11-01 |
refresh_after | 2026-09-17T11:15:00.000Z |
The same sample as raw JSON
{
"as_of": "2026-08-31T14:00:00Z",
"cik": "0000320193",
"fiscal_year_end": "0927",
"last_10k_filed": "2025-11-01",
"last_10q_filed": "2026-08-01",
"recent_10q_dates": [
"2026-08-01",
"2026-05-02",
"2026-01-31"
],
"expected_next_10q": "2026-10-31",
"expected_next_10k": "2026-11-01",
"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?
Timing questions around periodic reports.
What you skip building
- cadence derivation
- submissions slicing
- date math
When should you not use it?
Earnings-call dates or company guidance — we serve filing cadence only.
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