Load Oxylabs YouTube Transcript API data in Python using dltHub
Build a Oxylabs YouTube Transcript API-to-database or-dataframe pipeline in Python using dlt with automatic Cursor support.
In this guide, we'll set up a complete Oxylabs YouTube Transcript API data pipeline from API credentials to your first data load in just 10 minutes. You'll end up with a fully declarative Python pipeline based on dlt's REST API connector, like in the partial example code below:
Example code
Why use dltHub Workspace with LLM Context to generate Python pipelines?
- Accelerate pipeline development with AI-native context
- Debug pipelines, validate schemas and data with the integrated Pipeline Dashboard
- Build Python notebooks for end users of your data
- Low maintenance thanks to Schema evolution with type inference, resilience and self documenting REST API connectors. A shallow learning curve makes the pipeline easy to extend by any team member
- dlt is the tool of choice for Pythonic Iceberg Lakehouses, bringing mature data loading to pythonic Iceberg with or without catalogs
What you’ll do
We’ll show you how to generate a readable and easily maintainable Python script that fetches data from oxylabs_youtube_transcript_api’s API and loads it into Iceberg, DataFrames, files, or a database of your choice. Here are some of the endpoints you can load:
-
Query Endpoints: Endpoints related to managing and retrieving queries.
/v1/queries: General endpoint for managing queries./v1/queries/{job_id}: Retrieve a specific query using its job ID./v1/queries/batch: Allows for batch processing of multiple queries./v1/queries/%s: Another format for accessing a specific query./v1/queries/{id}: Retrieve a query using its unique identifier./v1/queries/%s/results: Fetch results for a specific query./v1/queries/{job_id}/results: Fetch results for a specific job ID query.
-
Schedule Endpoints: Endpoints for managing schedules.
/v1/schedules/{id}: Retrieve information about a specific schedule.
-
Info Endpoints: Endpoints providing information about the system.
/v1/info/callbacker_ips: Retrieve the IP addresses for callback services.
You will then debug the Oxylabs YouTube Transcript API pipeline using our Pipeline Dashboard tool to ensure it is copying the data correctly, before building a Notebook to explore your data and build reports.
Setup & steps to follow
💡Before getting started, let's make sure Cursor is set up correctly:
- We suggest using a model like Claude 3.7 Sonnet or better
- Index the REST API Source tutorial: https://dlthub.com/docs/dlt-ecosystem/verified-sources/rest_api/ and add it to context as @dlt rest api
- Read our full steps on setting up Cursor
Now you're ready to get started!
-
⚙️ Set up
dltWorkspaceInstall dlt with duckdb support:
pip install "dlt[workspace]"Initialize a dlt pipeline with Oxylabs YouTube Transcript API support.
dlt init dlthub:oxylabs_youtube_transcript_api duckdbThe
initcommand will setup the necessary files and folders for the next step. -
🤠 Start LLM-assisted coding
Here’s a prompt to get you started:
PromptPlease generate a REST API Source for Oxylabs YouTube Transcript API API, as specified in @oxylabs_youtube_transcript_api-docs.yaml Start with endpoints batch and 12345678900987654321 and skip incremental loading for now. Place the code in oxylabs_youtube_transcript_api_pipeline.py and name the pipeline oxylabs_youtube_transcript_api_pipeline. If the file exists, use it as a starting point. Do not add or modify any other files. Use @dlt rest api as a tutorial. After adding the endpoints, allow the user to run the pipeline with python oxylabs_youtube_transcript_api_pipeline.py and await further instructions. -
🔒 Set up credentials
You need to provide a username and password for basic authentication, which can be included in the request header as "Authorization" with the value "Basic " followed by the Base64 encoded string of "username:password".
To get the appropriate API keys, please visit the original source at https://developers.oxylabs.io/scraping-solutions/web-scraper-api/targets/youtube/youtube-transcript. If you want to protect your environment secrets in a production environment, look into setting up credentials with dlt.
-
🏃♀️ Run the pipeline in the Python terminal in Cursor
python oxylabs_youtube_transcript_api_pipeline.pyIf your pipeline runs correctly, you’ll see something like the following:
Pipeline oxylabs_youtube_transcript_api load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset oxylabs_youtube_transcript_api_data The duckdb destination used duckdb:/oxylabs_youtube_transcript_api.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs -
📈 Debug your pipeline and data with the Pipeline Dashboard
Now that you have a running pipeline, you need to make sure it’s correct, so you do not introduce silent failures like misconfigured pagination or incremental loading errors. By launching the dlt Workspace Pipeline Dashboard, you can see various information about the pipeline to enable you to test it. Here you can see:
- Pipeline overview: State, load metrics
- Data’s schema: tables, columns, types, hints
- You can query the data itself
dlt pipeline oxylabs_youtube_transcript_api_pipeline show -
🐍 Build a Notebook with data explorations and reports
With the pipeline and data partially validated, you can continue with custom data explorations and reports. To get started, paste the snippet below into a new marimo Notebook and ask your LLM to go from there. Jupyter Notebooks and regular Python scripts are supported as well.
import dlt data = dlt.pipeline("oxylabs_youtube_transcript_api_pipeline").dataset() # get "batch" table as Pandas frame data."batch".df().head()