Wasabi Stats API connector

Set up the Wasabi Stats API connector in Kaivo: authentication, configuration, the 2 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 Wasabi Stats 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 data from Wasabi Stats API instead of moving it.

What is the Wasabi Stats API connector

Sync your Wasabi storage stats into BigQuery with Kaivo to analyse cloud storage usage, bucket-level trends, and cost over time.

Category	Tech
Authentication	API key
Setup	Self-service

Getting started with the Wasabi Stats API connector

Sign up for Kaivo and create a workspace.
Connect your Wasabi Stats 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 Wasabi Stats API

Authenticate with your Secret Key.

Field	Description
Secret Key	The Secret Key paired with your Access Key (shown only once when the access key is created).

Configuring the Wasabi Stats API connector

When you set up the connector, you provide:

Field	Description
Access Key	Your Wasabi Access Key, created in the Wasabi Console under Access Keys.
Start Date	Any data before this date will not be fetched.

Tables and columns synced from Wasabi Stats API

Kaivo syncs 2 tables from Wasabi Stats API into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.

Standalone Bucket Utilizations (29 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`bucket`	`STRING`
`region`	`STRING`
`acct_num`	`FLOAT64`
`end_time`	`STRING`
`bucket_num`	`FLOAT64`
`start_time`	`STRING`
`create_time`	`STRING`
`acct_plan_num`	`FLOAT64`
`delete_bytes`	`FLOAT64`
`num_api_calls`	`FLOAT64`
`num_get_calls`	`FLOAT64`
`num_put_calls`	`FLOAT64`
`upload_bytes`	`FLOAT64`
`num_head_calls`	`FLOAT64`
`num_list_calls`	`FLOAT64`
`download_bytes`	`FLOAT64`
`num_delete_calls`	`FLOAT64`
`storage_read_bytes`	`FLOAT64`
`storage_wrote_bytes`	`FLOAT64`
`num_billable_objects`	`FLOAT64`
`raw_storage_size_bytes`	`FLOAT64`
`bucket_utilization_num`	`FLOAT64`
`padded_storage_size_bytes`	`FLOAT64`
`deleted_storage_size_bytes`	`FLOAT64`
`metadata_storage_size_bytes`	`FLOAT64`
`orphaned_storage_size_bytes`	`FLOAT64`
`num_billable_deleted_objects`	`FLOAT64`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Standalone Utilizations (45 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`acct_num`	`FLOAT64`
`end_time`	`STRING`
`start_time`	`STRING`
`create_time`	`STRING`
`acct_plan_num`	`FLOAT64`
`delete_bytes`	`FLOAT64`
`num_api_calls`	`FLOAT64`
`num_get_calls`	`FLOAT64`
`num_put_calls`	`FLOAT64`
`upload_bytes`	`FLOAT64`
`num_head_calls`	`FLOAT64`
`num_list_calls`	`FLOAT64`
`download_bytes`	`FLOAT64`
`num_delete_calls`	`FLOAT64`
`utilization_num`	`FLOAT64`
`storage_read_bytes`	`FLOAT64`
`storage_wrote_bytes`	`FLOAT64`
`num_billable_objects`	`FLOAT64`
`raw_storage_size_bytes`	`FLOAT64`
`regional_utilizations__eu_central_1__delete_bytes`	`FLOAT64`
`regional_utilizations__eu_central_1__num_api_calls`	`FLOAT64`
`regional_utilizations__eu_central_1__num_get_calls`	`FLOAT64`
`regional_utilizations__eu_central_1__num_put_calls`	`FLOAT64`
`regional_utilizations__eu_central_1__upload_bytes`	`FLOAT64`
`regional_utilizations__eu_central_1__num_head_calls`	`FLOAT64`
`regional_utilizations__eu_central_1__num_list_calls`	`FLOAT64`
`regional_utilizations__eu_central_1__download_bytes`	`FLOAT64`
`regional_utilizations__eu_central_1__num_delete_calls`	`FLOAT64`
`regional_utilizations__eu_central_1__storage_read_bytes`	`FLOAT64`
`regional_utilizations__eu_central_1__storage_wrote_bytes`	`FLOAT64`
`regional_utilizations__eu_central_1__num_billable_objects`	`FLOAT64`
`regional_utilizations__eu_central_1__raw_storage_size_bytes`	`FLOAT64`
`regional_utilizations__eu_central_1__padded_storage_size_bytes`	`FLOAT64`
`regional_utilizations__eu_central_1__deleted_storage_size_bytes`	`FLOAT64`
`regional_utilizations__eu_central_1__metadata_storage_size_bytes`	`FLOAT64`
`regional_utilizations__eu_central_1__orphaned_storage_size_bytes`	`FLOAT64`
`regional_utilizations__eu_central_1__num_billable_deleted_objects`	`FLOAT64`
`min_storage_charge_bytes`	`FLOAT64`
`padded_storage_size_bytes`	`FLOAT64`
`deleted_storage_size_bytes`	`FLOAT64`
`metadata_storage_size_bytes`	`FLOAT64`
`orphaned_storage_size_bytes`	`FLOAT64`
`num_billable_deleted_objects`	`FLOAT64`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

How the Wasabi Stats API sync works

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

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

Common use cases for Wasabi Stats API data

Usage tracking

Use Standalone Utilizations to track storage usage over time.

Bucket analysis

Use Standalone Bucket Utilizations to see which buckets consume the most storage.

Cost context

Bring storage stats into BigQuery to report on cost alongside your other cloud data.

Use Wasabi Stats API data in your AI and BI tools

Once Wasabi Stats 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 Wasabi Stats 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 Wasabi Stats API connector pricing and plan details.

Adform: Sync Adform to BigQuery.
Amplitude: Sync Amplitude to BigQuery.
Auth0: Sync Auth0 to BigQuery.
Convex: Sync Convex to BigQuery.
GitHub: Sync GitHub to BigQuery.
GitLab: Sync GitLab to BigQuery.

Was this helpful?

Still need help? Share an idea