Skip to main content
Every standardized financial response includes rules for interpreting its values. Do not guess scale from a filing label or apply the website’s display formatting to raw API numbers.

Unit classes

Use the response’s unit_convention map and the financial metric catalog when interpreting a value. Each metric definition states its unit class and API format.
Never multiply every value by the filing’s printed thousands or millions label. Standardized currency values have already been converted to base units by Rangler.

Reported and display currency

Each period distinguishes:
  • reported_currency: the statement currency selected from the issuer’s filing
  • display_currency: the currency of monetary values returned in metrics
  • currency: a compatibility field for the period’s returned monetary and per-share values
With currency=native, reported and display currency are normally identical. With an ISO 4217 target, only monetary unit classes are converted.
currency_conversion records the rate and period date used. Conversion does not change whether an accounting value was reported or derived; that classification remains in metric_origins.

Selecting a native currency

Some company histories contain more than one reported currency. available_reported_currencies lists the valid native choices and selected_reported_currency records the selected lane.
Use currency=native to keep the statement currency. Send an ISO 4217 code such as NGN or USD to request a supported conversion. The response always states the selected reported and display currencies.

Display formatting belongs at the edge

The API owns unit semantics and conversion. A UI may abbreviate 1250000000 as 1.25bn or render 0.184 as 18.4%, but it must not change the underlying meaning. Preserve the raw number and unit metadata for exports and calculations.