Monetary Authority of Macao Exchange Rate API: Official MOP Rates as JSON

The Monetary Authority of Macao publishes the official exchange rates that accounting, tax, and customs practice in Macao 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 amcm-exchange-rate npm package.

A peg you can see in the data

The pataca has been pegged to the Hong Kong dollar at 1.03 since 1977, and the AMCM table shows it: the HKD row prints 1.03 day after day, while the USD row tracks Hong Kong’s own dollar peg at just over 8 patacas. Every other currency moves — which is what a reconciliation between MOP books and foreign invoices actually needs.

Why official rates, not market rates

A live mid-market feed answers "what is USD/MOP 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 Monetary Authority of Macao’s published rates, and it never changes after publication.

Get the latest rates (REST)

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

The response is the bank's most recent published table — 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 amcm-exchange-rate

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

// One pair at the official rate
const pair = await getRate('USD', 'MOP', { 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 'amcm-exchange-rate';

const day = await getRatesForDate('2026-08-18', { apiKey: 'art_live_...' });

const series = await getHistory(
  { source: 'USD', target: 'MOP', 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 Monetary Authority of Macao does not print a pair directly, the API resolves it from the bank's published rates — an inverse, or a cross via MOP — 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 archive

The interbank middle-rate series reaches back to January 1999 — the year Macao returned to China — and we hold every published day of it, including currencies that have since left the table.

FAQ

Does the Monetary Authority of Macao have an official exchange rate API?

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

How do I get the official Macao exchange rate for a past date?

The rates-for-date endpoint returns the official table for any archived date; non-publication days resolve to the most recent published date and are flagged, so audit trails stay honest. Historical dates require a paid plan; latest rates are free.

Why does the AMCM table barely move for USD and HKD?

Because of the currency board: MOP is pegged to HKD at 1.03, and HKD is pegged to USD. The peg rows are stable by design; the other ~15 currencies move daily.