SubscriptionFlow Python API Docs | dltHub

Build a SubscriptionFlow-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

SubscriptionFlow offers a RESTful API for managing subscriptions. It uses OAuth for authentication and provides comprehensive documentation and Postman collections for integration. The API supports creating, managing, and updating subscriptions. The REST API base URL is https://{your_instance}.subscriptionflow.com/api/v1 and All requests (except /oauth/token) require a Bearer access token (OAuth2 client_credentials)..

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 SubscriptionFlow data in under 10 minutes.


What data can I load from SubscriptionFlow?

Here are some of the endpoints you can load from SubscriptionFlow:

ResourceEndpointMethodData selectorDescription
customers/customersGETdataList customers
customers_with_relations/customers/with-relationsGETdataCustomers with relations
customers_related/customers/{id}/relatedGETdataRelated resources for a customer
subscriptions/subscriptionsGETdataList subscriptions
subscriptions_with_relations/subscriptions/with-relationsGETdataSubscriptions with related data
payment_methods/payment-methodsGETdataList payment methods
contacts/contactsGETdataList contacts
usages/usagesGETdataList usages
oauth_token/oauth/tokenPOSTObtain OAuth2 access token (grant_type=client_credentials)

How do I authenticate with the SubscriptionFlow API?

Obtain a bearer token by POSTing client_id, client_secret and grant_type=client_credentials to https://{your_instance}.subscriptionflow.com/oauth/token. Include the returned access token in the Authorization header as: Authorization: Bearer <access_token>.

1. Get your credentials

  1. In your SubscriptionFlow instance admin/developer console create an OAuth client (OAuth customer) to obtain client_id and client_secret.
  2. Make a POST to https://{your_instance}.subscriptionflow.com/oauth/token with form-data: client_id, client_secret, grant_type=client_credentials to receive an access token.
  3. Use the access token in the Authorization header for API requests. Regenerate token when it expires.

2. Add them to .dlt/secrets.toml

[sources.subscription_flow_source] client_id = "your_client_id_here" client_secret = "your_client_secret_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 SubscriptionFlow 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 subscription_flow_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline subscription_flow_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset subscription_flow_data The duckdb destination used duckdb:/subscription_flow.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

dlt pipeline subscription_flow_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 SubscriptionFlow 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 subscription_flow_source(client_secret=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://{your_instance}.subscriptionflow.com/api/v1", "auth": { "type": "bearer", "token": client_secret, }, }, "resources": [ {"name": "customers", "endpoint": {"path": "customers", "data_selector": "data"}}, {"name": "subscriptions", "endpoint": {"path": "subscriptions", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="subscription_flow_pipeline", destination="duckdb", dataset_name="subscription_flow_data", ) load_info = pipeline.run(subscription_flow_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("subscription_flow_pipeline").dataset() sessions_df = data.customers.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM subscription_flow_data.customers LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("subscription_flow_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 SubscriptionFlow data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample 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 SubscriptionFlow?

Request dlt skills, commands, AGENT.md files, and AI-native context.