Integration workflows
Complete ticker-to-financials and filing-to-source request flows with real response examples.
Standardized statements
Consistent metric names, fiscal periods, ratios, currency controls, and optional filing sources.
Exact reported tables
The filing’s original row labels and columns, including statements of changes in equity.
Units and currency
Base-unit amounts, decimal percentages, share counts, and explicit FX conversion metadata.
Financial metric catalog
Definitions for metric keys, units, ratios, formulas, and required inputs.
data scope.
Start with a statement
company parameter accepts a ticker or Rangler company UUID. countryCode is optional when the ticker identifies only one company. Send the ISO 3166-1 alpha-2 market code when a ticker is ambiguous across markets. An unresolved ambiguity returns 409 with code = "ambiguous_ticker".
Use these focused routes for common requests:
Request each statement section separately. This keeps response time and payload size predictable, and lets you cache income statements, balance sheets, cash flows, ratios, and revenue segments independently.
Pick the right representation
Standardization does not replace the reported filing. It gives equivalent financial concepts consistent names while keeping links to the source value. See Reported and calculated values to understand how each value was produced.
Response-size defaults
Standardized endpoints omit embedded metric definitions by default and return compact filing references. Theircatalog_version identifies the metric definitions used to construct the response; cache those definitions separately instead of downloading them with every company.