Pabbly Subscriptions Python API Docs | dltHub
Build a Pabbly Subscriptions-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Pabbly Subscriptions is a SaaS subscription and recurring billing platform that provides a REST API to manage customers, plans, subscriptions, invoices, payments and webhooks. The REST API base URL is https://subscriptions.pabbly.com/api and all requests require a Bearer token for authentication.
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 Pabbly Subscriptions data in under 10 minutes.
What data can I load from Pabbly Subscriptions?
Here are some of the endpoints you can load from Pabbly Subscriptions:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| customers | subscriptions.pabbly.com/api/customers | GET | customers | List customers |
| subscriptions | subscriptions.pabbly.com/api/subscriptions | GET | subscriptions | List subscriptions |
| plans | subscriptions.pabbly.com/api/plans | GET | plans | List product plans |
| invoices | subscriptions.pabbly.com/api/invoices | GET | invoices | List invoices |
| transactions | subscriptions.pabbly.com/api/transactions | GET | transactions | List payment transactions |
| webhooks | subscriptions.pabbly.com/api/webhooks | GET | webhooks | List configured webhooks |
How do I authenticate with the Pabbly Subscriptions API?
The API uses HTTP Bearer token authentication. Include your token in the Authorization header as: Authorization: Bearer <YOUR_TOKEN>.
1. Get your credentials
- Sign in at https://accounts.pabbly.com/login.
- Open the Pabbly Subscriptions dashboard.
- Navigate to the Integrations or Developer/API section.
- Create or copy the Developer/API Bearer token.
- Store the token securely and use it in the Authorization header for API calls.
2. Add them to .dlt/secrets.toml
[sources.pabbly_subscriptions_source] api_token = "your_bearer_token_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 Pabbly Subscriptions 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 pabbly_subscriptions_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline pabbly_subscriptions_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset pabbly_subscriptions_data The duckdb destination used duckdb:/pabbly_subscriptions.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline pabbly_subscriptions_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 customers and subscriptions from the Pabbly Subscriptions 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 pabbly_subscriptions_source(api_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://subscriptions.pabbly.com/api", "auth": { "type": "bearer", "token": api_token, }, }, "resources": [ {"name": "customers", "endpoint": {"path": "customers", "data_selector": "customers"}}, {"name": "subscriptions", "endpoint": {"path": "subscriptions", "data_selector": "subscriptions"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="pabbly_subscriptions_pipeline", destination="duckdb", dataset_name="pabbly_subscriptions_data", ) load_info = pipeline.run(pabbly_subscriptions_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("pabbly_subscriptions_pipeline").dataset() sessions_df = data.subscriptions.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM pabbly_subscriptions_data.subscriptions LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("pabbly_subscriptions_pipeline").dataset() data.subscriptions.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 Pabbly Subscriptions 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/403 responses verify the Authorization header is present and the token is correct. Regenerate the Developer/API token from your Pabbly dashboard if necessary.
Rate limits and quotas
Pabbly enforces daily API call limits (documentation references a 10000 requests/day limit). Expect 429 Too Many Requests when quotas are exceeded — implement retry/backoff.
Pagination
List endpoints typically return arrays inside a top-level key (e.g., "customers", "subscriptions"). Check response for pagination fields (page, per_page, total) and use query parameters (page, limit) if supported.
Common errors
400 Bad Request — malformed input. 401 Unauthorized — missing/invalid token. 403 Forbidden — insufficient permissions. 404 Not Found — resource missing. 429 Too Many Requests — rate limit exceeded. 500/502/503 — server errors; retry later.
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 Pabbly Subscriptions?
Request dlt skills, commands, AGENT.md files, and AI-native context.