Mambu Payments Python API Docs | dltHub
Build a Mambu Payments-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Mambu Payments API allows financial institutions to manage and automate payment processes through a RESTful interface. The REST API base URL is https://TENANT_NAME.mambu.com/api/v1 and all requests require an 'apikey' header containing a unique UUID token.
dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading Mambu Payments data in under 10 minutes.
What data can I load from Mambu Payments?
Here are some of the endpoints you can load from Mambu Payments:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| payments | /payments | POST | Create a payment initiation request | |
| incoming_messages | /payments/incoming | POST | Route incoming messages to the Payments API | |
| payment_details | /payments/{id} | GET | Retrieve details of a specific payment order | |
| collection_details | /collections/{id} | GET | Retrieve collection details | |
| payments_status | /payments/{id}/status | GET | Retrieve the current status of a payment |
How do I authenticate with the Mambu Payments API?
Requests must authenticate using an API key provided in the 'apikey' header, which is generated via an API consumer with the required permissions.
1. Get your credentials
To obtain API credentials for Mambu Payments, follow these steps in the Mambu dashboard: 1. Navigate to Administration > Access > API Consumers. 2. Locate or create an API consumer that has the Manage Payments (MANAGE_PAYMENTS) permission assigned to it. 3. Select Actions > Manage keys for that consumer. 4. In the Manage Keys dialog, select Generate. 5. Optionally set an expiration time (TTL) and select Generate again. 6. Copy and store the generated API key immediately, as it will not be retrievable after the dialog is closed.
2. Add them to .dlt/secrets.toml
[sources.mambu_payments_source] api_key = "your_api_key_here" tenant_url = "https://your-tenant-name.mambu.com"
dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.
How do I set up and run the pipeline?
Set up a virtual environment and install dlt:
uv init uv add "dlt[hub]"
1. Install the dlt AI harness:
uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex
This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →
2. Install the rest-api-pipeline toolkit:
uv run dlthub ai toolkit install rest-api-pipeline
This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →
3. Start LLM-assisted coding:
Use /find-source to load data from the Mambu Payments API into DuckDB.
The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.
4. Run the pipeline:
uv run python mambu_payments_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline mambu_payments_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset mambu_payments_data The duckdb destination used duckdb:/mambu_payments.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
uv run dlthub show
This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.
Python pipeline example
This example loads /payments/incoming and /api/v1/collections from the Mambu Payments API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def mambu_payments_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://TENANT_NAME.mambu.com/api/v1", "auth": {"type": "api_key", "api_key": api_key, "name": "apikey", "location": "header"}, }, "resources": [ {"name": "loan_transactions_search", "endpoint": {"path": "loans/transactions:search", "data_selector": "items"}}, {"name": "journal_entries_search", "endpoint": {"path": "gljournalentries:search", "data_selector": "items"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="mambu_payments_pipeline", destination="duckdb", dataset_name="mambu_payments_data", ) load_info = pipeline.run(mambu_payments_source()) print(load_info)
To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.
How do I query the loaded data?
Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("mambu_payments_pipeline").dataset() sessions_df = data.loans/transactions:search.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM mambu_payments_data.loans/transactions:search LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("mambu_payments_pipeline").dataset() data.loans/transactions:search.df().head()
See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.
What destinations can I load Mambu Payments data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI harness:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-platform— Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform
Was this page helpful?
Community Hub
Need more dlt context for Mambu Payments?
Request dlt skills, commands, AGENT.md files, and AI-native context.