Company financials API checks for quarterly US coverage

A company financials API should return quarterly US statements, keep each figure tied to a filing page, and surface the latest reported period cleanly enough to use in an application or workflow. If it cannot do those three things, it is not ready for source-backed research or production use.

We show the evaluation criteria from our own product view: quarterly data, US companies, fresh filings, and statements that can be traced back to the source page behind every number.¹

What a company financials API should return for quarterly US use cases

For quarterly US coverage, the first question is not whether an API returns a revenue figure. It is whether it returns the full statement context around that figure, with the reporting period, the filing source, and a consistent structure across the income statement, balance sheet, and cash flow statement.

Our Data API is a REST API for US and Nordic filings. It exposes search, key figures, financial statements, company profiles, comparison and screening, with citations in every response.¹ That matters because developers usually need more than one endpoint: they need one machine-readable path for the latest quarter, and a second path for the filing page that backs each figure.

The basic check is simple. Ask for the latest quarterly revenue, operating income, total assets, and operating cash flow for one US issuer. Then verify that the result is not just a number list, but a source-backed statement set that preserves the company’s own reporting format.

How to check whether the data is source-backed and traceable to filings

Source-backed data is not the same as downloaded data. For a financial statements API, source-backed means each figure can be opened against the report page it came from. In our product views, every figure links to the report page, and US filings link to SEC EDGAR.¹

In our MCP workflow, the same Nordic and US filings dataset is available in ChatGPT, Claude, Cursor and other MCP clients. The tools can search filings, pull financials, compare companies, screen the universe, and cite every number back to a source page, with authenticated access through OAuth.²

That matters for any workflow where the statement is not the endpoint. Product teams may need to store the data in a dashboard, while analysts may need to cite the source in a note or review. The API should make both possible without changing the underlying figure.

One practical test is to compare the API output against the report page for a recent quarter. If the API only returns a derived summary, it is harder to validate. If it returns the statement plus source page, you can verify the number directly and keep the chain intact for downstream users.

Why consistent statement formatting matters across income statement, balance sheet, and cash flow

Consistent formatting is not cosmetic. It is what lets you compare one company across periods, and one company against peers, without rebuilding the schema each time. On company pages, we show income statement, balance sheet and cash flow in one consistent format where the data is available.¹

For developers, that consistency reduces mapping work. For analysts, it reduces the chance that one quarter is read differently from another because the API rearranged the line items. It also helps when you are building a company financials API example in Python, because a stable schema makes it easier to join quarterly rows, display them in a table, and pass them to an internal report generator.

This is also where statement APIs differ from a simple ticker lookup or market data feed. A company financials API free trial may show a few headline values, but if it cannot keep the statement structure stable across quarters, it is not enough for workflow automation.

What to look for in coverage, history, and the latest reported period

We cover more than 7,000 public companies in the United States, Finland and Sweden, and US key metrics go back more than 10 years.¹ That makes the latest quarter easy to anchor against the longer history, instead of forcing a manual scrape of recent filings.

For quarterly US coverage, test three things in sequence.

1. Can the API return the latest reported period first, without you specifying a historical year?
2. Can it retrieve enough history to show context for the quarter, not just the latest line items?
3. Can it keep the source page attached as you move from one statement to another?

When you evaluate a company financials API github project, that order still applies. Open-source code can be useful for prototyping, but the real question is whether the data layer behind it can keep pace with fresh filings and preserve source traceability.

How to compare API access with assistant workflows in ChatGPT and Claude

One common way to work with company financials data is a direct API integration in your application. Another is an assistant workflow inside ChatGPT or Claude, where the assistant can search filings and pull financial statements during the conversation.

We support both access paths: the Data API and authenticated MCP access. Our MCP server exposes the same Nordic and US filings dataset that powers the Data API, but as Model Context Protocol tools instead of REST endpoints.²

For analysts, this is often the fastest way to answer a question such as: Which quarter is the latest reported period for this company, and what changed in the filing text? For developers, it is a useful way to validate the workflow before you hard-code the same logic into an application.

That question is better answered from filing-based statements than from a price page when you need reported quarterly figures.

A practical selection checklist for developers and analysts

Use this checklist before you build around a company financials API.

• Quarterly US statements are available for the latest reported period.
• Each figure can be traced to a filing page, not just a company summary.
• Income statement, balance sheet and cash flow use one consistent schema.
• Historical quarters are available for context, not only the latest quarter.
• The API can support both application workflows and analyst workflows.
• Fresh filings appear quickly enough to keep pace with reporting.

Worked example: In Lundin Gold’s 2024 Q4 interim report, the company says its quarterly financial statements are reported under IFRS Accounting Standards as applicable to interim financial reporting.³ The same wording appears in 2024 Q3 and 2024 Q2.⁵⁴ That is the kind of continuity an API should preserve when it surfaces the latest reported period: the period itself, the statement context, and the source page that supports the data.

For a workflow team, the practical next step is to test the API against one current quarter, one prior quarter, and one peer. If the response keeps the same schema and source trail across all three, it is much easier to use in a dashboard, a notebook, or an assistant workflow. If it does not, you will spend time repairing the output before you can use it.

For teams that want both direct access and assistant workflows, our Data API and MCP connector are built from the same source-backed filings layer. The difference is only how you want to consume it: in code, in a dashboard, or in a conversation.¹²

What to try next:

• Check whether your current API returns the latest reported quarter first.
• Verify that every statement line can be opened to a filing page.
• Compare one US issuer in a direct API call and in Claude or ChatGPT.