Skip to content
Book a demoStart free
Connectors

Google Fonts Developer API connector

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

Google Fonts Developer API connector pricing, tier and credits on kaivo.io

Kaivo is a fully managed data platform that syncs your Google Fonts Developer 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 Google Fonts Developer API instead of moving it.

What is the Google Fonts Developer API connector

Section titled “What is the Google Fonts Developer API connector”

Sync the Google Fonts catalogue into BigQuery with Kaivo to inventory available typefaces and their variants for your design work.

CategoryOther
AuthenticationAPI key
SetupSelf-service

Getting started with the Google Fonts Developer API connector

Section titled “Getting started with the Google Fonts Developer API connector”
  1. Sign up for Kaivo and create a workspace.
  2. Connect your Google Fonts Developer API account.
  3. Choose which tables to sync.
  4. Wait for the initial sync to finish.
  5. Query your data in BigQuery or your favourite AI or BI tool.

Authenticate with your API Key.

Field Description
API Key
API key required to access the Google Fonts API. Generate one in the Google Cloud Console under APIs & Services.

|

Tables and columns synced from Google Fonts Developer API

Section titled “Tables and columns synced from Google Fonts Developer API”

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

fonts (3 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
kind STRING The API resource kind, always set to ‘webfonts#webfontList’
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
Column Type Description
_kaivo_parent_id STRING Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
version STRING Version of the font data
category STRING The category the font belongs to (e.g. ‘sans-serif’, ‘serif’)
family STRING The name of the font family (e.g. ‘Roboto’, ‘Open Sans’)
files__italic STRING URL to the italic font file
files__regular STRING URL to the regular font file
kind STRING The resource kind, should always be ‘webfonts#webfont’
last_modified STRING Timestamp of the last modification date of the font
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
Column Type Description
_kaivo_parent_id STRING Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
value STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
Column Type Description
_kaivo_parent_id STRING Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
value STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

How the Google Fonts Developer API sync works

Section titled “How the Google Fonts Developer API sync works”

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

How long does the initial sync take for Google Fonts Developer API?

Section titled “How long does the initial sync take for Google Fonts Developer API?”

It depends on how much history is in your Google Fonts Developer 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.

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 Google Fonts Developer API’s schema changes?

Section titled “What happens when Google Fonts Developer 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 Google Fonts Developer 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.

How do I handle GDPR or data deletion requests?

Section titled “How do I handle GDPR or data deletion requests?”

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 Google Fonts Developer 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 Google Fonts Developer API connector in Kaivo and all of its synced data is deleted with it.

Common use cases for Google Fonts Developer API data

Section titled “Common use cases for Google Fonts Developer API data”

Use fonts to list every available family and its variants in one place.

Analyse the styles and weights each family offers.

Track the font list over time to see what is added.

Bring the catalogue into BigQuery to search fonts alongside your brand assets.

Use Google Fonts Developer API data in your AI and BI tools

Section titled “Use Google Fonts Developer API data in your AI and BI tools”

Once Google Fonts Developer 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 Google Fonts Developer API data.

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

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

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

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

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

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

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

See our pricing page for Google Fonts Developer API connector pricing and plan details.