Load Marigold Engage Delivery Cloud data to DuckDB

Marigold Engage Delivery Cloud is an omnichannel communication and marketing automation platform for managing customer engagement campaigns. Everything needed to build a working Marigold Engage Delivery Cloud → 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 Marigold Engage Delivery Cloud 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 Marigold Engage Delivery Cloud 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 Marigold Engage Delivery Cloud 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.

---

Marigold Engage Delivery Cloud API at a glance

These values come from the Marigold Engage Delivery Cloud API reference — the authoritative source if anything here looks out of date.

---

How do I authenticate with the Marigold Engage Delivery Cloud API?

The API uses OAuth 2.0 to obtain a JWT Bearer token, which must be included in the Authorization header of all requests as 'Authorization: Bearer '. Content-Type: application/json is also required.

1. Get your credentials

To obtain credentials for the Marigold Engage (formerly Selligent) API, follow these steps: 1. Log in to your Marigold Engage administration dashboard. 2. Navigate to Admin Configuration on the left-hand menu. 3. Select Access Management, then choose Service Accounts. 4. Click Create Service Account. 5. Provide a name, select Type as Custom, and define an expiry date if required. 6. Under the Endpoints tab, configure the specific permissions/actions the service account is authorized to perform. 7. Save the configuration to generate your Key and Secret. Copy these values immediately, as they are required for authentication.

2. Add them to .dlt/secrets.toml

Copy
[sources.marigold_engage_delivery_cloud_source]
bearer_token = "REPLACE_ME"

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 Marigold Engage Delivery Cloud data can I load into DuckDB?

These are the Marigold Engage Delivery Cloud endpoints dlt can load into DuckDB:

---

How do I load only new Marigold Engage Delivery Cloud records?

Marigold Engage Delivery Cloud exposes start/end parameters (date-based) on reporting/v1/bounces, so dlt can request only the records that changed since the last run. Set it as the cursor_path and dlt tracks the high-water mark for you between runs.

Copy
{"name": "bounces", "endpoint": {
    "path": "reporting/v1/bounces",
    "data_selector": "value",
    "incremental": {"cursor_path": "start/end parameters (date-based)", "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 Marigold Engage Delivery Cloud pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /email/v1/messages/send and /organizations/{organization}/lists from the Marigold Engage Delivery Cloud API into DuckDB:

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

@dlt.source
def marigold_engage_delivery_cloud_source(bearer_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://<customername>.sdc.slgnt.eu/api (EU) or https://<customername>.sdc.slgnt.us/api (US)",
            "auth": {"type": "bearer", "token": bearer_token},
        },
        "resources": [
            {"name": "bounces", "endpoint": {"path": "reporting/v1/bounces", "data_selector": "value"}},
            {"name": "complaints", "endpoint": {"path": "reporting/v1/complaints", "data_selector": "value"}}
        ],
    }
    yield from rest_api_resources(config)


def load_marigold_engage_delivery_cloud_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="marigold_engage_delivery_cloud_pipeline",
        destination="duckdb",
        dataset_name="marigold_engage_delivery_cloud_data",
    )
    load_info = pipeline.run(marigold_engage_delivery_cloud_source())
    print(load_info)


if __name__ == "__main__":
    load_marigold_engage_delivery_cloud_to_duckdb()

Run it with python marigold_engage_delivery_cloud_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 Marigold Engage Delivery Cloud 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("marigold_engage_delivery_cloud_pipeline").dataset()
df = data.bounces.df()
print(df.head())

SQL:

Copy
SELECT * FROM marigold_engage_delivery_cloud_data.bounces LIMIT 10;

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

---

How do I deploy the Marigold Engage Delivery Cloud 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 Marigold Engage Delivery Cloud 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 Marigold Engage Delivery Cloud 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