Load Plesk Obsidian data to DuckDB

Plesk Obsidian REST API enables programmatic management of Plesk server objects and CLI utilities using JSON payloads. Everything needed to build a working Plesk Obsidian → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.

---

Build your Plesk Obsidian to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from Plesk Obsidian to DuckDB and run it on dltHub

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Plesk Obsidian API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.

---

Plesk Obsidian API at a glance

These values come from the Plesk Obsidian API reference — the authoritative source if anything here looks out of date.

---

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>:8443/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

Copy
[sources.plesk_obsidian_source]
plesk_url = "https://your-server-ip:8443"
api_key = "your_generated_api_key_here"

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.

---

What Plesk Obsidian data can I load into DuckDB?

These are the Plesk Obsidian endpoints dlt can load into DuckDB:

---

How do I load only new Plesk Obsidian records?

The Plesk Obsidian API reference does not document a timestamp or sequence field for these endpoints, so there is nothing to advertise here as verified. Pick a field from the endpoints table above that increases with every write, then set it as the cursor_path.

Copy
{"name": "domains", "endpoint": {
    "path": "api/v2/domains",
    # Replace with a field that increases on every write.
    "incremental": {"cursor_path": "REPLACE_ME", "initial_value": "2024-01-01T00:00:00Z"},
}}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.

---

What does the generated Plesk Obsidian pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /api/v2/domains and /api/v2/cli/commands from the Plesk Obsidian API into DuckDB:

Copy
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 load_plesk_obsidian_to_duckdb() -> 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)


if __name__ == "__main__":
    load_plesk_obsidian_to_duckdb()

Run it with python plesk_obsidian_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.

---

How do I query Plesk Obsidian data in DuckDB?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("plesk_obsidian_pipeline").dataset()
df = data.domains.df()
print(df.head())

SQL:

Copy
SELECT * FROM plesk_obsidian_data.domains LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the Plesk Obsidian to DuckDB pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

• Deploy & schedule — run the pipeline as a managed job with automatic retries.
• Monitor — observable job queues, alerting, and load metrics for every run.
• Transform — promote raw Plesk Obsidian loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load Plesk Obsidian data to?

dlt loads into any of these — only the destination argument changes:

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.

---

Next steps

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack