Free 8-K API
for SEC Filing Data免费 8-K API
获取 SEC 申报数据
Build a free 8-K event feed that detects new SEC current reports, preserves every reported Item, follows material exhibits, and issues correction-aware alerts with source evidence.
建立免费的 8-K 事件数据流：及时发现 SEC 重大事件报告，保留全部 Item，追踪关键附件，并以来源证据支持提醒与后续更正。
TL;DR摘要
Event feed, not headline feed
An 8-K can report several Items and attach the document that contains the real detail. Capture the filing package instead of reducing it to one generated headline.
Time has three meanings
Keep event or report date, SEC filing date, and accepted timestamp separately. Monitoring and point-in-time research normally depend on acceptance time.
Accession is the filing key
Deduplicate by accession number, not ticker and date. Link an 8-K/A to the original as a new disclosure version rather than overwriting it.
Evidence completes the alert
Return CIK, form, Items, primary document, exhibits, official URLs, retrieval time, and parser version so the event can be verified.
它是事件流，不是标题流
一份 8-K 可以同时报告多个 Item，真正细节还可能位于附件中。不能只保留一条自动生成的标题，而应采集完整申报材料。
时间至少有三种含义
事件或报告日期、SEC 申报日与 accepted timestamp 应分别保存；监控与时点研究通常以受理时间为准。
accession 是文件主键
按 accession number 去重，而不是按 ticker 与日期去重。8-K/A 应作为新的披露版本关联原文件，不能覆盖。
证据让提醒完整
返回 CIK、表格、Items、主要文件、附件、官方 URL、抓取时间与解析器版本，使事件能够被核验。
How to use a free 8-K API for SEC filings如何使用免费 8-K API 获取 SEC 申报
An 8-K API primarily supports event monitoring. Poll or stream new accessions across the issuer universe, parse the item numbers and acceptance timestamp, fetch linked exhibits, and classify the event without guessing from the headline alone. The workflow must distinguish filing arrival from the underlying event date and treat 8-K/A as a new disclosure version rather than a duplicate.
8-K API 的主要用途是事件监控。应在发行人范围内轮询或订阅新 accession，解析 Item 编号和 SEC 接收时间，获取关联附件，并在不只依赖标题的情况下分类事件。工作流必须区分文件到达时间与事件发生日期，并把 8-K/A 视为新的披露版本，而不是普通重复记录。
Item codes are the first structured clue, not the final interpretation. Item 1.01 can identify a material agreement; Item 2.01 a completed acquisition or disposition; Item 2.02 results of operations; Item 5.02 leadership and compensation events; Item 7.01 Regulation FD disclosure; Item 8.01 other events; and Item 9.01 financial statements and exhibits. One accession can contain several Items, while an EX-99.1 exhibit may contain the earnings release or presentation users actually need.
Item 编号是第一层结构化线索，但不是最终结论。例如，Item 1.01 可对应重大协议，Item 2.01 对应已完成的收购或处置，Item 2.02 对应经营结果，Item 5.02 涉及高管与薪酬事项，Item 7.01 是 Regulation FD 披露，Item 8.01 是其他事件，Item 9.01 则列示财务报表与附件。一份 accession 可以同时包含多个 Item，而用户真正想读的财报新闻稿或演示文稿常位于 EX-99.1 等附件中。
1. Detect new accessions with low duplication risk
Use accession number as the immutable event key and retain SEC acceptance time. A ticker-only poll can miss renamed issuers and produce duplicate notifications.
2. Parse item codes before assigning event meaning
Items distinguish earnings, agreements, acquisitions, officer changes, impairments, and other disclosures. Preserve every reported item because one 8-K can contain multiple events.
3. Retrieve and classify exhibits
Material detail often lives in an earnings release, agreement, or presentation filed as an exhibit. Save exhibit type, filename, URL, and its relationship to the parent filing.
4. Build correction-aware alerts
Send an initial alert from stable filing metadata, then enrich it after parsing. When an amendment arrives, link it to the original and emit a correction instead of a second unrelated event.
5. Separate detection from enrichment latency
Measure when EDGAR accepted the accession, when the feed observed it, and when documents and exhibits finished parsing. Label preliminary and enriched states explicitly instead of presenting incomplete evidence as final.
6. Preserve multi-event structure
Model filing, Item, exhibit, and derived event as related records. Alerts created from several Items should share one accession, while no single category should hide other material disclosures in the filing.
1. 以低重复风险发现新申报
用 accession number 作为不可变事件键，并保存 SEC 接收时间。只按股票代码轮询可能漏掉更名发行人，还会产生重复通知。
2. 先解析 Item 编号，再判断事件含义
Item 可区分财报、重大协议、收购、管理层变动、减值等披露。一份 8-K 可能包含多个事件，因此必须保留全部 Item。
3. 获取并分类附件
关键细节通常位于作为附件提交的财报新闻稿、协议或演示文稿中。应保存附件类型、文件名、URL 以及它与主申报的关系。
4. 构建能够处理修正的告警
先根据稳定申报元数据发送初始提醒，解析完成后再补充内容。收到修订文件时，应关联原申报并发送更正，而不是生成第二个无关事件。
5. 区分发现延迟与内容补全延迟
分别记录 accession 的受理时间、数据流首次发现时间，以及正文与附件解析完成时间。应明确标记“初步”与“已补全”状态，不能把证据尚不完整的内容当成最终结论。
6. 保留一份文件中的多事件结构
把 filing、Item、附件和派生事件建模为相关记录。由多个 Item 生成的提醒必须共享同一 accession，也不能用一个类别掩盖文件中的其他重要披露。
Free SEC filing API fields and capabilities免费 SEC 申报接口的字段与能力
| Layer层级 | Main job主要作用 | Best for适合场景 | Boundary边界 |
|---|---|---|---|
| Form type | 8-K or 8-K/A.8-K 或 8-K/A。 | Separating original filings from amendments.区分原始申报与修订文件。 | Do not infer event meaning from form type alone.不能只凭表单类型推断事件含义。 |
| CIK / ticker | Issuer lookup key.发行人查询键。 | Company-specific 8-K search.查询特定公司的 8-K。 | Ticker may be absent or change.股票代码可能缺失或变化。 |
| Accession / URL | Unique filing reference and source document.唯一申报标识与原始文档。 | Deduplication and audit trails.去重与审计追踪。 | Document parsing may be separate.文档解析可能需要另一接口。 |
| Extracted 8-K items | Item number, event category, exhibits, acceptance time, and filing text.Item 编号、事件类别、附件、接收时间与申报正文。 | Structured event monitoring and research.结构化事件监控与研究。 | Coverage varies by provider and plan.覆盖范围取决于提供方和套餐。 |
| Accepted timestamp受理时间 | When EDGAR accepted the filing.EDGAR 受理文件的时间。 | Ordering alerts and point-in-time research.提醒排序与时点研究。 | It is not necessarily the underlying event date.它不一定等于事件实际发生日期。 |
| Item listItem 列表 | All reported Item numbers and captions.文件报告的全部 Item 编号与标题。 | Routing to earnings, M&A, governance, financing, or risk workflows.路由到财报、并购、治理、融资或风险工作流。 | One filing can contain several Items; captions do not replace source text.一份文件可包含多个 Item；标题不能替代原文判断。 |
| Exhibit relationship附件关系 | Sequence, exhibit type, filename, description, URL, and parent accession.顺序、附件类型、文件名、说明、URL 与所属 accession。 | Retrieving releases, agreements, presentations, and schedules.获取新闻稿、协议、演示文稿与财务附表。 | The primary 8-K may only summarize the exhibit.8-K 主文档可能只概述附件。 |
8-K filings API example and validation checklist8-K 申报 API 示例与验证清单
Model the response as a filing package, not a flattened headline. This provider-neutral JSON uses placeholders, but it captures the relationships a production alert needs to preserve.
响应应被建模为完整申报材料，而不是压平成一条标题。下面是使用占位值的通用 JSON，重点展示生产级提醒必须保留的关联关系。
{
"issuer": {"cik": "CIK_PLACEHOLDER", "ticker": "TICKER_PLACEHOLDER"},
"filing": {
"accession_number": "ACCESSION_PLACEHOLDER",
"form": "8-K",
"accepted_at": "YYYY-MM-DDThh:mm:ss-04:00",
"report_date": "YYYY-MM-DD",
"items": ["2.02", "9.01"],
"filing_index_url": "SEC_FILING_INDEX_URL",
"primary_document_url": "SEC_PRIMARY_DOCUMENT_URL",
"amends_accession": null
},
"exhibits": [
{
"sequence": 1,
"type": "EX-99.1",
"description": "Earnings release",
"source_url": "SEC_EXHIBIT_URL",
"retrieval_status": "complete"
}
],
"processing": {
"state": "enriched",
"retrieved_at": "YYYY-MM-DDThh:mm:ssZ",
"parser_version": "PARSER_VERSION"
}
}The accession remains the parent key. Items and exhibits are child records, so a multi-Item filing is stored once and can generate several evidence-linked alerts. If an 8-K/A arrives, give it its own accession and populate amends_accession; never overwrite the original package or reuse its acceptance time.
accession 始终是父级主键。Item 与附件作为子记录保存，因此一份包含多个 Item 的文件只入库一次，却可以生成多条带证据的提醒。收到 8-K/A 时，应使用新的 accession，并填写 amends_accession；不能覆盖原申报材料，也不能沿用原文件的受理时间。
Define the event universe
Choose issuers, exact forms, Item filters, and a time window. Decide whether 8-K/A enters the same stream and whether every Item triggers an alert or only configured categories. Use CIK for issuer identity and ticker as display metadata.
Checkpoint with an overlap window
Persist the last accepted timestamp, re-read a small overlap after each run, paginate to completion, and deduplicate by accession. This protects against delayed availability, reordered responses, and partial failures.
Validate the filing package
Require CIK, accession, exact form, accepted time, report date, primary document, Item list, and official filing-index URL. Enumerate exhibits and verify links before marking the event complete.
Classify with evidence
Use Item codes and exhibit types as deterministic signals, then extract entities, amounts, dates, and summaries from source text. Store rule or model version, confidence, source location, and parent accession; route low-confidence results to review.
Test alert correctness
Replay a multi-Item filing, an earnings-release exhibit, an 8-K/A, a renamed issuer, an after-hours acceptance, and a temporary fetch failure. Measure detection delay, duplicate rate, missing-exhibit rate, and correction linkage.
定义事件范围
确定发行人、准确表格、Item 筛选和时间窗口，并明确 8-K/A 是否进入同一数据流，以及全部 Item 都提醒还是只提醒指定类别。发行人身份以 CIK 为准，ticker 作为展示信息。
设置带重叠窗口的检查点
持久化最后成功处理的 accepted timestamp，每次运行时回读一小段重叠窗口，完整处理分页，再按 accession 去重，防止延迟可见、响应重排或中途故障造成漏报。
验证完整申报材料
要求返回 CIK、accession、准确表格、受理时间、报告日期、主要文件、Item 列表与官方文件索引 URL。枚举附件并确认链接有效后，才能把事件标记为“内容完整”。
以证据支持事件分类
先用 Item 编号与附件类型作为确定性信号，再从原文提取主体、金额、日期和摘要。保存规则或模型版本、置信度、来源位置与父 accession；低置信度结果进入人工复核。
测试提醒是否正确
评测集应包含多 Item 文件、财报新闻稿附件、8-K/A、更名发行人、盘后受理文件和一次临时抓取失败，并衡量发现延迟、重复率、附件漏取率与修订关联准确率。
How QVeris helps discover an 8-K filing APIQVeris 如何帮助发现 8-K 申报接口
QVeris can help an agent discover and inspect capabilities for current-report discovery, Item extraction, exhibit retrieval, or filing alerts. Before calling a tool, the agent should state the issuer universe, exact forms, Item categories, time window, desired latency, amendment policy, and evidence fields. It should not turn a preliminary filing record into a definitive event summary before linked exhibits are available. Provider rights, quota, freshness, and usage terms still apply.
QVeris 可以帮助 Agent 发现并检查重大事件报告检索、Item 提取、附件下载或申报提醒等能力。调用前，Agent 应明确发行人范围、准确表格、Item 类别、时间窗口、延迟要求、修订策略与证据字段；关联附件尚未获得时，不能把初步文件记录包装成确定性的事件结论。服务商的数据权利、额度、更新频率和使用条款仍然适用。
- Open the QVeris tool details for issuer lookup, SEC filing search, or structured filing extraction.
- Inspect required parameters and returned fields before connecting the capability to an agent workflow.
- Keep the SEC source URL and provider attribution in every research output.
- 打开 QVeris 工具详情，查看符合发行人查询、SEC 申报检索或结构化解析需求的能力。
- 接入 Agent 工作流前，先检查必填参数、返回字段与提供方条款。
- 在研究输出中保留 SEC 原始链接与提供方归属。
FAQ常见问题
Is there an official free SEC 8-K API?
SEC EDGAR exposes public filing metadata and archived documents without an API key. Filter submissions for 8-K and 8-K/A, follow current access guidance, and retrieve the filing index plus exhibits when the event requires more than metadata.
Which fields are essential for an 8-K event feed?
Keep CIK, accession, form, accepted timestamp, filing and report dates, every Item, primary document, filing-index URL, exhibit sequence and type, retrieval state, and amendment relationship. Derived categories should retain evidence and classifier version.
Can one 8-K represent multiple events?
Yes. A filing can report several Items and exhibits. Model the filing once, attach multiple Item and document records, and let alerts share the accession rather than duplicating it as unrelated events.
Why are exhibits important?
The primary 8-K may summarize an earnings release, agreement, presentation, or financial schedule filed as an exhibit. Ignoring the exhibit list can miss the figures or terms users actually need.
How should 8-K/A affect alerts?
Store it as a separate accession, link it to the original disclosure, identify what changed, and emit a correction or update. Do not silently overwrite history or create an unrelated duplicate.
How can I reduce missed or duplicate alerts?
Checkpoint on accepted time, replay an overlap window, paginate fully, deduplicate by accession, separate preliminary from enriched status, and retry missing exhibits independently.
SEC 是否提供免费的 8-K 官方 API？
SEC EDGAR 无需 API key 即可提供公开申报元数据和归档正文。可在 submissions 中筛选 8-K 与 8-K/A，并根据事件需要获取文件索引与附件，同时遵守当前访问指引。
8-K 事件流至少应包含哪些字段？
应保留 CIK、accession、表格、accepted timestamp、申报日与报告日期、全部 Item、主要文件、文件索引 URL、附件顺序与类型、抓取状态和修订关系。派生类别还应保留证据与分类器版本。
一份 8-K 可以代表多个事件吗？
可以。一份文件可同时报告多个 Item 并包含多个附件。应只建立一条 filing 记录，再关联多个 Item 与文档；拆成提醒时共享同一 accession，不能复制成互不相关的事件。
为什么 8-K 附件很重要？
8-K 主文档可能只概述作为附件提交的财报新闻稿、协议、演示文稿或财务附表。忽略附件列表，很可能漏掉用户真正需要的数字或条款。
8-K/A 应如何影响提醒？
把它作为独立 accession 保存，与原披露建立关联，识别实际变化，并发送更正或更新。不能静默覆盖历史，也不能生成无关的重复提醒。
如何减少提醒漏报与重复？
按 accepted time 保存检查点，重放一段重叠窗口，完整处理分页，按 accession 去重，区分“初步”与“已补全”状态，并单独重试缺失附件。