Free 13F API
for SEC Holdings Data免费 13F API
SEC 机构持仓数据接入
Use a free 13F API or SEC source data to retrieve filings, normalize XML holdings into JSON, preserve amendments, and build an auditable point-in-time workflow.
使用免费 13F API 或 SEC 来源数据获取申报、把 XML 持仓标准化为 JSON、保留修订，
并建立可审计的时点化数据流程。
TL;DR核心结论
The lowest-cost source-first route is to use public SEC EDGAR filings and Form 13F datasets, then build your own parsing, identity mapping, versioning, and quality controls. A free vendor API can reduce that engineering work by exposing normalized JSON, ticker search, reverse holder lookup, and historical aggregation. Evaluate the value of the normalization—not merely whether an endpoint costs zero.
成本最低、来源最直接的路径，是使用 SEC EDGAR 公开申报和 Form 13F 数据集，再自行完成解析、身份映射、版本管理和质量控制。免费的第三方 API 可以通过标准化 JSON、股票代码查询、反向持有人查询和历史聚合来减少工程工作量。评估时应关注标准化带来的实际价值，而不能只看接口价格是否为零。
Keep the filing as the authority. A Form 13F submission can include a cover page, summary page, and information table, while holdings, notice, combination, and amendment forms require different handling. The API should expose enough filing identity and source evidence to reconcile every normalized row back to the correct submission version.
原始申报应始终作为权威依据。Form 13F 提交可包含封面、摘要页和信息表，而持仓报告、通知报告、组合报告及其修订需要不同处理。接口必须提供足够的申报身份与来源证据，使每条标准化记录都能追溯到正确的提交版本。
A free 13F API should return structured institutional holdings and preserve links or identifiers back to SEC filings.
Test manager portfolios by CIK and stock holders by CUSIP or ticker before committing to a provider.
13F is quarterly and filed after period end under the applicable deadline; fast parsing does not make the underlying positions real time.
Compare free quota, history, amendments, pagination, identifiers, licensing, and source traceability.
免费 13F API 应返回结构化机构持仓，并保留可追溯到 SEC 原始申报的链接或标识。
选择前分别测试按 CIK 获取机构组合，以及按 CUSIP 或股票代码查询持有人。
13F 按季度披露，并在期末后按照适用期限提交；解析速度再快，也不能把底层仓位变成实时数据。
比较免费额度、历史范围、修订、分页、标识符、许可和来源可追溯性。
Free 13F API data, fields, and filing timing免费 13F API 的数据、字段与申报时点
Form 13F is filed by qualifying institutional investment managers to disclose specified Section 13(f) securities. A developer-oriented API turns EDGAR submission metadata, cover and summary data, and XML information-table rows into queryable records while retaining report period, filing and amendment times, accession number, form type, reporting-manager relationships, and source document URLs.
Form 13F 由符合条件的机构投资管理人提交，用于披露规定范围内的 Section 13(f) 证券。面向开发者的接口会把 EDGAR 提交元数据、封面与摘要信息以及 XML 信息表记录转换为可查询数据，同时保留报告期、提交与修订时间、申报编号、表单类型、共同申报机构关系和来源文件链接。
Query 13F holdings by manager CIK
A manager-centric endpoint should return every disclosed position for one report period, paginate complete portfolios, and distinguish amendments from original filings.
Find institutional holders by ticker or CUSIP
A security-centric endpoint reverses the filing data to list reporting managers. Ticker support is convenient, but CUSIP, issuer class, and mapping provenance reduce false joins.
Validate the 13F holdings JSON response
Keep manager name and CIK, issuer, title of class, CUSIP, shares or principal amount, reported value, put/call flag, discretion, voting authority, report period, filed date, and accession number when available.
Parse filing structure before holdings rows
Identify 13F-HR, 13F-NT, combination reports, and amendments before treating an empty or partial information table as a portfolio. Capture other reporting managers and confidential-treatment indicators from the filing context.
Version value units and identifier rules
Historical filings and current forms can follow different value conventions. Preserve source units and filing-era rules, store CUSIP as text, and retain optional FIGI separately when present rather than replacing the source identifier.
按机构 CIK 查询 13F 投资组合
面向机构的端点应返回同一报告期内的全部披露持仓，支持完整分页，并区分原始申报与修订。
按股票代码或 CUSIP 查询机构持有人
面向证券的端点会反向聚合申报数据。股票代码查询更方便，但应同时保存 CUSIP、证券类别与映射来源，减少错误关联。
验证 13F 持仓 JSON 返回字段
可用时应保留机构名称与 CIK、发行人、证券类别、CUSIP、股数或本金、申报市值、看跌或看涨标记、投资权限、投票权、报告期、申报日期和申报编号。
先解析申报结构，再处理持仓行
在把空白或不完整的信息表解释为组合前，应先识别 13F-HR、13F-NT、组合报告和修订，并从申报语境中提取其他申报机构与保密处理标记。
对市值单位和标识规则进行版本化
历史申报与当前表单可能采用不同的市值约定。应保留来源单位及对应年代规则，把 CUSIP 按文本保存；存在 FIGI 时单独保留，不能用它替换来源标识。
Compare free SEC 13F API access options比较免费的 SEC 13F API 接入方式
| Option方式 | What you get可获得内容 | Check first优先核对 | Best use适用场景 |
|---|---|---|---|
| SEC source data | Public filings, submissions metadata, filing documents, and quarterly 13F data sets.公开申报、提交元数据、申报文件与季度 13F 数据集。 | User-Agent policy, parsing work, identifiers, and update process.User-Agent 规范、解析工作、标识符和更新流程。 | Auditable source-first pipelines.重视原始来源与审计的数据管道。 |
| Free vendor plan | Normalized JSON, ticker lookup, pagination, and sometimes historical quarters.标准化 JSON、股票代码查询、分页，部分包含历史季度。 | Request quota, history, licensing, amendment handling, and attribution.请求额度、历史、许可、修订处理和署名要求。 | Prototypes and small research tools.原型和小型研究工具。 |
| Sandbox or evaluation | Limited institutions, quarters, or sample responses for integration testing.有限的机构、季度或样例返回，用于接入测试。 | Whether production use and complete coverage require payment.生产使用和完整覆盖是否需要付费。 | Schema and client validation.字段结构和客户端验证。 |
| Source plus local normalization来源数据加本地标准化 | Immutable SEC files plus your own parsed tables, ticker mapping, and versioned snapshots.不可变 SEC 文件，加上自行解析的表、代码映射和版本化快照。 | EDGAR access policy, XML variants, form structure, QA ownership, storage and maintenance.EDGAR 访问规范、XML 变体、表单结构、质量责任、存储和维护。 | Teams that need control, reproducibility, and source completeness.需要控制力、可复现性和来源完整性的团队。 |
Interpret and compare 13F holdings without creating false signals正确解读和比较 13F 持仓，避免制造错误信号
Worked timeline: report period, filing date, and amendment date时间线示例：报告期、提交日与修订日
Assume a manager's positions are measured at December 31, the original 13F is filed on February 14, and an amendment is filed on March 1. A point-in-time query as of January 31 must not expose either filing. A query as of February 20 may use only the original submission, while a query as of March 5 may use the amendment but should still retain the superseded version and explain what changed.
假设某机构的持仓时点为 12 月 31 日，原始 13F 于 2 月 14 日提交，修订申报于 3 月 1 日提交。那么，以 1 月 31 日为分析时点的查询不能看到任何一个版本；以 2 月 20 日为时点，只能使用原始申报；以 3 月 5 日为时点才可以使用修订版，同时仍应保留被替代版本并说明改动内容。
This distinction matters in backtests and historical screens. Key the observation by report period, but gate availability by the public filing timestamp. Keep the accession number, form type, amendment type, accepted timestamp, retrieval timestamp, and the version-selection rule. Replacing every historical quarter with the newest corrected file introduces information that was not available at the earlier decision date.
这一差异对回测和历史筛选尤其重要。记录可以按报告期归档，但是否可用必须由公开提交时间决定。应保存申报编号、表单类型、修订类型、SEC 接收时间、获取时间和版本选择规则。如果直接用最新修订文件覆盖所有历史季度，就会把当时尚未公开的信息带入过去的决策时点。
A change in reported value is not automatically a trade申报市值变化不一定代表机构发生交易
Suppose a manager reports 1,000,000 shares worth 50 million USD in one quarter and the same 1,000,000 shares worth 60 million USD in the next. The 20% value increase may come entirely from the security's price. A holdings-change calculation should compare split-adjusted share or principal amounts first, then explain value changes separately.
假设某机构第一季度申报持有 100 万股、价值 5000 万美元，下一季度仍是 100 万股、价值变为 6000 万美元。这 20% 的市值增长可能完全来自股价上涨。计算持仓变化时，应优先比较经过拆股调整的股数或本金数量，再单独解释市值变化。
Before labeling a position new, increased, reduced, or exited, align CUSIP, issuer, title of class, put/call status, and reporting-manager scope. Corporate actions, identifier changes, class conversions, mergers, and ticker remaps can otherwise look like a sale followed by a new purchase. Keep both the source identity and the mapping decision so the result can be reversed.
在把仓位标记为新建、增持、减持或清仓前，应对齐 CUSIP、发行人、证券类别、看涨/看跌标记和申报机构范围。公司行动、标识变更、类别转换、并购和股票代码重映射，否则可能被误判成“卖出旧证券后买入新证券”。来源标识与映射决策都要保留，便于复核和撤销。
What a 13F portfolio does not show13F 持仓不能展示什么
Cash, short positions, many derivatives, non-reportable securities, and assets outside the Section 13(f) list may be absent. Net exposure and leverage cannot be inferred from long holdings alone.
The filing describes a quarter-end snapshot disclosed later. The manager may have changed or closed a position before the filing became public.
Notice and combination reports, other reporting managers, shared discretion, and confidential treatment can change who reports a position and whether the visible table is complete.
现金、空头仓位、许多衍生品、非申报证券以及不在 Section 13(f) 清单内的资产可能缺失。仅凭多头持仓无法推断净敞口和杠杆。
申报展示的是更早季末的快照，机构可能在文件公开前已经调整甚至清空仓位。
通知报告、组合报告、其他申报机构、共享投资权限和保密处理都会影响由谁申报，以及当前可见信息表是否完整。
When aggregating related managers, use reporting relationships from the filing instead of matching names. Deduplicate only when the same economic position is demonstrably reported through more than one relationship; preserve manager-level rows, voting authority, and investment discretion even when publishing a consolidated view.
汇总关联机构时，应依据申报中的机构关系，而不是只做名称匹配。只有能够证明同一经济持仓通过多个关系重复申报时才去重；即使对外展示合并结果，也应保留机构级记录、投票权和投资决策权限。
How to integrate a free 13F holdings API如何接入免费的 13F 持仓 API
Step 1: test one manager and one security
Use a known manager CIK for a portfolio query and one CUSIP or ticker for a holder query. Confirm reporting period, pagination, empty-state behavior, and amendment flags.
Step 2: normalize identifiers and units
Store CIK and CUSIP as strings, keep the security class, confirm whether value is reported in dollars or thousands, and do not merge ticker mappings without provenance.
Step 3: preserve point-in-time history
Key records by report period and accession number. Ingest amendments as new source events, avoid overwriting older quarters, and compare only information available by each filing date.
Step 4: handle free-tier limits safely
Cache immutable filing responses, follow pagination, respect 429 and Retry-After, log retrieval time, and verify the provider's current production and redistribution terms.
Step 5: reconcile every filing version
Compare normalized row count and reported-value total with the source summary, keep unresolved rows, distinguish notice and combination reports, and apply amendments idempotently. A successful HTTP response is not a completeness check.
Step 6: build a point-in-time publication layer
Expose only filings public by the requested analysis time. Return period, filed and amendment timestamps, source accession, mapping version, and known omissions with each portfolio or holder result.
步骤 1：测试一个机构和一只证券
用已知机构 CIK 测试组合查询，再用一个 CUSIP 或股票代码测试持有人查询，核对报告期、分页、空结果与修订标记。
步骤 2：标准化标识符与单位
把 CIK 与 CUSIP 保存为字符串，保留证券类别，确认申报市值字段以美元还是千美元为单位，并保存股票代码的映射来源。
步骤 3：保留时点历史
以报告期和申报编号作为记录键，把修订作为新的来源事件写入，不覆盖旧季度；比较数据时，只使用在相应申报日期已经公开的信息。
步骤 4：安全处理免费额度
缓存不可变申报结果、遍历分页、遵守 429 与 Retry-After、记录抓取时间，并核对当前生产与再分发条款。
步骤 5：核对每个申报版本
把标准化行数和申报市值合计与来源摘要核对，保留未解析记录，区分通知与组合报告，并以幂等方式应用修订。HTTP 请求成功并不代表数据完整。
步骤 6：建立时点化发布层
只暴露在指定分析时点已经公开的申报。每次返回组合或持有人结果时，都应附带报告期、提交与修订时间、来源申报编号、映射版本和已知缺失。
How QVeris helps find 13F data capabilitiesQVeris 如何帮助查找 13F 数据能力
QVeris helps agents discover and inspect callable financial-data capabilities. For a 13F task, define whether the job is filing retrieval, manager portfolio, security holder lookup, or quarter comparison; identify whether the input is CIK, ticker, CUSIP, period, or accession; then inspect form coverage, amendment handling, pagination, source evidence, historical access, and provider terms before calling it.
QVeris 帮助智能体发现并检查可调用的金融数据能力。处理 13F 任务时，应先明确目标是获取申报、查询机构组合、按证券查持有人还是比较季度，并确定输入属于 CIK、股票代码、CUSIP、报告期还是申报编号；随后检查表单覆盖、修订处理、分页、来源证据、历史访问和供应商条款，再发起调用。
- Open the QVeris tool details to inspect the required inputs.
- Use the broader institutional holdings API guide when the task is ownership research rather than a 13F-specific developer integration.
- Verify provider coverage, pricing, licensing, and data accuracy against current documentation and the original SEC filing.
- 使用 QVeris 工具详情发现相关 API 能力并检查必填输入。
- 如果任务是更宽泛的机构持股研究，而不是 13F 开发接入，请查看机构持仓 API 指南。
- 服务商覆盖、价格、许可与数据准确性仍需对照当前文档和 SEC 原始申报验证。
FAQ
Is there a free API for 13F filings?
Yes. The SEC provides public EDGAR filing data, and some vendors offer free plans or sandboxes that normalize Form 13F holdings. Check quotas, history, licensing, and whether holdings are parsed.
Does the SEC have a 13F API?
SEC data endpoints and quarterly Form 13F data sets provide public source material, but developers may still need to retrieve filing documents and normalize holdings records.
Is 13F data real time?
No. It is a quarterly disclosure filed after period end under the applicable deadline. A provider can parse a new filing quickly, but the positions still describe an earlier quarter-end.
Which fields should a 13F holdings API return?
Useful fields include manager name and CIK, issuer, CUSIP, shares, reported value, security class, put or call status, report period, filing date, accession number, and amendment status.
Can I download historical 13F holdings as JSON?
Some APIs expose historical quarters or bulk JSON/JSONL downloads. Confirm coverage dates, amendments, point-in-time availability, quotas, and license terms before relying on them.
Why can a 13F filing have no holdings table?
A notice report may identify other managers reporting the positions, while combination reports split reporting. Inspect form type and filing relationships before interpreting an empty table as zero holdings.
How do I verify a normalized 13F API?
Reconcile source accession, form type, row count, reported-value total, amendments, and unresolved identifiers against the SEC filing. Test both a holdings report and a notice or combination case.
哪里可以免费获取 13F 数据？
可从 SEC EDGAR 与季度 Form 13F 数据集获取公开来源，也有服务商提供免费额度或沙盒。应核对历史、字段、请求限制和许可。
SEC 是否提供 13F API？
SEC 提供公开数据端点、申报文件和季度 13F 数据集，但开发者仍可能需要下载文件并标准化持仓记录。
13F 持仓数据是实时的吗？
不是。它属于在期末后按适用期限提交的季度披露。供应商可以快速解析新申报，但仓位仍对应更早的季末时点。
13F 数据接口应返回哪些字段？
常见字段包括机构名称与 CIK、发行人、CUSIP、股数、申报市值、证券类别、看跌或看涨标记、报告期、申报日期、申报编号与修订状态。
能否下载历史 13F JSON 数据？
部分接口提供历史季度或批量 JSON/JSONL。采用前应核对覆盖日期、修订、时点化访问、额度与许可。
为什么有些 13F 申报没有持仓表？
通知报告可能指明由其他机构代为申报，组合报告也会拆分申报范围。必须先检查表单类型和机构关系，不能把空表解释为持仓为零。
如何验证标准化 13F API？
应把来源申报编号、表单类型、行数、申报市值合计、修订和未解析标识同 SEC 原文核对，并同时测试持仓报告与通知或组合报告案例。
Authoritative 13F references and related guides13F 权威参考与相关指南
Use the SEC sources to verify filing obligations, timing, and original records. Vendor free plans and limits can change, so confirm them in current provider documentation.
使用 SEC 来源核对申报义务、时点与原始记录。服务商免费套餐和额度可能变化，应以当前官方文档为准。