Load Mambu data to DuckDB

Mambu is a cloud banking platform providing a REST API for core banking operations and management. Everything needed to build a working Mambu → 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 Mambu 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 Mambu 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 Mambu 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.

---

Mambu API at a glance

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

---

How do I authenticate with the Mambu API?

Mambu supports Basic authentication, which requires an Authorization header with a Base64-encoded 'username:password' string prefixed by 'Basic '. Alternatively, API keys are passed in the 'apiKey' header.

1. Get your credentials

To generate API keys, you must use the API Consumers feature. Navigate to Administration > Access > API Consumers in the Mambu UI. Select 'Add consumer' to create a new API consumer, then select 'Actions' > 'Manage keys' for the created consumer. Click 'Generate' in the Manage Keys dialog to create a new API key. Note that this may be an Early Access feature depending on your contract, requiring contact with your Mambu Customer Success Manager. Alternative basic authentication uses Mambu UI login credentials (username and password) sent via the 'Authorization' header as a base64-encoded 'username:password' string.

2. Add them to .dlt/secrets.toml

Copy
[sources.mambu_source]
mambu_base_url = "https://your-tenant-name.mambu.com"
mambu_api_key = "your-api-key-here"
# If using basic auth instead:
# mambu_username = "your-username"
# mambu_password = "your-password"

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

These are the Mambu endpoints dlt can load into DuckDB:

---

How do I load only new Mambu records?

Mambu exposes transactionId on loans/transactions:search, 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": "loan_transactions_search", "endpoint": {
    "path": "loans/transactions:search",
    "incremental": {"cursor_path": "transactionId", "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 Mambu pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /users and /loans from the Mambu API into DuckDB:

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

@dlt.source
def mambu_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://TENANT_NAME.mambu.com/api",
            "auth": {"type": "http_basic", "username": "REPLACE_ME", "password": api_key},
        },
        "resources": [
            {"name": "loan_transactions_search", "endpoint": {"path": "loans/transactions:search"}},
            {"name": "journal_entries_search", "endpoint": {"path": "gljournalentries:search"}}
        ],
    }
    yield from rest_api_resources(config)


def load_mambu_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="mambu_pipeline",
        destination="duckdb",
        dataset_name="mambu_data",
    )
    load_info = pipeline.run(mambu_source())
    print(load_info)


if __name__ == "__main__":
    load_mambu_to_duckdb()

Run it with python mambu_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 Mambu 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("mambu_pipeline").dataset()
df = data.loans_transactions_search.df()
print(df.head())

SQL:

Copy
SELECT * FROM mambu_data.loans_transactions_search LIMIT 10;

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

---

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