Central Bank of Uzbekistan Exchange Rate API: Official UZS Rates as JSON

The Central Bank of Uzbekistan publishes the official exchange rates that accounting, tax, and customs rules in Uzbekistan reference — published official rates, not moving market prices. This guide shows how to pull them as JSON: via a REST endpoint or the zero-dependency cbu-exchange-rate npm package.

What the CBU publishes

• ~75 currencies against the som — one of Central Asia's broadest official tables.
• History back to 2016 — queryable by exact date or as a time series.
• The bank's own publication date on every response, so a rate is always citable.
• No gaps to trip over — weekends and Uzbek holidays resolve to the most recent published rates and are flagged explicitly.

The USD/UZS rate anchors the table: Uzbek tax, customs, and accounting conversion all cite the CBU official rate.

Why official rates, not market rates

A live mid-market feed answers "what is USD/UZS trading at right now?" — the right tool for checkouts and dashboards. But accountants, auditors, and tax authorities ask a different question: "which rate were you required to use for this date?" That answer comes from the Central Bank of Uzbekistan's published rates, and it never changes after publication.

Get the latest rates (REST)

curl "https://allratestoday.com/api/v1/central-bank/cbu/latest" \
  -H "Authorization: Bearer YOUR_API_KEY"

The response is the bank's most recent published data — every rate and the publication date. The latest rates are available on every plan, including the free tier (300 requests/month, no credit card).

The npm SDK

npm install cbu-exchange-rate

import { getRate, getLatestRates } from 'cbu-exchange-rate';

// One pair at the official CBU rate
const pair = await getRate('USD', 'UZS', { apiKey: 'art_live_...' });
console.log(pair.rate, pair.rate_date);

// The bank's full published table
const table = await getLatestRates({ apiKey: 'art_live_...' });
console.log(table.rate_date, table.rates.length);

Zero dependencies, TypeScript types included, and it runs anywhere fetch exists — Node 18+, Bun, Deno, and edge runtimes.

Historical rates for an invoice date

import { getRatesForDate, getHistory } from 'cbu-exchange-rate';

// The official rates for an invoice date — non-publication days return
// the most recent published date, flagged via published_on_requested_date.
const day = await getRatesForDate('2026-06-30', { apiKey: 'art_live_...' });

// Time series for one pair
const series = await getHistory(
  { source: 'USD', target: 'UZS', from: '2026-01-01' },
  { apiKey: 'art_live_...' }
);

Historical dates and time series need a paid plan; the latest rates stay free.

Published vs derived pairs

If the CBU does not print a pair directly, the API resolves it from the bank's published rates — an inverse, or a cross rate via UZS — and flags it derived: true with the method used. Official and computed values are never silently mixed, which is exactly the distinction an auditor will ask about.

The series that captured a liberalization

Our archive starts in 2016 — which means it contains one of the most dramatic single prints in any official series: September 2017, when Uzbekistan liberalized its currency regime and the official som rate devalued roughly 48% overnight, from about 2,866 to 8,100 per dollar. The managed drift past 12,000 since is all there too, one official print per day.

FAQ

Does the Central Bank of Uzbekistan have an official exchange rate API?

The CBU publishes its official rates on its own site, and AllRatesToday serves the same published rates as clean JSON via REST or the cbu-exchange-rate npm package. The latest table is free.

How often do Central Bank of Uzbekistan rates update?

Once per business day, Tashkent time. These are published official rates, not moving market prices — every API response carries the publication date so you can cite it.

Can I get the CBU rate for a past date, like an invoice date?

Yes. The /central-bank/cbu/rates-for-date endpoint returns the official rates for any archived date. Non-publication days resolve to the most recent published date and are flagged, so your audit trail stays honest. Historical dates require a paid plan; latest rates are free.