Share Class and Voting Rights Data APIs for Capital Structure Analysis

Not all public company shares carry the same economic or voting rights. Some companies have multiple share classes, voting and non-voting shares, super-voting shares, preferred shares, or dual-class structures that separate ownership economics from corporate control.

That distinction matters. A simple share count may show how much equity is outstanding, but it may not explain who controls the vote, which shares are freely tradable, how market capitalization should be interpreted, or where an analyst needs to review company filings more closely.

Share class and voting rights data sits at the intersection of capital structure, governance, security identification, and filings research. APIs can help teams connect company profile data, share counts, float, market capitalization, identifiers, and filing records. Deeper voting-rights interpretation, proxy-voting behavior, and shareholder vote outcomes may still require proxy statements, prospectuses, governance datasets, or specialist proxy-voting platforms.

Key Takeaways

• Share class details and voting rights are related, but they are not the same.
• APIs can support company, share, float, market cap, identifier, and filing workflows.
• Voting rights may require filings, proxy statements, prospectuses, governance datasets, or proxy-voting platforms.
• Actual voting behavior and proxy outcomes are separate from share class structure.
• Financial Modeling Prep can support capital-structure and filings-context workflows, but it should not be treated as a full proxy-voting platform.

Why Share Class and Voting Rights Data Matters

Share class data helps analysts understand how a company's equity is structured. Voting rights data helps explain how control may be distributed across that structure.

A company may issue Class A shares with standard voting rights and Class B shares with enhanced voting rights. Another company may have non-voting shares, preferred equity, or multiple listed securities tied to the same issuer. In those cases, economic ownership and voting control may not move together.

This matters for several workflows:

• Governance analysis
• Capital structure review
• Security master management
• Market capitalization analysis
• Float and liquidity review
• Company research dashboards
• Ownership and control analysis

A dashboard that treats all share classes as interchangeable may misread the company's control structure. A valuation screen that ignores share-class differences may mix securities with different liquidity profiles. A governance review that uses float or share count alone may miss voting provisions that are only visible in filings.

Structured data helps reduce that risk. For example, company share float data can help teams review shares outstanding, float, and liquidity context. That is useful for understanding the economic side of the capital structure. It does not, by itself, explain voting power.

Share Class Details vs. Voting Rights Data

Share class details describe the security. Voting rights describe the control rights attached to that security. Actual voting behavior shows how those rights were exercised.

Those are three separate layers.

Share class data may include the security name, ticker, exchange, issuer, share class name, CUSIP, ISIN, share count, float, and security type. This is the structural layer. It helps teams identify what security they are looking at and how it relates to the broader issuer.

Voting rights data explains whether the shares vote, how many votes attach to each share, whether conversion rights exist, and whether special class-level voting provisions apply. This information may be found in prospectuses, proxy statements, charters, bylaws, or security descriptions.

Actual voting behavior is different again. It shows how shareholders, funds, or institutions voted on specific matters. That layer belongs more naturally to proxy-voting records, Form N-PX data, governance platforms, and shareholder meeting materials.

Keeping these layers separate is important. A share can be correctly identified without having its full voting provisions normalized into a database field. A share can carry voting rights without showing how the holder actually voted. A governance dashboard should not confuse security structure with proxy-voting outcomes.

Which APIs Include Share Class Details and Voting Rights Data?

Share class details and voting rights data are usually available through a combination of financial data APIs, filings APIs, institutional reference platforms, governance datasets, and proxy-voting systems.

Financial data APIs such as Financial Modeling Prep can support company, share, float, market cap, identifier, and filing-related workflows. These are useful for capital structure analysis, issuer mapping, company dashboards, and security-level context. Deeper voting-rights interpretation, proxy-voting records, and shareholder vote outcomes generally require governance datasets, proxy statements, Form N-PX records, or specialized proxy-voting platforms.

The right source depends on the question.

If the question is, “What securities are tied to this issuer?” company profile, symbol search, identifier, and filing data may be enough to begin the review.

If the question is, “How many shares are outstanding and how much float is available?” share and float data are more relevant.

If the question is, “Does this class carry one vote, ten votes, or no votes?” filings and governance data may be required.

If the question is, “How did shareholders vote on a proposal?” that is a proxy-voting or meeting-outcome workflow, not a standard capital-structure API workflow.

FMP is best positioned as part of the capital-structure and filings-context layer. It can help teams connect public-company data, identifiers, share and float context, market cap, financial statements, and filings. It should not be positioned as a full proxy-voting system or a definitive source for every class-specific voting provision.

What Data Fields to Look For in Share Class APIs

Share class and voting-rights workflows often require fields from several datasets. No single field usually explains the full capital structure or governance picture.

Useful share class fields may include:

• Issuer name
• Security name
• Ticker or trading symbol
• Exchange
• CIK
• CUSIP
• ISIN
• Share class name
• Security type
• Currency
• Issuer relationship

Useful capital structure fields may include:

• Shares outstanding
• Float
• Market capitalization
• Preferred equity, where relevant
• Class-level share count, where available
• Historical share count or float, where available

Useful voting-rights fields may include:

• Voting vs. non-voting status
• Votes per share
• Conversion rights
• Class-level voting limits
• Special voting provisions
• Proxy eligibility
• Historical vote records, where available

Useful filing context may include:

• Prospectuses
• Proxy statements
• Annual reports
• 10-K disclosures
• Security descriptions
• Corporate charters or bylaws, where needed

Teams should confirm which fields are actually available from a provider and which require filing review. Basic share and float data may be accessible through financial data APIs. Complex voting provisions often require reading the underlying disclosure.

Where Share Class and Voting Rights Data Comes From

Share class and voting-rights data begins with company disclosures.

Prospectuses, annual reports, proxy statements, security descriptions, charters, bylaws, and exchange records can all contain relevant information. These records may explain how many share classes exist, whether a class votes, how many votes are attached to each share, whether conversion rights exist, and whether certain holders have special control rights.

APIs can make this information easier to retrieve and connect, but the level of normalization varies. Some providers focus on structured company and security data. Some provide filing access. Some specialize in governance or proxy-voting data. Others focus on institutional security master workflows.

For FMP-based workflows, company profile data can provide issuer and listing context, while share float data can help analysts review shares outstanding, float, and liquidity context where available.

Market cap data adds economic scale. Financial statements add broader capital-structure context. Filings provide the source material analysts may need when class-level rights are not fully represented in a structured field. For example, market capitalization data can support equity value context, while the Balance Sheet Statement API can help connect share-class review to reported equity, preferred stock, and broader balance sheet structure.

The important point is that share class and voting rights analysis usually requires a connected view. Company metadata, share and float data, market data, filings, and identifiers all play different roles.

How Share Class Data Connects to Capital Structure Analysis

Share class data becomes more useful when it is connected to market cap, float, liquidity, identifiers, financial statements, and company-level context.

A company may have multiple securities tied to the same issuer. One class may be widely traded. Another may be closely held. One may vote. Another may not. A preferred security may have different rights than common equity. An ADR or dual listing may create another layer of mapping.

For analysts, this affects how ownership and control are interpreted. For data teams, it affects how securities are joined across datasets. For product teams, it affects how company dashboards display issuer-level and security-level information.

Identifier mapping is central to that work. CIKs, CUSIPs, ISINs, tickers, company names, and exchange symbols help teams connect the correct security to the correct issuer. A mismatch can create errors in market cap, float, ownership, or governance views.

When the workflow starts with an issuer identifier, CIK search can help connect filing context to the company record. When the workflow starts with a ticker or listed security, search by symbol can help confirm the correct company before joining market cap, float, filing, and profile data.

Teams may also need stock symbol search when dealing with changing symbols, secondary listings, or issuer-level mapping. These reference steps are not administrative details. They are what keep the capital-structure view tied to the correct company and security.

Challenges in Standardizing Share Class and Voting Rights Data

Share class and voting-rights data is difficult to standardize because companies disclose capital structure and governance rights in different ways.

Common challenges include:

• Multiple share classes tied to the same issuer
• Related tickers that represent different rights
• Voting and non-voting share classes
• Super-voting shares
• Preferred shares
• Dual listings and ADRs
• CUSIP and ISIN mapping issues
• Share reclassifications
• Conversions between preferred and common equity
• Stock splits that affect different classes differently
• Incomplete class-level fields
• Legal language embedded in filings
• Differences between voting rights and actual voting outcomes

A simple voting flag may not capture the full picture. A class may vote on ordinary matters but have special provisions for certain transactions. A preferred security may have contingent voting rights. A founder-controlled class may carry enhanced votes. These details often require review of the filing language.

That is why provider methodology matters. Teams should understand whether the data source is returning a structured field, a filing reference, a normalized governance interpretation, or a proxy-voting record. Those are not interchangeable.

FMP can reduce manual work by giving teams structured access to company data, identifiers, share and float context, market cap, financial statements, and filings-related records. Complex class rights and proxy-voting behavior may still require specialized governance sources or direct filing review.

Provider Categories for Share Class and Voting Rights Data

Share class and voting-rights data usually comes from several provider categories. The right choice depends on whether the workflow needs capital-structure context, source verification, security master coverage, legal interpretation, or proxy-voting records.

Provider Type	Best Fit	Typical Strength	Limitation
Financial data APIs	Capital structure and company-data integration	Company data, identifiers, share and float context, filings access, market data links	May not fully normalize all voting-rights provisions
Filings APIs and public disclosures	Source verification and rights detail	Prospectuses, proxy statements, security descriptions, official disclosures	Requires parsing and interpretation
Institutional reference platforms	Security master workflows and cross-market reference data	Broad symbology, class-level reference data, cross-market coverage	Higher cost and workflow complexity
Governance and proxy-voting platforms	Voting records, proxy workflows, and governance context	Deeper voting records, proxy workflows, governance context	More specialized and may not cover full market-data integration

Financial Modeling Prep fits in the financial data API category. It can support company metadata, identifiers, share and float context, market cap, financial statements, and filings-related workflows. It should not be treated as a complete governance database or proxy-voting platform.

What to Look For in a Share Class or Voting Rights Data API

When evaluating a share class or voting-rights data API, teams should first define the workflow they are trying to support.

A capital structure workflow may need company identifiers, share counts, float, market cap, and filings. A governance research workflow may need voting provisions, proxy statements, class-level control rights, and shareholder meeting materials. A proxy-voting workflow may need actual vote records, fund voting behavior, compliance records, and proposal-level data.

Useful evaluation criteria include:

• Company identifier support
• Security-level identifiers
• Ticker, CIK, CUSIP, and ISIN coverage
• Share class names
• Security type fields
• Voting vs. non-voting flags, where available
• Share count and float data
• Market cap data
• Filing access
• Historical availability
• Documentation quality
• Update cadence
• Cross-dataset joins
• Plan or tier availability, only if verified

Teams should also ask how the provider handles newly issued securities, conversions, reclassifications, symbol changes, dual listings, and delistings. A clean share-class workflow depends on the ability to maintain the relationship between issuer, security, filing, market data, and share count over time.

Most importantly, buyers should distinguish between share class data, voting rights data, and actual voting behavior. A provider may be strong in one layer and limited in another.

Building Reliable Share Class and Voting Rights Data Workflows

Reliable share class and voting-rights workflows require more than a single field. Teams need to connect company metadata, security identifiers, share and float data, market cap, filings, and governance-specific sources where needed.

FMP can support the capital-structure side of that workflow through API-accessible public-company data, identifiers, share and float context, market cap, financial statements, and filings-related records. Financial statement context can also matter when analysts need to review preferred equity, reported equity structure, or broader capital structure alongside the share-class view. For teams building this layer at scale, broader statement access through financial statement APIs can help connect share-class analysis with reported fundamentals.

That still leaves some work outside a standard financial data API. Deeper legal interpretation, proxy-voting behavior, shareholder vote outcomes, and proposal-level governance records may require specialist datasets or direct review of filings.

Share class and voting-rights data is most useful when it is treated as a connected capital-structure and governance workflow, not as an isolated field. The goal is to understand how securities, ownership economics, liquidity, and control rights fit together.

Frequently Asked Questions

What is the difference between share class data and voting rights data?

Share class data describes the structure of a security, such as its ticker, exchange, issuer, class name, security type, share count, and identifiers. Voting rights data explains the control rights attached to that class, such as votes per share, voting or non-voting status, conversion rights, or special class-level provisions.

Can financial data APIs show whether shares are voting or non-voting?

Some financial data APIs may provide security descriptions, class labels, or fields that help identify whether a share class is voting or non-voting. Complex dual-class structures, contingent rights, or special provisions may still require review of prospectuses, proxy statements, charters, bylaws, or governance datasets.

Where do voting rights details usually come from?

Voting rights details usually come from company disclosures. Prospectuses, proxy statements, annual reports, security descriptions, corporate charters, and bylaws may explain how voting rights attach to each class. APIs can help retrieve and connect these records, but legal or governance interpretation may require additional review.

Does share float data show voting power?

No. Share float data shows how many shares are available for public trading. It can help analysts understand liquidity and economic availability, but it does not show voting power by itself. Voting power depends on the rights attached to each share class and the ownership of those shares.

What is the difference between voting rights and actual voting behavior?

Voting rights describe what a shareholder is entitled to do. Actual voting behavior shows how those rights were used in a specific shareholder vote, board election, proxy proposal, or fund voting record. Those outcomes are usually handled through proxy-voting records, governance datasets, meeting results, or Form N-PX data.

When do teams need a governance or proxy-voting platform?

Teams usually need a governance or proxy-voting platform when they need proposal-level vote records, mutual fund voting behavior, shareholder meeting outcomes, proxy workflow tools, or compliance records. Standard financial data APIs are better suited for company data, identifiers, share and float context, filings access, and capital-structure analysis.