Zen Payments Python API Docs | dltHub

Build a Zen Payments-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

Zen Payments API enables integration with payment processing; it supports creating, settling, canceling, and retrieving payments; also offers over 100 payment methods. The REST API base URL is https://api.zen.com/v1 and all requests require an Authorization header with the Terminal API key.

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 pip install "dlt[workspace]" and start loading Zen Payments data in under 10 minutes.


What data can I load from Zen Payments?

Here are some of the endpoints you can load from Zen Payments:

ResourceEndpointMethodData selectorDescription
transactions/transactionsGETList transactions (retrieve transactions list)
transaction/transactions/{transactionId}GETRetrieve a single transaction
customers/customersGETList customers
customer/customers/{customerId}GETRetrieve a single customer
payments/payments/{paymentId}GETGet payment details (payments API example shows payment object returned)
payment_links/payment-linksGETFetch list of Payment-by-Link (PBL) links
payouts/payoutsGETList payouts
currencies/currenciesGETList available currencies and exchange info

How do I authenticate with the Zen Payments API?

All requests require an Authorization header containing the merchant’s Terminal API key (the Terminal API key value from your ZEN merchant dashboard). Requests must use HTTPS and send/accept JSON (Content-Type: application/json, Accept: application/json).

1. Get your credentials

  1. Sign in to your ZEN merchant dashboard at https://my.zen.com.
  2. Go to the API / Integration or Developer section of the dashboard (often labeled API Keys or Terminal API Key).
  3. Create or copy the Terminal API key for the environment (test or production) you will use.
  4. Ensure your merchant account has API access and that any IP whitelisting required by ZEN is configured.

2. Add them to .dlt/secrets.toml

[sources.zen_payments_source] api_key = "your_terminal_api_key_here"

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 venv && source .venv/bin/activate uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

dlt 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:

dlt ai toolkit rest-api-pipeline install

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 Zen 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:

python zen_payments_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline zen_payments_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset zen_payments_data The duckdb destination used duckdb:/zen_payments.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

dlt pipeline zen_payments_pipeline 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 transactions and customers from the Zen 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 zen_payments_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.zen.com/v1", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "transactions", "endpoint": {"path": "transactions"}}, {"name": "customers", "endpoint": {"path": "customers"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="zen_payments_pipeline", destination="duckdb", dataset_name="zen_payments_data", ) load_info = pipeline.run(zen_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("zen_payments_pipeline").dataset() sessions_df = data.transactions.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM zen_payments_data.transactions LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("zen_payments_pipeline").dataset() data.transactions.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 Zen Payments data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample 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 Workbench:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-runtime — Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install

Was this page helpful?

Community Hub

Need more dlt context for Zen Payments?

Request dlt skills, commands, AGENT.md files, and AI-native context.