Skip to content

Sources, units & freshness

A number is only useful when its meaning survives the integration. Keep source, reporting period, entity scope and currency attached to each financial fact.

Financial facts include the source document title, original source URL, document version and page number. Document excerpts include source URLs and a Fisk document link.

Present a source link near the metric or explanation it supports. Do not imply that a fact has been independently verified by your own product unless you have performed that review.

Financial value fields are decimal strings in base units. unit_multiplier records source provenance, so it must not be applied again.

Returned value Currency Display example
"1200000000" TZS TZS 1.2 billion
"2.75" TZS TZS 2.75, when appropriate to the measure

The examples above are illustrative. Use the actual metric definition to distinguish totals, per-share values and ratios.

Fisk API returns the reported currency. It does not automatically convert financial facts into a user’s preferred currency. If your application converts them, retain the original amount and disclose the exchange rate and date separately.

Annual, interim and point-in-time facts are not interchangeable. Compare compatible period_type, period_start and period_end values.

Group and standalone company figures may differ. Keep entity_scope visible, and retain the restated marker when supplied.

If two available facts use different definitions, show their distinction. Do not select a convenient value simply because it produces a smoother chart.

The gateway returns facts and pages from the active, ready document version. Replaced versions are excluded. Keep version identifiers if you store references so your integration can recognize a revision.

Timestamp or status What it tells you
meta.asOf When Fisk assembled the API result
Fact reporting dates The period the company reported
reviewed_at When a fact was reviewed
Document publication date/status Available publication context
Quote trading date and retrieval time When the quote traded and was retrieved
Event lifecycle Whether a date is confirmed or estimated

An API response generated today can contain a historical quote or a prior-year financial result. Do not label it “live” based on meta.asOf.

Use an explicit unavailable state for missing fields or empty results. Do not fill gaps with zeros, extrapolated values or fabricated source links.

For AI workflows, source text is untrusted input. Quote or summarize it as evidence; never treat embedded instructions as authority over the assistant.