Google-webfonts

Availability:

Airbyte Cloud Airbyte OSS PyAirbyte

Support Level:

Marketplace

Connector Version:

0.1.16(Last updated 2 days ago)

CDK Version:

0.80.0

Sync Success Rate:

Usage Rate:

This page contains the setup guide and reference information for the Google-webfonts source connector.

Prerequisites

Api key is mandate for this connector to work, It could be generated by a gmail account for free at https://console.cloud.google.com/apis/dashboard. Just pass the generated API key and optional parameters for establishing the connection. Example:123

Setup guide

Step 1: Set up Google-webfonts connection

• Generate an API key (Example: 12345)
• Params (If specific info is needed)
• Available params
  • sort: SORT_UNDEFINED, ALPHA, DATE, STYLE, TRENDING, POPULARITY
  • alt: json, media or proto
  • prettyPrint: boolean

Step 2: Set up the Google-webfonts connector in Airbyte

For Airbyte Cloud:

1. Log into your Airbyte Cloud account.
2. In the left navigation bar, click Sources. In the top-right corner, click +new source.
3. On the Set up the source page, enter the name for the Google-webfonts connector and select Google-webfonts from the Source type dropdown.
4. Enter your api_key.
5. Enter the params configuration if needed. Supported params are: sort, alt, prettyPrint (Optional)
6. Click Set up source.

For Airbyte OSS:

1. Navigate to the Airbyte Open Source dashboard.
2. Set the name for your source.
3. Enter your api_key.
4. Enter the params configuration if needed. Supported params are: sort, alt, prettyPrint (Optional)
5. Click Set up source.

Supported sync modes

The Google-webfonts source connector supports the following sync modes:

Feature	Supported?
Full Refresh Sync	Yes
Incremental Sync	No
Replicate Incremental Deletes	No
SSL connection	Yes
Namespaces	No

Supported Streams

• Webfonts (Single stream API)

API method example

GET https://webfonts.googleapis.com/v1/webfonts?key=<1234567>&sort=SORT_UNDEFINED&prettyPrint=true&alt=json

Performance considerations

Google Webfont's API reference has v1 at present and v2 is at development. The connector as default uses v1.

Reference

Config fields reference

Field

Type

Property name

string

api_key

string

alt

string

prettyPrint

string

sort

Changelog

Expand to review

Version	Date	Pull Request	Subject
0.1.16	2024-08-17	44279	Update dependencies
0.1.15	2024-08-10	43552	Update dependencies
0.1.14	2024-08-03	43181	Update dependencies
0.1.13	2024-07-27	42774	Update dependencies
0.1.12	2024-07-20	42365	Update dependencies
0.1.11	2024-07-13	41761	Update dependencies
0.1.10	2024-07-10	41593	Update dependencies
0.1.9	2024-07-09	41203	Update dependencies
0.1.8	2024-07-06	40847	Update dependencies
0.1.7	2024-06-25	40420	Update dependencies
0.1.6	2024-06-22	40173	Update dependencies
0.1.5	2024-06-04	38960	[autopull] Upgrade base image to v1.2.1
0.1.4	2024-05-28	38684	Make connector compatible with Builder
0.1.3	2024-04-19	37172	Upgrade to CDK 0.80.0 and manage dependencies with Poetry.
0.1.2	2024-04-15	37172	Base image migration: remove Dockerfile and use the python-connector-base image
0.1.1	2024-04-12	37172	schema descriptions
0.1.0	2022-10-26	Init	Initial commit