Fiserv Python API Docs | dltHub
Build a Fiserv-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Fiserv provides various REST APIs for payment processing and merchant services managed through the Fiserv Developer platform. The REST API base URL is https://prod.emea.api.fiservapps.com and Requests typically require an API-Key header and a Message-Signature header, while some use Bearer token authorization..
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 Fiserv data in under 10 minutes.
What data can I load from Fiserv?
Here are some of the endpoints you can load from Fiserv:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| authorisations | /authorisations | GET | List and retrieve authorisations | |
| transactions | /transactions | GET | List and retrieve transactions | |
| fundings | /fundings | GET | List and retrieve fundings | |
| transaction_inquiry | /transactions/{transaction-id} | GET | Retrieve status of an existing transaction | |
| order_inquiry | /orders/{order-id} | GET | Retrieve an order and related transactions |
How do I authenticate with the Fiserv API?
Authentication typically requires an API Key and a Message-Signature header, which is an HMAC-SHA256 signature generated from the API Key, timestamp, request body, and URL path. Some endpoints may also use OAuth 2.0 with a Bearer token in the Authorization header.
1. Get your credentials
- Visit the Fiserv Developer Portal at https://portal.fiserv.dev/ or the relevant Developer Studio workspace. 2. Register for an account using your business email address and complete any required email verification and Multi-Factor Authentication (MFA) setup. 3. Log in to your dashboard/workspace. 4. Navigate to the 'API Keys', 'Credentials', or 'Applications' management section. 5. Click 'Create new key' (or 'Create API key'). 6. Select the target environment (Sandbox for testing, or Production for live use). 7. Provide a descriptive name for the application and finalize the creation to retrieve your API Key and Secret. Note: Production access may require additional validation, merchant account linking, or manual approval from Fiserv support.
2. Add them to .dlt/secrets.toml
[sources.fiserv_source] api_key = "your_api_key_here" api_secret = "your_api_secret_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 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 Fiserv 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 fiserv_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline fiserv_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset fiserv_data The duckdb destination used duckdb:/fiserv.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 authorisations and payments from the Fiserv 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 fiserv_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://prod.emea.api.fiservapps.com", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "authorisations", "endpoint": {"path": "authorisations"}}, {"name": "transactions", "endpoint": {"path": "transactions"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="fiserv_pipeline", destination="duckdb", dataset_name="fiserv_data", ) load_info = pipeline.run(fiserv_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("fiserv_pipeline").dataset() sessions_df = data.authorisations.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM fiserv_data.authorisations LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("fiserv_pipeline").dataset() data.authorisations.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 Fiserv 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 Fiserv?
Request dlt skills, commands, AGENT.md files, and AI-native context.