Pin Payments Python API Docs | dltHub
Build a Pin Payments-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Pin Payments API uses HTTP basic authentication with API keys; secret keys have full access, while publishable keys can only store card and bank details. The API supports creating charges and managing recipients and transfers. Responses are in JSON format. The REST API base URL is https://api.pinpayments.com/1 (live) and https://test-api.pinpayments.com/1 (test) and all requests require HTTP Basic auth with your secret API key as the username and an empty password.
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 Pin Payments data in under 10 minutes.
What data can I load from Pin Payments?
Here are some of the endpoints you can load from Pin Payments:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| charges | /charges | GET | response | Paginated list of charges |
| charges_search | /charges/search | GET | response | Search charges by query/date/amount |
| charge | /charges/{charge_token} | GET | response | Get single charge details |
| charges_verify | /charges/verify?session_token={session_token} | GET | response | Verify 3D Secure charge result |
| cards | /cards/{card_token} | GET | response | Get card details (card POST returns response object) |
| recipients | /recipients | GET | response | Paginated list of recipients |
| recipient | /recipients/{recipient_token} | GET | response | Get single recipient details |
| recipient_transfers | /recipients/{recipient_token}/transfers | GET | response | Recipient's transfers (paginated) |
| transfers | /transfers | GET | response | Paginated list of transfers |
| transfers_search | /transfers/search | GET | response | Search transfers by query/date/amount |
| transfer | /transfers/{transfer_token} | GET | response | Get single transfer details |
| transfer_line_items | /transfers/{transfer_token}/line_items | GET | response | Line items for a transfer (paginated) |
How do I authenticate with the Pin Payments API?
Authenticate using HTTP Basic access authentication. Use your secret API key as the username and an empty password; e.g. curl https://test-api.pinpayments.com/1/charges -u your-secret-key:
1. Get your credentials
- Log in to your Pin Payments dashboard 2) Open Account → API Keys (or https://dashboard.pinpayments.com/api_keys) 3) Copy the secret key for the environment you need (live keys for api.pinpayments.com, test keys for test-api.pinpayments.com)
2. Add them to .dlt/secrets.toml
[sources.pin_payments_source] api_key = "your_secret_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 Pin 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 pin_payments_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline pin_payments_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset pin_payments_data The duckdb destination used duckdb:/pin_payments.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline pin_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 charges and transfers from the Pin 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 pin_payments_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.pinpayments.com/1 (live) and https://test-api.pinpayments.com/1 (test)", "auth": { "type": "http_basic", "api_key": api_key, }, }, "resources": [ {"name": "charges", "endpoint": {"path": "charges", "data_selector": "response"}}, {"name": "transfers", "endpoint": {"path": "transfers", "data_selector": "response"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="pin_payments_pipeline", destination="duckdb", dataset_name="pin_payments_data", ) load_info = pipeline.run(pin_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("pin_payments_pipeline").dataset() sessions_df = data.charges.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM pin_payments_data.charges LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("pin_payments_pipeline").dataset() data.charges.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 Pin Payments 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 Pin Payments?
Request dlt skills, commands, AGENT.md files, and AI-native context.