Loop Admin Python API Docs | dltHub
Build a Loop Admin-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Loop API documentation provides endpoints for managing subscriptions, generating tokens, and handling webhooks. Key resources include API reference and interactive guides. For more details, consult the official Loop API reference. The REST API base URL is https://api.loopsubscriptions.com and All Admin API requests require an API token passed via the X-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 Loop Admin data in under 10 minutes.
What data can I load from Loop Admin?
Here are some of the endpoints you can load from Loop Admin:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| customers | /admin/customers | GET | Read all customers (list customers and subscription counts) | |
| customer_details | /admin/customer/{customer_id} | GET | Read customer details | |
| subscriptions | /admin/subscription | GET | Read all subscriptions | |
| subscription_details | /admin/subscription/{subscription_id} | GET | Read subscription details | |
| products | /admin/2023-10/product | GET | List products and selling-plan mapping status | |
| past_orders | /admin/orders/past | GET | Read all past/subscription orders | |
| scheduled_orders | /admin/orders/scheduled | GET | Read all scheduled orders | |
| frequencies | /admin/frequencies | GET | List available frequencies | |
| activity_logs | /admin/activity-logs | GET | List activity logs for the store | |
| cancellation_reasons | /admin/cancellation-reasons | GET | List cancellation reasons |
How do I authenticate with the Loop Admin API?
Loop Admin API uses per-store API tokens generated in the Loop Admin portal. Include the token in requests as the X-Authorization header (X-Authorization: <api_token>); all requests must be HTTPS.
1. Get your credentials
- Log into your Loop Admin portal for the store.
- Go to Settings → Manage API tokens (or Generate Admin API tokens).
- Click “Generate new token”, give it a descriptive name and select scopes/permissions required.
- Copy the generated token immediately (store it securely); use it in the X-Authorization header for API requests.
2. Add them to .dlt/secrets.toml
[sources.loop_admin_source] api_key = "your_loop_admin_api_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 Loop Admin 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 loop_admin_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline loop_admin_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset loop_admin_data The duckdb destination used duckdb:/loop_admin.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline loop_admin_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 Loop Admin 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 loop_admin_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.loopsubscriptions.com", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "customers", "endpoint": {"path": "admin/customers"}}, {"name": "subscriptions", "endpoint": {"path": "admin/subscription"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="loop_admin_pipeline", destination="duckdb", dataset_name="loop_admin_data", ) load_info = pipeline.run(loop_admin_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("loop_admin_pipeline").dataset() sessions_df = data.customers.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM loop_admin_data.customers LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("loop_admin_pipeline").dataset() data.customers.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 Loop Admin 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 Loop Admin?
Request dlt skills, commands, AGENT.md files, and AI-native context.