Cardinity Python API Docs | dltHub
Build a Cardinity-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Cardinity's API documentation is available at https://developers.cardinity.com/api/v1/. The API uses OAuth 1.0 for authentication. To create a payment, use the Payment\Create class with required parameters. The REST API base URL is https://api.cardinity.com/v1 and all requests require OAuth 1.0 (0-legged) 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 pip install "dlt[workspace]" and start loading Cardinity data in under 10 minutes.
What data can I load from Cardinity?
Here are some of the endpoints you can load from Cardinity:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| payments | /payments | GET | (top-level array) | List all payments (returns top‑level JSON array of payment objects) |
| payment | /payments/{payment_id} | GET | (object) | Retrieve a single payment by ID |
| refunds | /payments/{payment_id}/refunds | GET | (top-level array) | List refunds for a payment (returns array of refund objects) |
| refund | /payments/{payment_id}/refunds/{refund_id} | GET | (object) | Retrieve a specific refund |
| settlements | /payments/{payment_id}/settlements | GET | (top-level array) | List settlements for a payment |
| settlement | /payments/{payment_id}/settlements/{settlement_id} | GET | (object) | Retrieve a specific settlement |
| chargebacks | /payments/chargebacks | GET | (top-level array) | List all chargebacks |
| chargebacks_of_payment | /payments/{payment_id}/chargebacks | GET | (top-level array) | List chargebacks for a specific payment |
| chargeback | /payments/{payment_id}/chargebacks/{chargeback_id} | GET | (object) | Retrieve a specific chargeback |
| voids | /payments/{payment_id}/voids | GET | (top-level array) | List voids for a specific payment |
How do I authenticate with the Cardinity API?
Cardinity uses OAuth 1.0 (0‑legged / consumer‑key‑only) for API requests. Include an Authorization header in the OAuth format (Authorization: OAuth oauth_consumer_key="", oauth_signature_method="HMAC-SHA1", oauth_timestamp="", oauth_nonce="", oauth_version="1.0", oauth_signature=""). Content-Type: application/json is required for JSON bodies.
1. Get your credentials
- Sign up for a Cardinity merchant account (or test account) at Cardinity.
- In the Cardinity dashboard request API access / API credentials for the account.
- Cardinity will provide a Consumer Key and Consumer Secret for the environment (test and/or live).
- Use those values as consumer_key and consumer_secret in your dlt source config and generate OAuth1 headers for requests.
2. Add them to .dlt/secrets.toml
[sources.cardinity_source] consumer_key = "your_consumer_key_here" consumer_secret = "your_consumer_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 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 Cardinity 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 cardinity_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline cardinity_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset cardinity_data The duckdb destination used duckdb:/cardinity.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline cardinity_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 payments and refunds from the Cardinity 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 cardinity_source(consumer_key, consumer_secret=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.cardinity.com/v1", "auth": { "type": "oauth1", "consumer_key": consumer_key, consumer_secret, }, }, "resources": [ {"name": "payments", "endpoint": {"path": "payments"}}, {"name": "refunds", "endpoint": {"path": "payments/{payment_id}/refunds"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="cardinity_pipeline", destination="duckdb", dataset_name="cardinity_data", ) load_info = pipeline.run(cardinity_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("cardinity_pipeline").dataset() sessions_df = data.payments.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM cardinity_data.payments LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("cardinity_pipeline").dataset() data.payments.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 Cardinity 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 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 Cardinity?
Request dlt skills, commands, AGENT.md files, and AI-native context.