Stripo Python API Docs | dltHub

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

Last updated:

The Stripo API allows auto-generation of emails using external data sources. Authentication requires a Plugin ID, Secret Key, userId, and role. The API supports generating and retrieving email templates. The REST API base URL is https://my.stripo.email/emailgeneration/v1 and token-based API authentication (JWT token issued by plugin auth endpoint).

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


What data can I load from Stripo?

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

ResourceEndpointMethodData selectorDescription
emailsemail (generate)POST https://my.stripo.email/emailgeneration/v1/email(response body object; generated email object)Generate an email from modules and external data using transformers
emails_listemailGET https://my.stripo.email/emailgeneration/v1/email(list location depends on response; documentation shows "Get the list of emails" — response contains emails array)Get the list of emails
email_by_idemail/{id}GET https://my.stripo.email/emailgeneration/v1/email/{id}(single email object)Get email by ID
raw_htmlemail/{id}/rawGET https://my.stripo.email/emailgeneration/v1/email/{id}/raw(raw html string or object)Get raw HTML & CSS for email
validate_tokenvalidateGET https://my.stripo.email/emailgeneration/v1/validate(validation result object)Validate the JWT token and access permissions

How do I authenticate with the Stripo API?

Obtain a JWT token by calling the plugin auth endpoint with pluginId, secretKey, userId and role (use role "API" for server-to-server). Include the returned token in requests to the emailgeneration endpoints (token passed in request headers for validation/authorization).

1. Get your credentials

  1. Sign in to Stripo dashboard and create or open your Plugin. 2) Copy pluginId and secretKey from Plugin details. 3) From your backend, POST JSON {"pluginId","secretKey","userId","role":"API"} to https://plugins.stripo.email/api/v1/auth to receive {"token":"..."}. 4) Use that token in request headers for subsequent API calls.

2. Add them to .dlt/secrets.toml

[sources.stripo_source] plugin_id = "your_plugin_id" secret_key = "your_secret_key" user_id = "1"

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 Stripo 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 stripo_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline stripo_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 emails and emails_list from the Stripo 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 stripo_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://my.stripo.email/emailgeneration/v1", "auth": { "type": "bearer", "token": token, }, }, "resources": [ {"name": "emails", "endpoint": {"path": "email"}}, {"name": "email_by_id", "endpoint": {"path": "email/{id}"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="stripo_pipeline", destination="duckdb", dataset_name="stripo_data", ) load_info = pipeline.run(stripo_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("stripo_pipeline").dataset() sessions_df = data.emails.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM stripo_data.emails LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("stripo_pipeline").dataset() data.emails.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 Stripo 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 Stripo?

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