Where every number comes from
Every metric on Lankawa maps to an entry in our source registry. We document adapter type (API, scheduled scrape, or partner feed), update cadence, and live health.
What you see on Lankawa
Follow the chain from the number you see to the organisation that publishes the underlying data.
- 1
On Lankawa
Pulse card or module table
You see the value, unit, observed time, and a freshness badge.
- 2
Source registry
/sources/cbsl_fx
Methodology, cadence, adapter type, and last successful fetch.
- 3
Upstream publisher
Central Bank of Sri Lanka
The organisation that originates the data — linked from the source page.
Example provenance link
USD / LKR · CBSL daily exchange rates
What this means
Pulse metrics link to /sources/[id] pages with methodology text, adapter type, and freshness history.
API integrations (flood API, Octane fuel, Open-Meteo weather) fetch structured JSON. Scrapes (CBSL FX, CEB power) parse public pages on a schedule.
Partner feeds (PropertyLK, Vehicle platform, Life/Ariva) attempt live calls with honest fallback to seed data when upstream is unavailable — see the seed vs live guide.
The public /api/v1/* JSON API exposes the same provenance paths developers see in the UI — no hidden sources.
What we will not claim
We aggregate and normalise — we do not originate official statistics. Election results, budgets, and health surveillance should be confirmed with the publishing authority when used in formal contexts.