Paymentology Sprint Python API Docs | dltHub

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

Last updated:

Paymentology Sprint's Card API allows issuing, managing, and securing cards. It includes methods for authorizations and reconciliation. The API also supports tokenization and dispute handling. The REST API base URL is https://apidev.voucherengine.com/card/v1/xmlrpc.cfm and Authentication uses client‑specific token/secret credentials generated via Paymentology’s token generation methods rather than a standard Bearer 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 pip install "dlt[workspace]" and start loading Paymentology Sprint data in under 10 minutes.


What data can I load from Paymentology Sprint?

Here are some of the endpoints you can load from Paymentology Sprint:

ResourceEndpointMethodData selectorDescription
list_cardsListCardsGETReturn a list of all cards linked to a customer reference
card_detailCardDetailGETGet details of a card identified by its tracking number
list_tokensListTokensGETReturns all tokens linked to a card
most_recent_transactionsMostRecentTransactionsGETProvides the latest transactions on a card
statementStatementGETRetrieve the statement of a card or pocket

How do I authenticate with the Paymentology Sprint API?

Authentication is performed by supplying the token and secret generated for the client in each RPC call; no universal HTTP Authorization header is defined.

1. Get your credentials

  1. Contact your Paymentology account manager or sales representative to request API access.
  2. Ask for a developer sandbox or production client ID and secret.
  3. Use the "GenerateTimeBasedSecret" method documented in the API reference to create a time‑based token.
  4. Store the token (and secret, if required) in your dlt secrets.toml file.
  5. Include the token in each RPC call as described in the API documentation.

2. Add them to .dlt/secrets.toml

[sources.paymentology_sprint_source] api_key = "your_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 Paymentology Sprint 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 paymentology_sprint_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline paymentology_sprint_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 list_cards and card_detail from the Paymentology Sprint 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 paymentology_sprint_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://apidev.voucherengine.com/card/v1/xmlrpc.cfm", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "list_cards", "endpoint": {"path": "ListCards"}}, {"name": "card_detail", "endpoint": {"path": "CardDetail"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="paymentology_sprint_pipeline", destination="duckdb", dataset_name="paymentology_sprint_data", ) load_info = pipeline.run(paymentology_sprint_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("paymentology_sprint_pipeline").dataset() sessions_df = data.list_cards.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM paymentology_sprint_data.list_cards LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("paymentology_sprint_pipeline").dataset() data.list_cards.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 Paymentology Sprint 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 Paymentology Sprint?

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