Compare free SEC filing APIs for EDGAR data, XBRL, extraction, alerts, limits, provenance, and architecture.
比较免费 SEC 申报 API 的 EDGAR 数据、XBRL、章节提取、提醒、额度、来源追溯与生产架构。
The short answer is that the SEC itself offers public, keyless EDGAR data access, while commercial providers may offer a limited free plan around the same source material. The better choice depends less on the word “free” than on whether you need raw authority, normalized fields, searchable text, extracted sections, or production alerts. A developer validating one issuer can use a very different stack from a research product monitoring thousands of issuers.
简单来说，SEC 本身提供无需密钥的 EDGAR 公共数据接口，商业服务商则可能围绕同一批源文件提供有限免费套餐。真正影响选择的不是“免费”二字，而是你需要权威原文、标准化字段、正文搜索、章节提取，还是生产级提醒。只验证一家公司的开发者，与持续监控数千家发行人的研究产品，适合的方案并不相同。
Before comparing providers, write down one acceptance task: for example, “return every 8-K filed by this CIK after a timestamp, include accession number and primary-document URL, and surface amendments separately.” A concrete task makes historical gaps, ambiguous freshness, and misleading free-tier claims visible in minutes.
比较服务前，先写出一条可验收任务，例如：“返回该 CIK 在某一时间点之后提交的全部 8-K，包含 accession number 与主要文件 URL，并把修订文件单独标出。”有了具体任务，历史缺口、更新时间含糊和免费套餐描述不清等问题，几分钟内就能暴露出来。
Use data.sec.gov for submissions history and XBRL company facts without an API key. You still own ticker mapping, document retrieval, caching, parsing, and monitoring.通过 data.sec.gov 获取申报历史与 XBRL 公司事实，无需 API 密钥；但股票代码映射、正文下载、缓存、解析与监控仍需自行实现。
A provider may add ticker lookup, consistent JSON, search, extracted sections, SDKs, or webhooks. Test whether those derived fields link back to the exact filing version.第三方服务可能提供股票代码查询、统一 JSON、全文搜索、章节提取、SDK 或 webhook；还要测试派生字段能否回溯到准确的文件版本。
Check daily and monthly quotas, burst limits, historical depth, endpoint exclusions, trial expiry, attribution, redistribution, and commercial-use rights.应核对日/月额度、突发限制、历史范围、受限端点、试用期限，以及署名、再分发与商业使用权。
Keep CIK, accession number, accepted time, filing and report dates, form type, amendment status, and the official SEC document URL.保留 CIK、accession number、受理时间、申报日与报告期、表格类型、修订状态及 SEC 官方文件 URL。
The official SEC EDGAR application programming interfaces expose JSON submissions history and XBRL data at data.sec.gov. They require no API key, but automated access must comply with the SEC privacy and security policy and identify the requesting application.
官方 SEC EDGAR API 文档说明了 data.sec.gov 的 JSON 申报历史与 XBRL 数据端点。这些接口无需 API 密钥，但自动访问必须遵守 SEC 隐私与安全政策，并标识请求应用。
Resolve the ticker to a ten-digit, zero-padded CIK, then request the company submissions JSON. The response includes recent forms, filing dates, accession numbers, primary documents, and references to older submission files.
先把股票代码解析为十位补零 CIK，再请求公司的 submissions JSON。响应包含近期表格、申报日期、accession number、主要文件及更早历史文件的引用。
Companyfacts, companyconcept, and frames endpoints serve machine-readable XBRL facts. They are useful for financial metrics, but they are not a universal substitute for complete 10-K, 10-Q, 8-K, S-1, Form 4, or exhibit text.
companyfacts、companyconcept 与 frames 端点提供机器可读的 XBRL facts，适合财务指标；但它们不能替代完整的 10-K、10-Q、8-K、S-1、Form 4 或附件正文。
Treat every endpoint as a different data contract. Submissions answers “what did this entity file?”, archive documents answer “what was disclosed?”, and XBRL endpoints answer “which tagged facts were reported in a particular context?” Combining them requires explicit joins on CIK, accession number, form, period, unit, and filing version—not a blind merge on company name and fiscal year.
应把每类端点视为不同的数据契约：submissions 回答“这家主体提交了什么”，归档正文回答“文件披露了什么”，XBRL 端点则回答“某个上下文中报告了哪些标签化事实”。组合这些数据时，应明确按 CIK、accession number、表格、期间、单位和文件版本关联，不能只按公司名称与财年粗略合并。
The official route is strongest when source fidelity and control matter. Its engineering cost appears later: resolving historical submission files, downloading exhibits, extracting narrative sections, reconciling amended filings, and operating a respectful incremental crawler. A third-party layer is valuable only if its saved engineering time exceeds the limitations imposed by its quota, schema, latency, or license.
当来源可靠性与自主控制最重要时，官方接口通常更合适；但工程成本会出现在后续环节，包括读取更早的 submissions 文件、下载附件、提取叙述章节、处理修订申报，以及维护符合访问规范的增量采集器。只有当第三方服务节省的工程时间大于额度、字段、延迟或许可带来的限制时，它才真正有价值。
| Check检查项 | Official SEC EDGAR官方 SEC EDGAR | Third-party free tier第三方免费套餐 |
|---|---|---|
| Authentication鉴权 | No API key; descriptive User-Agent required.无需 API 密钥；需使用说明性 User-Agent。 | Usually an account and API key.通常需要账户与 API 密钥。 |
| Response响应 | Submissions JSON, raw documents, and as-filed XBRL.申报 JSON、原始文件与申报态 XBRL。 | May normalize tickers, sections, facts, and form-specific fields.可能标准化股票代码、章节、财务事实与表格字段。 |
| Free boundary免费边界 | Public access subject to fair-access policy.公开访问，受公平访问政策约束。 | Monthly quota, endpoint limits, trial, or beta may apply.可能有月度额度、端点限制、试用或测试期。 |
| Best fit适合场景 | Authoritative source and custom ingestion.权威来源与自建采集处理。 | Faster prototypes needing cleaner schemas or search.需要更干净字段或搜索能力的快速原型。 |
| History and amendments历史与修订 | Public filing history is available, but older metadata and documents may require multiple archive paths.可获取公开申报历史，但较早元数据与正文可能需要读取多个归档路径。 | Coverage may start at a vendor-specific date; test Form /A handling and backfill behavior.覆盖范围可能从服务商指定日期开始；需测试 /A 修订文件与历史回填方式。 |
| Narrative text叙述正文 | Full documents and exhibits are authoritative, but section extraction is your responsibility.完整正文与附件具备权威性，但章节提取需要自行完成。 | May expose risk factors, MD&A, items, or exhibit search; validate boundaries against source HTML.可能直接提供风险因素、MD&A、8-K 项目或附件搜索；应与原始 HTML 核验边界。 |
| Delivery交付方式 | Build polling, checkpoints, deduplication, and replay yourself.轮询、检查点、去重与重放机制需自行构建。 | Webhooks or feeds may reduce work; verify delay, retry policy, ordering, and missed-event recovery.webhook 或数据流可减少开发量，但要核对延迟、重试、顺序与漏报恢复机制。 |
| Verify必须核对 | Current access policy, caching, throttling, and endpoint semantics.当前访问政策、缓存、限流与端点语义。 | Quota, history, freshness, source links, license, and export rights.额度、历史、更新频率、来源链接、许可与导出权。 |
Map a ticker to CIK, then choose whether you need filing metadata, a complete document, XBRL facts, or a form-specific normalized record. A 10-K API free search and a Form 4 transaction feed are different data tasks.
把股票代码映射到 CIK，再确定需要的是申报元数据、完整正文、XBRL facts，还是表格专用的标准化记录。查询免费 10-K API 与订阅 Form 4 交易流是不同的数据任务。
Use an issuer mapping that can survive ticker changes, multiple share classes, and non-US symbols. Store the resolved CIK with the mapping source and observation date. For form filters, decide whether variants such as 10-K/A and 8-K/A belong in the same result set or a separate amendment stream.
发行人映射应能处理股票代码变更、多类别股份和非美国代码，并保存解析后的 CIK、映射来源与观察日期。设置表格筛选时，还要先确定 10-K/A、8-K/A 等修订表格是并入原结果，还是进入单独的修订数据流。
Set a descriptive User-Agent with application and contact information, add a timeout, handle 429 and 5xx responses, cache unchanged data, and use exponential backoff. Do not treat the absence of an API key as permission for unlimited traffic.
设置包含应用与联系信息的说明性 User-Agent，配置超时，处理 429 与 5xx，缓存未变化的数据并使用指数退避。无需密钥并不代表可以无限请求。
Centralize request pacing across workers instead of throttling each process independently. Cache ticker mappings and immutable filing documents, use conditional requests where appropriate, honor Retry-After, and log status code, latency, URL, attempt count, and response size. A “free” integration that repeatedly downloads unchanged archives is neither reliable nor considerate.
多个工作进程应共享统一限流器，而不是各自独立控制频率。缓存股票代码映射与不可变申报文件，在适用时使用条件请求，遵守 Retry-After，并记录状态码、延迟、URL、尝试次数与响应大小。反复下载未变化归档的“免费”接入既不稳定，也不符合合理访问原则。
Store raw JSON and source URLs beside normalized fields. Keep accession numbers as stable filing identifiers, distinguish filing date from report period, and preserve amendments rather than silently overwriting earlier records.
把原始 JSON 与来源 URL 和标准化字段一起保存。使用 accession number 作为稳定文件标识，区分申报日期与报告期，并保留修订记录，不要静默覆盖旧版本。
Run a small evaluation set before production: one issuer with decades of history, one recent IPO, one company with multiple share classes, one amended filing, one filing with many exhibits, and one tagged fact reported in different units or contexts. Compare counts and identifiers with EDGAR, inspect source links manually, then test incremental updates and replay after a simulated outage.
上线前应准备一组小型评测样本：一家历史很长的发行人、一家近期 IPO 公司、一家拥有多类别股份的公司、一份修订文件、一份附件较多的申报，以及一个在不同单位或上下文中出现的 XBRL fact。先与 EDGAR 核对数量与标识并人工检查来源链接，再测试增量更新和模拟故障后的重放。
QVeris helps developers and AI agents discover and inspect available data capabilities. In the QVeris tool details, search by job rather than by a single provider name: “latest 8-K metadata,” “10-K risk-factor text,” “company facts by CIK,” or “Form 4 transactions.” Inspect required identifiers, output schema, source links, freshness, and provider requirements before an agent calls a capability. Keep the official EDGAR identifier in downstream records so a normalized result remains independently verifiable. See the QVeris documentation for the capability workflow.
QVeris 帮助开发者与 AI Agent 发现并检查可用的数据能力。在 QVeris 工具详情中，建议按任务而不是只按服务商名称搜索，例如“最新 8-K 元数据”“10-K 风险因素正文”“按 CIK 查询公司事实”或“Form 4 交易”。Agent 调用前应检查必填标识、输出字段、来源链接、更新频率和服务要求；下游记录还应保留 EDGAR 官方标识，使标准化结果可以独立核验。能力调用流程可参考 QVeris 文档。
Yes. Official EDGAR data access does not require a paid subscription or API key. The tradeoff is that you build more of the issuer mapping, archive retrieval, parsing, caching, and monitoring layer yourself. A commercial “free API” usually limits requests, history, endpoints, or production use.
Choose EDGAR when authority, complete source documents, and control matter most. Evaluate a third-party layer when normalized schemas, search, section extraction, SDKs, or alerts save meaningful engineering time. Test both with the same forms, dates, and amendment cases.
Official filing records are organized around CIK rather than ticker. Resolve ticker to CIK first, preserve the mapping source and date, and expect ticker changes or multiple share classes. Some third-party APIs perform this step, but the resolved CIK should still be visible.
No. Submissions describe filing history and document metadata. XBRL endpoints expose tagged facts with concepts, units, periods, forms, and filing contexts. Full narrative disclosures and exhibits remain in filing documents.
Test recent and old filings, amendments, exhibit-heavy documents, multiple share classes, missing optional fields, and an incremental update after a known filing. Verify accession numbers and source URLs against EDGAR, then measure latency, quota behavior, and recovery after errors.
Keep CIK, accession number, form and amendment status, accepted timestamp, filing date, report period, primary document, official URL, retrieval time, provider, and raw-response version. For extracted facts or text, retain the source location and transformation version.
有。官方 EDGAR 数据接口无需付费订阅或 API 密钥；代价是股票代码映射、归档下载、解析、缓存与监控等能力需要自行建设。商业服务所称的“免费 API”通常会限制请求量、历史范围、可用端点或生产用途。
如果最看重权威原文、完整附件与自主控制，优先选择 EDGAR；如果统一字段、全文搜索、章节提取、SDK 或提醒能明显节省工程时间，可以评估第三方服务。两种方案都应使用相同的表格、日期与修订案例测试。
官方申报记录以 CIK 为核心，而不是以股票代码为核心。应先把 ticker 解析为 CIK，保留映射来源与日期，并考虑代码变更和多类别股份。第三方 API 可以代做这一步，但响应中仍应显示最终使用的 CIK。
不是。submissions 描述申报历史与文件元数据；XBRL 端点提供带有概念、单位、期间、表格和申报上下文的标签化事实。完整的叙述性披露与附件仍位于申报正文中。
样本应覆盖近期与较早文件、修订申报、附件较多的文件、多类别股份、缺失可选字段，以及已知新申报后的增量更新。先用 EDGAR 核对 accession number 与来源 URL，再测试延迟、额度行为和错误恢复。
至少保留 CIK、accession number、表格与修订状态、受理时间、申报日、报告期、主要文件、官方 URL、抓取时间、数据服务商及原始响应版本。对提取后的事实或正文，还要记录来源位置与转换版本。
