Load Plesk Obsidian data in Python using dltHub

Build a Plesk Obsidian-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

Plesk Obsidian REST API enables programmatic management of Plesk server objects and CLI utilities using JSON payloads. The REST API base URL is https://<plesk-host>:8443/api/v2 and all requests require either Basic authentication or an X-API-Key header.

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 Plesk Obsidian data in under 10 minutes.


What data can I load from Plesk Obsidian?

Here are some of the endpoints you can load from Plesk Obsidian:

ResourceEndpointMethodData selectorDescription
domains/api/v2/domainsGETList all domains
auth_keys/api/v2/auth/keysGETList all authentication keys
db_users/api/v2/db_usersGETList all database users
cli_commands/api/v2/cli/commandsGETList all supported CLI utilities
server_settings/api/v2/server/settingsGETGet current server settings

How do I authenticate with the Plesk Obsidian API?

Authentication is performed via Basic Auth (Authorization: Basic <base64_encoded_credentials>) or an API key passed in the X-API-Key header.

1. Get your credentials

To generate an API key for the Plesk Obsidian REST API, use the command-line interface (CLI) on the server, or issue a POST request using basic authentication. 1. Option 1: Using CLI (Recommended) Access the server via SSH and run: plesk bin secret_key -c -ip-address <your_ip_address> This returns the API key string. 2. Option 2: Using REST API (Requires Basic Auth) Send an authenticated POST request to the auth endpoint: curl -X POST --user <admin_user>:<admin_password> -H "Content-Type: application/json" -d '{}' "https://<server_ip>

/api/v2/auth/keys" The response will contain your API key. Once generated, use this key in the 'X-API-Key' request header for subsequent calls.

2. Add them to .dlt/secrets.toml

[sources.plesk_obsidian_source] plesk_url = "https://your-server-ip:8443" api_key = "your_generated_api_key_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 Plesk Obsidian 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 plesk_obsidian_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline plesk_obsidian_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset plesk_obsidian_data The duckdb destination used duckdb:/plesk_obsidian.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 /api/v2/domains and /api/v2/cli/commands from the Plesk Obsidian 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 plesk_obsidian_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://<plesk-host>:8443/api/v2", "auth": {"type": "api_key", "api_key": api_key, "name": "X-API-Key"}, }, "resources": [ {"name": "domains", "endpoint": {"path": "api/v2/domains"}}, {"name": "auth_keys", "endpoint": {"path": "api/v2/auth/keys"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="plesk_obsidian_pipeline", destination="duckdb", dataset_name="plesk_obsidian_data", ) load_info = pipeline.run(plesk_obsidian_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("plesk_obsidian_pipeline").dataset() sessions_df = data.domains.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM plesk_obsidian_data.domains LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("plesk_obsidian_pipeline").dataset() data.domains.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 Plesk Obsidian data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample 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 Plesk Obsidian?

Request dlt skills, commands, AGENT.md files, and AI-native context.

Available Pipelines