Load Epay data to DuckDB

ePay Payments API is a platform for initializing and managing payment sessions and transactions for merchants. Everything needed to build a working Epay → 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 Epay 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 Epay 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 Epay 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.

---

Epay API at a glance

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

---

How do I authenticate with the Epay API?

The API uses Bearer authentication, requiring the Authorization header to be set with the format 'Bearer [API_KEY]'.

1. Get your credentials

1. Log in to your Epay merchant account at https://www.epay.com. 2. Navigate to the API Management section (often found under the user avatar or Developer settings menu). 3. If required, complete the merchant KYC verification process. 4. Click the button to generate or recreate your API_KEY. 5. You will be prompted to enter your payment password and a Google Authenticator 2FA code to confirm the action. 6. Once confirmed, the API_KEY will be displayed; ensure you store it securely as it is required for signing all API requests. 7. Optionally, if using payout functionality, register your server IP address in the IP whitelist section within the same dashboard area.

2. Add them to .dlt/secrets.toml

Copy
[sources.epay_source]
api_key = "your_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 Epay data can I load into DuckDB?

These are the Epay endpoints dlt can load into DuckDB:

---

How do I load only new Epay records?

Epay exposes offset on public/api/v1/transactions, 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": "transactions", "endpoint": {
    "path": "public/api/v1/transactions",
    "data_selector": "items",
    "incremental": {"cursor_path": "offset", "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 Epay pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading paymentApi/merReceive and paymentApi/queryOrder from the Epay API into DuckDB:

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

@dlt.source
def epay_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://payments.epay.eu",
            "auth": {"type": "bearer", "token": api_key},
        },
        "resources": [
            {"name": "transactions", "endpoint": {"path": "public/api/v1/transactions", "data_selector": "items"}},
            {"name": "payment_methods", "endpoint": {"path": "public/api/v1/payment-methods/imported", "data_selector": "items"}}
        ],
    }
    yield from rest_api_resources(config)


def load_epay_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="epay_pipeline",
        destination="duckdb",
        dataset_name="epay_data",
    )
    load_info = pipeline.run(epay_source())
    print(load_info)


if __name__ == "__main__":
    load_epay_to_duckdb()

Run it with python epay_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 Epay 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("epay_pipeline").dataset()
df = data.transactions.df()
print(df.head())

SQL:

Copy
SELECT * FROM epay_data.transactions LIMIT 10;

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

---

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