Global Exchange Rates

Global Exchange Rates publishes currency rates from many named providers instead of one blended feed. Agents list currencies and providers, fetch latest and historical rates, and convert amounts with a source you can audit.

Verified 5 actions API key available

Global Exchange Rates website Platform Documentation Capability data verified 2026-08-25

The month end revaluation run starts for open foreign currency invoices

List Providers returns the sources available and what each one quotes against

The agent confirms the policy provider publishes history and accepts the base needed

Get Historical Rates pulls a rate for each invoice's own document date

The agent compares the date it asked for with the date the answer came back stamped with

Every invoice whose rate carries an earlier date than requested is listed with both dates

The controller decides which of those may stand on the prior published rate

What This Integration Enables

Most currency APIs answer the question "what is the rate". Global Exchange Rates answers "whose rate", which is a different and usually more useful question. It publishes the European Central Bank's figures, a national central bank's figures, and its own blended feed as separate named sources rather than folding them into one number. For accounting, tax, and contract work, the source of a rate is often the part that has to hold up under review, and this connector is built for the teams that have discovered that the hard way.

FlowRunner agents list the available currencies and providers, read what each provider quotes against and whether it carries any history at all, and pull latest or historical rates from the one your policy names. Convert Currency does the arithmetic at the source, so the amount and the rate come from the same provider at the same instant with the same rounding, which removes a class of penny differences that reconciliation work otherwise inherits. The connector is read only, so the judgment worth gating is not the lookup. It is the moment a rate becomes a figure in someone's books.

Without FlowRunner

One rate, no provenance A number arrives from a general purpose feed with nothing recorded about where it came from

Weekends papered over A Saturday invoice quietly gets Friday's rate and nothing in the record says so

Arithmetic in the workflow The rate is fetched, multiplied, and rounded somewhere downstream of the source

With FlowRunner

The source named on the record The provider code is stored beside the figure, so the number can be defended later

Missing dates raised, not filled A date the provider never published is flagged as a decision instead of substituted silently

Conversion done at the source The amount and the rate come back from the same provider at the same moment with the same rounding

Use Case Scenarios

Invoices valued at the rate that applied when they were issued

An invoice raised in a foreign currency needs a home currency figure, and the right rate is the one that applied on its document date rather than today's. The agent reads the open invoice list from NetSuite or Xero, calls Convert Currency with each invoice's own date and amount, and writes the converted figure back with the provider code stored alongside it. Because the conversion happens at the source, the rate on the record and the figure on the record cannot disagree. The provider code is what makes the entry answerable months later.
A daily rate table the whole stack reads from

Several systems each fetch their own rate and quietly disagree. Instead, one scheduled flow calls Get Latest Rates against the named policy provider each morning and writes a single table into Google Sheets, with the provider, the reference currency, and the timestamp in the header rows. Pricing, billing, and reporting all read that table. When the provider publishes nothing on a given morning, the flow leaves the previous row in place and posts a note into Slack rather than overwriting the table with a stale figure carrying today's date.
Choosing a provider before committing to it

Not every source is usable for every job. The agent calls List Providers and reads three fields on each: the reference currency it quotes against, whether it carries any time series at all, and whether it publishes bid and ask or only a midpoint. A provider with no history cannot serve a revaluation run. A central bank will refuse a base currency other than its own rather than silently computing a cross rate. The agent produces the shortlist and the reasons, and the treasury owner picks the provider that the accounting policy will actually stand behind.

Human-in-Loop Highlight

The riskiest thing this API does is answer helpfully. On Get Historical Rates, the Latest flag defaults to on, which means "the most recent rates up to this date", so asking for a Saturday quietly returns Friday's rate with Friday's date attached. Turn the flag off and a date the provider never published returns nothing at all. Neither answer is wrong, and neither is a decision. A valuation usually wants the most recent available figure. A contract that names a date usually means the rate published on that date, and substituting the day before changes what somebody agreed to. So the revaluation agent runs with the flag off, collects every date that came back empty, and stops. It posts: "Provider ECB published no rate for 2026-03-15 on 6 invoices totaling 84,200 EUR. The 2026-03-13 rate is the most recent before it. Apply that rate, or hold these six for manual valuation?" The controller answers once for the batch. The digital andon cord here is not about the lookup failing. It is about a number nobody chose ending up in the ledger.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

5 actions

Reference

List Currencies Returns the ISO 4217 currency list with each currency's numeric code and whether it is obsolete. The obsolete flag matters for historical work, since a currency that no longer exists still has rates on old dates.
List Providers Returns the rate sources available, from named central banks to the vendor's own blended feed. Three fields decide whether a provider fits the job: what it quotes against, whether it has any history, and whether it publishes bid and ask.

Rates

Get Latest Rates Returns the most recent rates from one provider. A base currency other than the provider's own reference currency is refused rather than recalculated, which is the right behavior and a surprise the first time.
Get Historical Rates Returns rates for a past date. Read the Latest flag carefully, because on by default means "the most recent rates up to this date" and a weekend or holiday quietly answers with the previous business day.
Convert Currency Converts an amount into one or more currencies at today's rates or a past date's. Doing the arithmetic here means the rate and the result share a source, a moment, and a rounding rule.

Frequently Asked Questions

What can FlowRunner do with Global Exchange Rates?

FlowRunner agents can run List Currencies, List Providers, and Get Latest Rates in Global Exchange Rates, plus 2 more actions.

Does connecting Global Exchange Rates to FlowRunner require OAuth?

No. Global Exchange Rates connects to FlowRunner with an API key, no OAuth flow required.

Can Global Exchange Rates trigger a FlowRunner workflow automatically?

Global Exchange Rates doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Global Exchange Rates

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us