Exchange Rates API connector

Set up the Exchange Rates API connector in Kaivo: authentication, configuration, the 1 BigQuery tables it syncs, and answers to common questions.

Written By Lauri Raivio

Last updated 16 days ago

Kaivo is a fully managed data platform that syncs your Exchange Rates API data into a Google BigQuery warehouse and keeps it up to date automatically. There is no pipeline to build and no infrastructure to run, so you can spend your time analysing your payment and finance data instead of moving it.

What is the Exchange Rates API connector

Sync your Exchange Rates API currency rates into BigQuery with Kaivo to convert amounts and track foreign exchange rates over time.

Category	Finance & Payments
Authentication	API key
Setup	Self-service

Getting started with the Exchange Rates API connector

Sign up for Kaivo and create a workspace.
Connect your Exchange Rates API account.
Choose which tables to sync.
Wait for the initial sync to finish.
Query your data in BigQuery or your favourite AI or BI tool.

Authenticating Exchange Rates API

Authenticate with your API Key.

Field	Description
API Key	Your API key. Get it from the Exchange Rates API marketplace.

Configuring the Exchange Rates API connector

When you set up the connector, you provide:

Field	Description
Start Date	Any data before this date will not be fetched.
Base Currency	ISO reference currency. The free plan only supports EUR as the base currency.
Ignore Weekends	Skip weekends when fetching exchange rate data, as exchanges are closed on weekends.

Tables and columns synced from Exchange Rates API

Kaivo syncs 1 table from Exchange Rates API into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.

exchange_rates (174 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`base`	`STRING`
`date`	`STRING`
`rates__aed`	`FLOAT64`
`rates__afn`	`FLOAT64`
`rates__all`	`FLOAT64`
`rates__amd`	`FLOAT64`
`rates__ang`	`FLOAT64`
`rates__aoa`	`FLOAT64`
`rates__ars`	`FLOAT64`
`rates__aud`	`FLOAT64`
`rates__awg`	`FLOAT64`
`rates__azn`	`FLOAT64`
`rates__bam`	`FLOAT64`
`rates__bbd`	`FLOAT64`
`rates__bdt`	`FLOAT64`
`rates__bgn`	`FLOAT64`
`rates__bhd`	`FLOAT64`
`rates__bif`	`FLOAT64`
`rates__bmd`	`FLOAT64`
`rates__bnd`	`FLOAT64`
`rates__bob`	`FLOAT64`
`rates__brl`	`FLOAT64`
`rates__bsd`	`FLOAT64`
`rates__btc`	`FLOAT64`
`rates__btn`	`FLOAT64`
`rates__bwp`	`FLOAT64`
`rates__byn`	`FLOAT64`
`rates__byr`	`FLOAT64`
`rates__bzd`	`FLOAT64`
`rates__cad`	`FLOAT64`
`rates__cdf`	`FLOAT64`
`rates__chf`	`FLOAT64`
`rates__clf`	`FLOAT64`
`rates__clp`	`FLOAT64`
`rates__cny`	`FLOAT64`
`rates__cop`	`FLOAT64`
`rates__crc`	`FLOAT64`
`rates__cuc`	`FLOAT64`
`rates__cup`	`FLOAT64`
`rates__cve`	`FLOAT64`
`rates__czk`	`FLOAT64`
`rates__djf`	`FLOAT64`
`rates__dkk`	`FLOAT64`
`rates__dop`	`FLOAT64`
`rates__dzd`	`FLOAT64`
`rates__egp`	`FLOAT64`
`rates__ern`	`FLOAT64`
`rates__etb`	`FLOAT64`
`rates__eur`	`FLOAT64`
`rates__fjd`	`FLOAT64`
`rates__fkp`	`FLOAT64`
`rates__gbp`	`FLOAT64`
`rates__gel`	`FLOAT64`
`rates__ggp`	`FLOAT64`
`rates__ghs`	`FLOAT64`
`rates__gip`	`FLOAT64`
`rates__gmd`	`FLOAT64`
`rates__gnf`	`FLOAT64`
`rates__gtq`	`FLOAT64`
`rates__gyd`	`FLOAT64`
`rates__hkd`	`FLOAT64`
`rates__hnl`	`FLOAT64`
`rates__hrk`	`FLOAT64`
`rates__htg`	`FLOAT64`
`rates__huf`	`FLOAT64`
`rates__idr`	`FLOAT64`
`rates__ils`	`FLOAT64`
`rates__imp`	`FLOAT64`
`rates__inr`	`FLOAT64`
`rates__iqd`	`FLOAT64`
`rates__irr`	`FLOAT64`
`rates__isk`	`FLOAT64`
`rates__jep`	`FLOAT64`
`rates__jmd`	`FLOAT64`
`rates__jod`	`FLOAT64`
`rates__jpy`	`FLOAT64`
`rates__kes`	`FLOAT64`
`rates__kgs`	`FLOAT64`
`rates__khr`	`FLOAT64`
`rates__kmf`	`FLOAT64`
`rates__kpw`	`FLOAT64`
`rates__krw`	`FLOAT64`
`rates__kwd`	`FLOAT64`
`rates__kyd`	`FLOAT64`
`rates__kzt`	`FLOAT64`
`rates__lak`	`FLOAT64`
`rates__lbp`	`FLOAT64`
`rates__lkr`	`FLOAT64`
`rates__lrd`	`FLOAT64`
`rates__lsl`	`FLOAT64`
`rates__ltl`	`FLOAT64`
`rates__lvl`	`FLOAT64`
`rates__lyd`	`FLOAT64`
`rates__mad`	`FLOAT64`
`rates__mdl`	`FLOAT64`
`rates__mga`	`FLOAT64`
`rates__mkd`	`FLOAT64`
`rates__mmk`	`FLOAT64`
`rates__mnt`	`FLOAT64`
`rates__mop`	`FLOAT64`
`rates__mro`	`FLOAT64`
`rates__mur`	`FLOAT64`
`rates__mvr`	`FLOAT64`
`rates__mwk`	`FLOAT64`
`rates__mxn`	`FLOAT64`
`rates__myr`	`FLOAT64`
`rates__mzn`	`FLOAT64`
`rates__nad`	`FLOAT64`
`rates__ngn`	`FLOAT64`
`rates__nio`	`FLOAT64`
`rates__nok`	`FLOAT64`
`rates__npr`	`FLOAT64`
`rates__nzd`	`FLOAT64`
`rates__omr`	`FLOAT64`
`rates__pab`	`FLOAT64`
`rates__pen`	`FLOAT64`
`rates__pgk`	`FLOAT64`
`rates__php`	`FLOAT64`
`rates__pkr`	`FLOAT64`
`rates__pln`	`FLOAT64`
`rates__pyg`	`FLOAT64`
`rates__qar`	`FLOAT64`
`rates__ron`	`FLOAT64`
`rates__rsd`	`FLOAT64`
`rates__rub`	`FLOAT64`
`rates__rwf`	`FLOAT64`
`rates__sar`	`FLOAT64`
`rates__sbd`	`FLOAT64`
`rates__scr`	`FLOAT64`
`rates__sdg`	`FLOAT64`
`rates__sek`	`FLOAT64`
`rates__sgd`	`FLOAT64`
`rates__shp`	`FLOAT64`
`rates__sll`	`FLOAT64`
`rates__sos`	`FLOAT64`
`rates__srd`	`FLOAT64`
`rates__std`	`FLOAT64`
`rates__svc`	`FLOAT64`
`rates__syp`	`FLOAT64`
`rates__szl`	`FLOAT64`
`rates__thb`	`FLOAT64`
`rates__tjs`	`FLOAT64`
`rates__tmt`	`FLOAT64`
`rates__tnd`	`FLOAT64`
`rates__top`	`FLOAT64`
`rates__try`	`FLOAT64`
`rates__ttd`	`FLOAT64`
`rates__twd`	`FLOAT64`
`rates__tzs`	`FLOAT64`
`rates__uah`	`FLOAT64`
`rates__ugx`	`FLOAT64`
`rates__usd`	`FLOAT64`
`rates__uyu`	`FLOAT64`
`rates__uzs`	`FLOAT64`
`rates__vef`	`FLOAT64`
`rates__vnd`	`FLOAT64`
`rates__vuv`	`FLOAT64`
`rates__wst`	`FLOAT64`
`rates__xaf`	`FLOAT64`
`rates__xag`	`FLOAT64`
`rates__xau`	`FLOAT64`
`rates__xcd`	`FLOAT64`
`rates__xdr`	`FLOAT64`
`rates__xof`	`FLOAT64`
`rates__xpf`	`FLOAT64`
`rates__yer`	`FLOAT64`
`rates__zar`	`FLOAT64`
`rates__zmk`	`FLOAT64`
`rates__zmw`	`FLOAT64`
`rates__zwl`	`FLOAT64`
`success`	`BOOL`
`timestamp`	`INT64`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

How the Exchange Rates API sync works

After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Exchange Rates API supports it, each sync pulls only new and changed records so it stays fast; otherwise it refreshes the whole table. Every record keeps its original ID, so you won't get duplicate rows.

Frequently asked questions

How long does the initial sync take for Exchange Rates API?

It depends on how much history is in your Exchange Rates API account. Most initial syncs finish within minutes, while large accounts can take a few hours. After that, syncs only fetch new and changed records, so they're much faster.

Can I sync only some tables or columns?

Yes. You pick which tables to sync when you set up the connection and can change the selection later. Tables you don't select are never copied to your warehouse.

What happens when Exchange Rates API's schema changes?

New fields are never added automatically. You choose which fields to sync, so data you haven't selected (sensitive personal data, for example) never lands in your warehouse. When a new field appears, it becomes available for you to add. What happens to removed or renamed fields depends on a table's sync mode: full-refresh tables always match what's currently in Exchange Rates API, so dropped fields disappear, while incremental tables keep their existing columns and history, so an old field stays and newly added fields fill in over time.

Your data lives in your own Kaivo-managed BigQuery warehouse, so the most direct option is to delete or anonymise specific records right in BigQuery. If you delete data in Exchange Rates API instead, full-refresh tables drop it on the next sync, while incremental tables keep it, so you would remove the row in BigQuery or ask us to run a full refresh. To remove everything, delete the Exchange Rates API connector in Kaivo and all of its synced data is deleted with it.

Common use cases for Exchange Rates API data

Currency conversion

Use exchange_rates rates to convert transactions into a single reporting currency.

Rate history

Track rates by date to see how currency pairs move over time.

Multi-currency reporting

Join rates to your sales or expense data to report consistently across markets.

FX exposure

Analyse rate changes against your currency positions to understand exposure.

Use Exchange Rates API data in your AI and BI tools

Once Exchange Rates API data lands in your Kaivo-managed BigQuery warehouse, you can explore it with AI tools or any BI tool that connects to BigQuery. Here's how the most common destinations work with Exchange Rates API data.

Claude

Use Kaivo's MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →

Power BI

Microsoft's BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →

Data Studio

Free Google BI tool with native BigQuery support. One-click connection to your Kaivo warehouse; great for SMB teams on Google Workspace. Setup guide →

Tableau

The premium analytics standard, with native BigQuery integration. Setup guide →

Google Sheets

Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →

Excel

Connect via Power Query's BigQuery connector. Setup guide →

Metabase

Open-source BI tool with strong BigQuery support. Setup guide →

See our pricing page for Exchange Rates API connector pricing and plan details.

Chargebee: Sync Chargebee to BigQuery.
ChartMogul: Sync ChartMogul to BigQuery.
Fennoa: Sync Fennoa to BigQuery.
Fortnox: Sync Fortnox to BigQuery.
FreshBooks: Sync FreshBooks to BigQuery.
PayPal Enterprise Payments: Sync PayPal Enterprise Payments to BigQuery.

Was this helpful?

Still need help? Share an idea