Fiserv Optis Python API Docs | dltHub
Build a Fiserv Optis-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Fiserv Optis is a financial services platform providing RESTful APIs for card issuing, transaction processing, and management across various banking domains. The REST API base URL is https://prod.api.fiservapps.com and API requests generally require a Bearer token or HMAC signature in the Authorization header..
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 Optis data in under 10 minutes.
What data can I load from Fiserv Optis?
Here are some of the endpoints you can load from Fiserv Optis:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| payment_history | /payments/v2/paymentHistory | GET | Retrieves payment history for a customer account. | |
| payment_details | /payments/v2/paymentDetails | GET | Retrieves specific payment details. | |
| auto_payments | /payments/v2/autoPayments | GET | Retrieves auto-payment configurations. | |
| approved_queue | /adjustments/v2/approvedQueue | GET | Retrieves the queue of approved adjustments. | |
| rejected_queue | /adjustments/v2/rejectedQueue | GET | Retrieves the queue of rejected adjustments. |
How do I authenticate with the Fiserv Optis API?
Authentication is performed by obtaining a JWT access token via a POST request to a dedicated endpoint, which is then passed in the Authorization header as a Bearer token. For other Fiserv API products that use HMAC, a signature must be generated using an API Key, timestamp, request body, and URL path, then passed in the Authorization header.
1. Get your credentials
- Navigate to the Fiserv Developer Portal at https://fiserv.dev/. 2. Register for an account using your business email address and complete the identity verification/MFA process. 3. Log in to the Developer Portal. 4. Navigate to the API Keys page. 5. Click Create new key to initiate a request. 6. Select your environment (Sandbox for testing, Production for live operations). 7. Provide required details (e.g., Merchant ID, StoreID) if requesting a Production key. 8. Once approved/generated, the portal will display your API Key and Secret. Securely store these, as the secret may only be visible once.
2. Add them to .dlt/secrets.toml
[sources.fiserv_optis_source] access_token = "REPLACE_ME"
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 Optis 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_optis_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline fiserv_optis_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset fiserv_optis_data The duckdb destination used duckdb:/fiserv_optis.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/v2/paymentHistory and /payments/v2/rightTimePayment from the Fiserv Optis 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_optis_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://prod.api.fiservapps.com", "auth": {"type": "bearer", "token": access_token}, }, "resources": [ {"name": "payment_history", "endpoint": {"path": "payments/v2/paymentHistory"}}, {"name": "payment_details", "endpoint": {"path": "payments/v2/paymentDetails"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="fiserv_optis_pipeline", destination="duckdb", dataset_name="fiserv_optis_data", ) load_info = pipeline.run(fiserv_optis_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_optis_pipeline").dataset() sessions_df = data.payment_history.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM fiserv_optis_data.payment_history LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("fiserv_optis_pipeline").dataset() data.payment_history.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 Optis 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 Optis?
Request dlt skills, commands, AGENT.md files, and AI-native context.