Libsyn Python API Docs | dltHub
Build a Libsyn-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Libsyn provides specific integrations and a status API for managing and monitoring podcast-related data and services. The REST API base URL is https://status.libsyn.com/api/v1 and Integration-specific credentials (OAuth2 bearer tokens or API keys) are used; some endpoints are public..
dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading Libsyn data in under 10 minutes.
What data can I load from Libsyn?
Here are some of the endpoints you can load from Libsyn:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| components | https://status.libsyn.com/api/v1/components | GET | components | List of system components and their status |
| notices | https://status.libsyn.com/api/v1/notices | GET | notices | List of incidents, maintenance notices, and updates |
| status | https://status.libsyn.com/api/v1/status | GET | Overall service status summary | |
| notice | https://status.libsyn.com/api/v1/notices/:id | GET | notice | Detailed information for a single notice |
| component | https://status.libsyn.com/api/v1/components/:id | GET | component | Detailed information for a single component |
How do I authenticate with the Libsyn API?
Integrations typically use OAuth2 or API keys generated via the Libsyn account dashboard. The status API does not require authentication.
1. Get your credentials
Libsyn does not provide a general-purpose public REST API for all users. API access is typically a premium feature available through Libsyn Pro or Enterprise plans. To obtain credentials: 1. Contact the Libsyn sales team or your account manager to inquire about API access for your plan. 2. Once authorized, log into your Libsyn account dashboard. 3. Navigate to the integration or developer settings section provided by your account representative. 4. Follow the instructions to generate an API key or OAuth client credentials (e.g., Client ID and Client Secret). 5. Save these credentials securely, as they will be required for your pipeline configuration. Note: The Libsyn Status API (status.libsyn.com/api/v1) is publicly accessible and does not require credentials.
2. Add them to .dlt/secrets.toml
[sources.libsyn_source] access_token = "your_api_key_or_token_here"
dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.
How do I set up and run the pipeline?
Set up a virtual environment and install dlt:
uv init uv add "dlt[hub]"
1. Install the dlt AI harness:
uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex
This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →
2. Install the rest-api-pipeline toolkit:
uv run dlthub ai toolkit install rest-api-pipeline
This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →
3. Start LLM-assisted coding:
Use /find-source to load data from the Libsyn API into DuckDB.
The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.
4. Run the pipeline:
uv run python libsyn_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline libsyn_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset libsyn_data The duckdb destination used duckdb:/libsyn.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
uv run dlthub show
This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.
Python pipeline example
This example loads components and notices from the Libsyn API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def libsyn_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://status.libsyn.com/api/v1", "auth": {"type": "bearer", "token": access_token}, }, "resources": [ {"name": "components", "endpoint": {"path": "api/v1/components", "data_selector": "components"}}, {"name": "notices", "endpoint": {"path": "api/v1/notices", "data_selector": "notices"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="libsyn_pipeline", destination="duckdb", dataset_name="libsyn_data", ) load_info = pipeline.run(libsyn_source()) print(load_info)
To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.
How do I query the loaded data?
Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("libsyn_pipeline").dataset() sessions_df = data.notices.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM libsyn_data.notices LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("libsyn_pipeline").dataset() data.notices.df().head()
See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.
What destinations can I load Libsyn data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI harness:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-platform— Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform
Was this page helpful?
Community Hub
Need more dlt context for Libsyn?
Request dlt skills, commands, AGENT.md files, and AI-native context.