Reteno Python API Docs | dltHub

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

Last updated:

Reteno's Debug Mode enables real-time event data logging for app validation. It's found at https://docs.reteno.com/reference/debug-mode. This feature helps developers during app development. The REST API base URL is https://reteno.com/api/v2 and API uses OAuth 2.0 (Authorization Code / Refresh Token flow) to obtain Bearer access tokens; some backend endpoints can be accessed using API keys for server-to-server contact updates..

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


What data can I load from Reteno?

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

ResourceEndpointMethodData selectorDescription
contacts/api/v1/contactsGETRetrieve contacts (list)
contact/api/v1/contact/{id}GETRetrieve single contact by id
groups/api/v1/groupsGETRetrieve groups (segments)
version/api/v2/versionGETAPI/version info (returns object with version fields)
site_script/api/v1/site/scriptGETReturns site script (text/plain)
products_config/api/v1/products/configGETProduct feed configuration (JSON)
broadcasts/api/v1/broadcastsGETList broadcasts
messages_email/api/v1/messages/emailGETList email messages/status
contacts_activity/api/v1/contacts/activityGETContacts activity stream

How do I authenticate with the Reteno API?

Obtain an OAuth2 access token from https://uaa.reteno.com/uaa/oauth/token (authorization_code or refresh_token). Send Authorization: Bearer <ACCESS_TOKEN> header on API requests. Some server-side methods can use API key authentication (API key header described in API-keys docs).

1. Get your credentials

  1. Log into Reteno account and go to Settings -> Integrations / API or Developer area. 2) Register a new application/client to receive Client ID and Client Secret. 3) Use the authorization URL https://uaa.reteno.com/uaa/oauth/authorize?response_type=code&client_id=YOUR_CLIENT_ID&redirect_uri=YOUR_CALLBACK_URL to obtain an authorization code. 4) Exchange code for tokens at https://uaa.reteno.com/uaa/oauth/token with client_id and client_secret to receive access_token and refresh_token.

2. Add them to .dlt/secrets.toml

[sources.reteno_source] client_id = "your_client_id" client_secret = "your_client_secret" access_token = "your_access_token"

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 Reteno 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 reteno_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline reteno_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 contacts and contacts_activity from the Reteno 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 reteno_source(client_secret=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://reteno.com/api/v2", "auth": { "type": "bearer", "access_token": client_secret, }, }, "resources": [ {"name": "contacts", "endpoint": {"path": "api/v1/contacts"}}, {"name": "contacts_activity", "endpoint": {"path": "api/v1/contacts/activity"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="reteno_pipeline", destination="duckdb", dataset_name="reteno_data", ) load_info = pipeline.run(reteno_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("reteno_pipeline").dataset() sessions_df = data.contacts.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM reteno_data.contacts LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("reteno_pipeline").dataset() data.contacts.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 Reteno 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 Reteno?

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