CoinAPI.io connector

Set up the CoinAPI.io connector in Kaivo: authentication, configuration, the 3 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 CoinAPI.io 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 CoinAPI.io connector

Sync your CoinAPI crypto market data into BigQuery with Kaivo to analyse price history, trades, and quotes across exchanges over time.

Category	Finance & Payments
Authentication	API key
Setup	Self-service

Getting started with the CoinAPI.io connector

Sign up for Kaivo and create a workspace.
Connect your CoinAPI.io 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 CoinAPI.io

Authenticate with your API Key.

Field	Description
API Key	Your CoinAPI API key. Create a free account at coinapi.io and copy your key from the dashboard.

Configuring the CoinAPI.io connector

When you set up the connector, you provide:

Field	Description
Symbol ID	The trading pair or asset symbol to sync (e.g. BITSTAMP_SPOT_BTC_USD).
Period	The time period for each data point (e.g. 5SEC, 1HRS, 2MTH).
Start Date	Any data before this date will not be fetched.

Tables and columns synced from CoinAPI.io

Kaivo syncs 3 tables from CoinAPI.io into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.

ohlcv_historical_data (12 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`price_close`	`FLOAT64`	The closing price of the asset during the specified time period.
`price_high`	`FLOAT64`	The highest price of the asset reached during the specified time period.
`price_low`	`FLOAT64`	The lowest price of the asset reached during the specified time period.
`price_open`	`FLOAT64`	The opening price of the asset for the specified time period.
`time_close`	`TIMESTAMP`	The timestamp representing the closing time of the specified period (in UTC).
`time_open`	`TIMESTAMP`	The timestamp representing the opening time of the specified period (in UTC).
`time_period_end`	`TIMESTAMP`	The timestamp representing the end time of the specified time period (in UTC).
`time_period_start`	`TIMESTAMP`	The timestamp representing the start time of the specified time period (in UTC).
`trades_count`	`INT64`	The total number of trades executed during the specified time period.
`volume_traded`	`FLOAT64`	The total volume of the asset traded during the specified time period.
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

quotes_historical_data (9 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`ask_price`	`FLOAT64`	The asking price for the specified symbol at the given time.
`ask_size`	`FLOAT64`	The size of the ask order for the specified symbol at the given time.
`bid_price`	`FLOAT64`	The bidding price for the specified symbol at the given time.
`bid_size`	`FLOAT64`	The size of the bid order for the specified symbol at the given time.
`symbol_id`	`STRING`	A unique identifier for the symbol being quoted.
`time_coinapi`	`TIMESTAMP`	The timestamp when the quote data was received by the CoinAPI service.
`time_exchange`	`TIMESTAMP`	The timestamp of when the quote data was received by the exchange.
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

trades_historical_data (10 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`price`	`FLOAT64`	The price at which the trade occurred.
`size`	`FLOAT64`	The size or quantity of the trade.
`symbol_id`	`STRING`	The unique symbol identifier for the trade.
`taker_side`	`STRING`	The side of the trade representing the taker (e.g., buy or sell).
`time_coinapi`	`TIMESTAMP`	The timestamp of the trade in the CoinAPI format.
`time_exchange`	`TIMESTAMP`	The timestamp of the trade in the exchange's native time format.
`time_period_end`	`TIMESTAMP`	The end timestamp of the time period to which the trade belongs.
`uuid`	`STRING`	The universally unique identifier associated with the trade.
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

How the CoinAPI.io sync works

After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where CoinAPI.io 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 CoinAPI.io?

It depends on how much history is in your CoinAPI.io 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 CoinAPI.io'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 CoinAPI.io, 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 CoinAPI.io 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 CoinAPI.io connector in Kaivo and all of its synced data is deleted with it.

Common use cases for CoinAPI.io data

Price history

Use ohlcv_historical_data to chart open, high, low, and close prices over time.

Trade analysis

Analyse trades_historical_data by price and size to study volume and taker side.

Spread tracking

Use quotes_historical_data bid and ask prices to monitor spreads across symbols.

Backtesting data

Combine OHLCV and trades to build datasets for strategy analysis.

Use CoinAPI.io data in your AI and BI tools

Once CoinAPI.io 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 CoinAPI.io 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 CoinAPI.io 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