Montonio Python API Docs | dltHub
Build a Montonio-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Montonio is a payments platform that provides APIs (Stargate) to accept and manage online payments, payment methods, payment links and related operations. The REST API base URL is https://stargate.montonio.com/api and all requests require a Bearer JWT (signed with store Secret Key) 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 pip install "dlt[workspace]" and start loading Montonio data in under 10 minutes.
What data can I load from Montonio?
Here are some of the endpoints you can load from Montonio:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| stores_payment_methods | /stores/payment-methods | GET | paymentMethods | Fetch enabled payment methods (returns list in paymentMethods key) |
| payment_links | /payment-links | GET | data | List payment links (response wrapper uses data key for records) |
| payments | /payments | GET | data | List payments (response wrapper uses data key) |
| orders | /orders | GET | data | List orders (response wrapper uses data key) |
| refunds | /refunds | GET | data | List refunds (response wrapper uses data key) |
| payment_links_create | /payment-links | POST | Create payment link (included for completeness) |
How do I authenticate with the Montonio API?
Authentication uses short-lived JWT Bearer tokens signed with your store Secret Key. Include the token in the Authorization header as: Authorization: Bearer .
1. Get your credentials
- Sign into the Montonio Partner System (dashboard). 2) Locate your Store/Access Key and Secret Key (Access Key used as JWT payload, Secret Key to sign JWT). 3) Create a JWT with payload {"accessKey":"YOUR_ACCESS_KEY","exp": } signed with HS256 using your Secret Key. 4) Use the JWT as Bearer token in Authorization header for API requests.
2. Add them to .dlt/secrets.toml
[sources.montonio_payments_source] access_key = "YOUR_ACCESS_KEY" secret_key = "YOUR_SECRET_KEY"
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 Montonio 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 montonio_payments_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline montonio_payments_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset montonio_payments_data The duckdb destination used duckdb:/montonio_payments.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline montonio_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 stores_payment_methods and payments from the Montonio 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 montonio_payments_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://stargate.montonio.com/api", "auth": { "type": "bearer", "token": token, }, }, "resources": [ {"name": "stores_payment_methods", "endpoint": {"path": "stores/payment-methods", "data_selector": "paymentMethods"}}, {"name": "payments", "endpoint": {"path": "payments", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="montonio_payments_pipeline", destination="duckdb", dataset_name="montonio_payments_data", ) load_info = pipeline.run(montonio_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("montonio_payments_pipeline").dataset() sessions_df = data.stores_payment_methods.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM montonio_payments_data.stores_payment_methods LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("montonio_payments_pipeline").dataset() data.stores_payment_methods.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 Montonio 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.
Troubleshooting
Authentication failures
If you receive 401 or response body containing STORE_NOT_FOUND or Unauthorized, verify that your JWT token payload contains correct accessKey and hasn't expired, and that it was signed with the correct Secret Key (HS256). Ensure Authorization header is exactly: Authorization: Bearer .
Rate limits and error responses
The API returns standard HTTP error codes (4xx/5xx). For 4xx errors inspect the JSON message field for error codes. Example returned error body for auth issues: {"statusCode":401,"message":"STORE_NOT_FOUND","error":"Unauthorized"}.
Sandbox vs Production base URLs
Use https://stargate.montonio.com/api for production; sandbox requests in examples use https://sandbox-stargate.montonio.com/api. Ensure you point to the correct host for environment.
Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.
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 Montonio?
Request dlt skills, commands, AGENT.md files, and AI-native context.