Skip to main content
The financial metric catalog is Rangler’s reference list of standard financial fields and calculation rules. It explains what each API key means, how its values are measured, and how each ratio or growth figure is calculated. The current catalog contains 145 metrics, 56 ratios, 6 unit formats, and 2 growth calculations.

Income statement metrics

Income, expense, profit, banking, insurance, and per-share concepts.

Balance-sheet metrics

Assets, liabilities, equity, reserves, deposits, and share counts.

Cash-flow metrics

Operating, investing, financing, and capital-expenditure cash flows.

Ratios and formulas

Profitability, returns, leverage, liquidity, banking, and valuation formulas.

Growth calculations

Supported growth periods, formulas, required metrics, and API formats.

​
Metric availability by company

The catalog covers every supported company type, but a company response contains only the metrics supported by its filings and reporting model. A bank can return net_interest_income while an industrial issuer can return revenue and gross_profit. These standard metrics do not replace issuer wording. Use reported tables when you need every printed line item or the exact label from a filing.
A metric definition explains what the value represents. Check metric_origins to learn whether a specific value came directly from a filing, was calculated from other line items, or was built from other periods.

​
Unit conventions

​
Retrieve the catalog through the API

Your application can fetch metric and ratio definitions separately:
The definition lists are the same for every company. Use them to find available keys, format values, check formulas, and record which version produced a response. Use /v1/financials/metric-catalog only if you want both lists and growth definitions in one response. Current generated catalog version: sha256:869de4ef677e32d8c23f8315fd3001244cb18d12ee00af7512ef554cfe46267f.

​
Versioning and caching

Every standardized statement response includes catalog_version. This value identifies the exact set of definitions used for that response. Cache the definitions under that version and fetch them again only when the version changes. Keep older versions if you need to recreate a previous export.