Live SEC API use case
SEC 8-K API
A focused 8-K monitoring page for teams that search for current report APIs and need a normalized polling feed without parsing raw EDGAR submissions.
GET /v1/sec/changes?since=2026-07-01&form=8-K&limit=50
{
"data": [
{
"changeType": "material_event",
"observedAt": "2026-07-03T00:00:00+00:00",
"filing": {
"ticker": "AAPL",
"form": "8-K",
"eventType": "current_report",
"filedAt": "2026-07-02"
}
}
],
"meta": { "count": 1, "form": "8-K" }
}
Workflow Fit
This page shows how the implemented SEC endpoints fit common buyer workflows, examples, and pricing tiers.
- Material-event alert workers for issuer watchlists.
- Internal compliance dashboards that track current reports.
- News and research tools that need ticker-first 8-K metadata.
8-K first-call path
Use the same 8-K workflow signal across REST, hosted MCP, Postman, and direct-access review before moving it into a scheduled alert worker.
-
REST playgroundOpen the filing-change playgroundform=8-Kwith the 8-K form filter before copying code. -
No-key MCP checkRun the MCP browser demosec_demo_latest_filingsthen call the subscription-info tool for REST and hosted MCP access routes. -
Machine handoffRead the first public tool-call JSONtools/callfor the no-key tools/call payload and follow-up access call. -
Postman importDownload the Postman collection/v1/sec/changesand pair it with the public environment file for REST endpoint review. -
Hosted MCP accessRequest hosted MCP accessx-api-keywhen production tool calls must run against the hosted MCP endpoint.
Use Case FAQ
Is the SEC 8-K API a separate backend?
No. It is a focused use-case page for the live filing-change endpoint with a form=8-K filter.
Does it summarize the legal meaning of an 8-K?
No. It returns public filing metadata and source-linked records only.