3036ddae5a
* New source: Google webfonts * chore: Add Docs * chore: update changelog * chore: resolved given comments for PR * chore: unwanted files removed * fix: generate and add source definitions Co-authored-by: sajarin <sajarindider@gmail.com>
1.2 KiB
1.2 KiB
Google-webfonts
The connector uses the v1 API documented here: https://developers.google.com/fonts/docs/developer_api . It is straightforward HTTP REST API with API authentication.
API key
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
Implementation details
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: Generate schema for the endpoint
Custom schema is generated and tested with different IDs
Step 3: Spec, Secrets, and connector yaml files are configured with reference to the Airbyte documentation.
In a nutshell:
- Navigate to the Airbyte Open Source dashboard.
- Set the name for your source.
- Enter your
api_key. - Enter your config params if needed. (Optional)
- Click Set up source.
- We use only GET methods, towards the webfonts endpoints which is straightforward