Load Demon DMS data to DuckDB

Demon DMS is a platform that combines master data, customer relationship, product, and inventory management for literary magazines and presses. Everything needed to build a working Demon DMS → 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 Demon DMS 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 Demon DMS 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 Demon DMS 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.

---

Demon DMS API at a glance

These values come from the Demon DMS API documentation. Check them against the vendor's current reference before relying on them in production.

---

How do I authenticate with the Demon DMS API?

The API uses a custom Authorization header with a scheme 'DMN' followed by a 'PUBLIC_KEY:DIGEST' format. Additionally, an 'X-DMN-Timestamp' header is required.

1. Get your credentials

To obtain API credentials for Demon DMS, log in to your Demon DMS instance dashboard. Navigate to the API settings or Integrations management area (typically found under /management or /settings). Create a new API key pair by selecting the option to generate or manage API keys. Note that Demon uses a public key and a secret key format, often requiring an Authorization header in the format 'DMN {PUBLIC_KEY}:{SECRET_KEY}'.

2. Add them to .dlt/secrets.toml

Copy
[sources.demon_dms_source]
demon_dms_api_key = "DMN your_public_key:your_secret_key"

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 Demon DMS data can I load into DuckDB?

These are the Demon DMS endpoints dlt can load into DuckDB:

---

How do I load only new Demon DMS records?

The Demon DMS 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": "integrations", "endpoint": {
    "path": "integrations",
    # 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 Demon DMS pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading integrations and remote/orders from the Demon DMS API into DuckDB:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def demon_dms_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://{{SUBDOMAIN}}.api.demondms.com",
            "auth": {"type": "bearer", "token": api_key},
        },
        "resources": [
            {"name": "integrations", "endpoint": {"path": "integrations"}},
            {"name": "remote_orders", "endpoint": {"path": "remote/orders"}}
        ],
    }
    yield from rest_api_resources(config)


def load_demon_dms_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="demon_dms_pipeline",
        destination="duckdb",
        dataset_name="demon_dms_data",
    )
    load_info = pipeline.run(demon_dms_source())
    print(load_info)


if __name__ == "__main__":
    load_demon_dms_to_duckdb()

Run it with python demon_dms_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 Demon DMS 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("demon_dms_pipeline").dataset()
df = data.integrations.df()
print(df.head())

SQL:

Copy
SELECT * FROM demon_dms_data.integrations LIMIT 10;

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

---

How do I deploy the Demon DMS 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 Demon DMS 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 Demon DMS 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