Choose a Free Shareholder Data API选择合适的免费股东数据 API

Define the ownership question before choosing a shareholder API选择股东数据 API 前先明确所有权问题

Developers usually want a usable endpoint rather than a definition: query a company or security, identify disclosed owners, retrieve ownership amounts or percentages, and trace each result to a filing or registry record. The first decision is the dataset, not the vendor. A public-company investor page, an institutional-holdings screen, a KYB ownership graph, and a private-company cap table require different sources and legal definitions.

开发者通常需要的是可直接调用的接口，而不只是概念解释：按企业或证券查询公开披露的所有者，获取持股数量或比例，并把每条结果追溯到申报或登记记录。第一步应先确定数据集，而不是先选供应商。上市公司股东页面、机构持仓筛选、KYB 股权穿透图和非上市公司股权表分别依赖不同来源与法律定义。

No public API should be assumed to provide a complete, live list of every ultimate human owner. Securities may be held through nominees, custodians, funds, trusts, or layered companies; disclosures can be threshold-based, periodic, jurisdiction-specific, private, or legally restricted. A high-quality API exposes source scope, effective dates, ownership path, confidence or unresolved links, and the reason a person or entity appears in the result.

不能默认任何公共 API 都能提供完整、实时的最终自然人所有者名单。证券可能通过名义持有人、托管机构、基金、信托或多层公司持有；披露又可能受持股门槛、申报周期、司法辖区、隐私与法律限制影响。高质量接口应说明来源范围、生效日期、股权路径、置信或未解析环节，以及某个人或实体为何出现在结果中。

Free shareholder data API coverage and ownership types免费股东数据 API 的覆盖范围与股东类型

A shareholder endpoint may offer ticker or company lookup, institutional holders, beneficial owners, registered members, ownership percentages, historical filings, or corporate ownership chains. These labels do not establish equivalence. Record the governing source, disclosure threshold, included owner types, security or share class, geographic coverage, observation date, and whether the dataset represents reported, registered, inferred, or calculated ownership.

股东接口可能支持按证券或企业查询机构持有人、受益所有人、登记股东、持股比例、历史申报或企业股权链，但名称相似不代表口径相同。应记录主管来源、披露门槛、纳入的股东类型、证券或股份类别、地域覆盖、观察日期，以及数据属于申报、登记、推断还是计算结果。

How to compare free shareholder data API options如何比较免费的股东信息接口

Reconcile ownership percentages, sources, and unknown states勾稽持股比例、来源与未知状态

Worked indirect-ownership example间接持股计算示例

Assume Company A owns 60% of Company B, and Company B owns 40% of Company C. Along that path, A's derived economic interest in C is 60% × 40% = 24%. If A also directly owns 5% of the same share class in C, a simple model may report 29%—but only when both records use compatible effective dates, denominators, ownership definitions, and share classes.

假设 A 公司持有 B 公司 60%，B 公司持有 C 公司 40%，那么沿这条路径计算，A 对 C 的间接经济权益为 60% × 40% = 24%。如果 A 还直接持有 C 同一股份类别的 5%，简单模型可以得到 29%；但前提是两条记录的生效日期、分母、所有权定义和股份类别彼此兼容。

Do not automatically add parallel paths. They may represent voting rights versus economic rights, joint control, nominee holdings, duplicate registry records, or the same interest disclosed by several sources. Preserve each edge, path formula, source, effective period, and confidence before publishing a consolidated percentage. Circular ownership also requires a declared calculation method rather than repeated multiplication until an arbitrary cutoff.

平行路径不能自动相加，因为它们可能分别代表投票权与经济权益、共同控制、名义持有、重复登记，或同一权益被多个来源披露。发布合并比例前，应保留每条关系、路径公式、来源、生效期间和可信状态。遇到循环持股时，也必须采用明确的计算方法，而不是持续相乘到某个任意截止点。

Different disclosures can describe different owner populations不同披露可能描述不同的股东范围

A mismatch among these sources is therefore a reconciliation task, not immediate proof that one provider is wrong. Compare issuer, security class, denominator, effective date, filing date, legal ownership concept, and amendment status before choosing a preferred record.

因此，不同来源的名单不一致首先属于口径勾稽问题，不能立即认定某个供应商出错。选择优先记录前，应比较发行人、证券类别、分母、生效日期、申报日期、法律所有权概念和修订状态。

Represent unknown ownership states explicitly明确表示未知的所有权状态

Free shareholder data API integration steps免费股东数据 API 的接入步骤

import os, requests

response = requests.get(
    "https://provider.example/v1/shareholders",
    headers={"Authorization": f"Bearer {os.environ['API_KEY']}"},
    params={"company_id": "KNOWN_ID", "period": "2026-Q1"},
    timeout=20,
)
response.raise_for_status()
for row in response.json().get("results", []):
    required = {"owner_id", "company_id", "reported_at", "source_id"}
    if not required.issubset(row):
        raise ValueError("Unexpected shareholder schema")

The hostname and identifiers are illustrative. Replace them with the provider’s documented endpoint and identifier scheme.

以上域名与标识仅用于说明请求结构，请替换为服务商文档中的真实端点和标识体系。

How QVeris helps discover shareholder data capabilitiesQVeris 如何帮助发现股东数据能力

• Open the QVeris tool details by ownership type, market, or company-data capability.
• Inspect authentication, identifiers, response fields, limits, and provider terms before use.
• Use the QVeris documentation to connect a verified capability to an app or agent.

• 在 QVeris 工具详情中按股东类型、市场或企业数据能力搜索。
• 调用前检查鉴权、标识、返回字段、限额和服务商条款。
• 参考 QVeris 文档，把已验证的能力接入应用或智能体。

Frequently asked questions常见问题

Authoritative references权威参考资料