Load Lemon Squeezy data to DuckDB
Build a Lemon Squeezy to DuckDB pipeline with your coding agent. One prompt scaffolds it with the dltHub AI harness, plus the Lemon Squeezy API base URL, auth, endpoints, and incremental loading.
Lemon Squeezy is a merchant-of-record platform providing an API for managing stores, products, subscriptions, and orders. Everything needed to build a working Lemon Squeezy → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.
Build your Lemon Squeezy to DuckDB pipeline
Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.
PromptRunuvx dlthub-init@latestto build a pipeline from Lemon Squeezy to DuckDB and run it on dltHub
That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Lemon Squeezy API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →
Prefer to write it yourself? Every fact the agent uses is below.
Lemon Squeezy API at a glance
| Base URL | https://api.lemonsqueezy.com/v1 |
| Example endpoint | GET v1/orders |
| Records found at | data |
| Authentication | all requests require a Bearer token in the Authorization header along with specific content-type headers — sent in the Authorization header, prefixed Bearer |
| Also required | Accept, Content-Type |
| Pagination | Page-number via page[number], next cursor at none, page size via page[size] (default 10, max 100). Pagination is page-based (not cursor-token based). Continue paging by following links.next from the response; if links.next is absent you are on the last page. Page parameters are URL query parameters: page[number] selects which page to retrieve, and page[size] controls results per page (min 1, max 100; default 10). |
| Incremental field | updated_at |
| Record id | id |
| API reference | https://docs.lemonsqueezy.com/api |
These values come from the Lemon Squeezy API reference — the authoritative source if anything here looks out of date.
How do I authenticate with the Lemon Squeezy API?
Lemon Squeezy uses Bearer authentication, requiring an Authorization header (Bearer {api_key}), as well as Accept and Content-Type headers set to application/vnd.api+json.
1. Get your credentials
To obtain API credentials, log in to your Lemon Squeezy dashboard and navigate to Settings > API in the left-hand menu. Click the + New API Key button, provide a descriptive name for the key, and click Create API Key. Ensure you copy the key immediately, as it is only displayed once.
2. Add them to .dlt/secrets.toml
[sources.lemon_squeezy_source] api_key = "your_api_key_here"
dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.
What Lemon Squeezy data can I load into DuckDB?
These are the Lemon Squeezy endpoints dlt can load into DuckDB:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| orders | /v1/orders | GET | data | Returns a list of orders |
| products | /v1/products | GET | data | Returns a list of products |
| customers | /v1/customers | GET | data | Returns a list of customers |
| subscriptions | /v1/subscriptions | GET | data | Returns a list of subscriptions |
| usage_records | /v1/usage-records | GET | data | Returns a list of usage records |
How do I load only new Lemon Squeezy records?
Lemon Squeezy exposes updated_at on v1/orders, so dlt can request only the records that changed since the last run. Set it as the cursor_path and dlt tracks the high-water mark for you between runs.
{"name": "orders", "endpoint": { "path": "v1/orders", "data_selector": "data", "incremental": {"cursor_path": "updated_at", "initial_value": "2024-01-01T00:00:00Z"}, }}
On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.
What does the generated Lemon Squeezy pipeline look like?
A standard dlt REST API pipeline — the same code you would write by hand, loading products and subscriptions from the Lemon Squeezy API into DuckDB:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def lemon_squeezy_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.lemonsqueezy.com/v1", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "orders", "endpoint": {"path": "v1/orders", "data_selector": "data"}}, {"name": "products", "endpoint": {"path": "v1/products", "data_selector": "data"}} ], } yield from rest_api_resources(config) def load_lemon_squeezy_to_duckdb() -> None: pipeline = dlt.pipeline( pipeline_name="lemon_squeezy_pipeline", destination="duckdb", dataset_name="lemon_squeezy_data", ) load_info = pipeline.run(lemon_squeezy_source()) print(load_info) if __name__ == "__main__": load_lemon_squeezy_to_duckdb()
Run it with python lemon_squeezy_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.
How do I query Lemon Squeezy data in DuckDB?
dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("lemon_squeezy_pipeline").dataset() df = data.orders.df() print(df.head())
SQL:
SELECT * FROM lemon_squeezy_data.orders LIMIT 10;
See querying your data with dataset and exploring it in marimo notebooks.
How do I deploy the Lemon Squeezy to DuckDB pipeline in production?
The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.
- Deploy & schedule — run the pipeline as a managed job with automatic retries.
- Monitor — observable job queues, alerting, and load metrics for every run.
- Transform — promote raw Lemon Squeezy loads into governed, documented models.
- Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.
What other destinations can I load Lemon Squeezy data to?
dlt loads into any of these — only the destination argument changes:
| Destination | Example value |
|---|---|
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.
Next steps
Was this page helpful?
Community Hub
Need more dlt context for Lemon Squeezy to DuckDB?
Request dlt skills, commands, AGENT.md files, and AI-native context.