Inside the StockFit Earnings APIs: A Deep Dive

The StockFit Earnings APIs cover the full lifecycle of a public company's earnings cadence: when the next print lands, what the headline numbers were, how EPS has evolved, whether earnings convert to cash, what the multi-year trends look like, and what the dividend track record says. Eight endpoints, all parsed straight from SEC filings (10-K, 10-Q), all callable by ticker or CIK. To make this concrete, this post walks through each endpoint with one ticker as the canvas: The Coca-Cola Company (KO) — a 62-year dividend grower with one famously broken EPS year that perfectly demonstrates why these endpoints exist as a set rather than a single “earnings” call.

1. The one-call summary

Snapshot is the executive-summary endpoint. One call returns the most recent fiscal year's headline numbers — EPS, revenue, all three margin tiers, returns, free cash flow, growth rates, the Piotroski F-Score, and the predicted next earnings/filing dates. It's designed to be the single backing call for a leaderboard widget, a watchlist row, or an LLM prompt that needs to know “the current state” in a few hundred bytes.

KO — FY2025 snapshot

Twelve numbers, one HTTP call. The 23.5% EPS jump on 1.9% revenue growth is the headline — operating leverage and tighter share count both contributing. Snapshot also returns a Piotroski F-Score of 7/9 (a strong fundamental-quality reading) and the next predicted earnings date.

2. When does the company report?

Two endpoints share a job. Date returns the predicted next earnings date for one symbol; Calendar takes up to 50 symbols in a single call and returns the full set. Dates are predicted from each company's historical filing cadence (most US filers report on a tight rhythm), so they may shift by a day or two from the actual announcement.

KO — next earnings & filing

Calendar — KO peer beverage cluster

One call returned the full beverage-sector reporting calendar. Spread is wide: KO and the energy-drink names report in late April / early May, the bottler-heavy PEP and KDP not until mid-July. For portfolio-level dashboards, this batched format is what makes a real calendar widget cheap to build.

3. The full EPS trail

EPS History returns the per-period EPS series with both basic and diluted values, net income, the diluted share count, and year-over-year growth. Useful for charts, but more useful for the share-count column — that's where buyback effects on EPS become visible.

FY2017 stands out: EPS of $0.29, an 80.8% drop from the prior year — driven by the Tax Cuts & Jobs Act transition charge and bottler refranchising activity. FY2018 then bounced +421%. Either of those numbers in isolation is misleading, which is exactly why the next two endpoints exist.

4. Chart-ready EPS & net margin

EPS Chart returns the same data as EPS History but reshaped for visualization libraries: a periods array, parallel series arrays for absolute values (EPS, Net Income), and a rates array for derived percentages (Net Margin). Drop straight into Recharts, ECharts, or D3 without preprocessing.

Net margin trajectory (10-year)

Net margin nearly doubled from 15.6% to 27.3% across the decade, with FY2025 setting a new historical high (the trends endpoint confirms this with historicalMaxNetMargin: 27.3). Bottler refranchising structurally shifted the business mix toward higher-margin concentrate sales — the chart endpoint doesn't explain why, but it makes the shape obvious.

5. Multi-year CAGRs & margin direction

Trends compresses the multi-year picture into a single response: 3-year and 5-year CAGRs for revenue, net income, EPS, and free cash flow; margin direction (expanding / stable / contracting) computed against a 3-year-ago baseline; net-margin volatility (historical vs recent); and quality flags. This is the endpoint that sees through the FY2017 anomaly without you having to write the smoothing logic.

Two facts the trends endpoint surfaces directly: (1) all three margin tiers are expanding, and (2) the 5-year EPS CAGR (11.1%) is meaningfully ahead of the revenue CAGR (7.7%) — operating leverage at work. The endpoint also reports net-margin volatility of 6.2 historically vs 1.9 recently, signaling that the post-2017 business is structurally more stable than the longer-history numbers suggest.

6. Earnings quality — do they convert to cash?

Quality Chart juxtaposes net income with operating cash flow and free cash flow over time, plus the OCF/Net Income and FCF/Net Income ratios. A persistent ratio below ~0.8 is a textbook earnings-quality red flag (accruals running ahead of cash). It's the kind of derived signal that's annoying to compute on every chart but drives the most actionable alerts.

OCF/NI ran 1.0–1.3x for years, then dropped to 0.64x in FY2024 and 0.57x in FY2025. That's a real signal: net income is growing while cash from operations isn't keeping pace — a working-capital story worth understanding before reacting. The quality endpoint surfaces it without you needing to merge two financial statements together.

7. The dividend track record

Dividend History returns per-share dividend amounts, total dividends paid, payout ratio (dividends / net income), dividend coverage (operating cash flow / dividends paid), and year-over-year dividend growth. KO is a Dividend King with a 62-year increase streak; the endpoint exposes every dimension you'd want for a dividend-safety scorecard.

Two stories in one table. First, FY2017's payout ratio of 506%: the dividend didn't change, but the EPS denominator collapsed — a textbook case of why a single-year payout ratio can't be read in isolation. Second, dividend coverage (the ratio of operating cash flow to dividends paid) has tightened from 1.45x in FY2016 to 0.84x in FY2025. Below 1.0 means OCF alone no longer covers the dividend; the company is funding the gap from the balance sheet or financing.

The dividend itself, though, has gone up every single year on the table — 19 of 19 in this window. The endpoint's job is to surface both signals at once: the streak and the tightening coverage. Whether that's a concern is a judgment call; whether the data shows it should not be.

What you can build with this

Eight endpoints, one consistent shape (all keyed by symbol or cik, all returning JSON with a stable schema). A few small ideas that compose them:

The bottom line