Trengo Python API Docs | dltHub

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

Last updated:

Trengo is a multi‑channel communication platform offering a REST API for managing contacts, conversations, messages, tickets, channels, and webhooks. The REST API base URL is `` and All requests require a Bearer token in the 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 Trengo data in under 10 minutes.


What data can I load from Trengo?

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

ResourceEndpointMethodData selectorDescription
contacts/contactsGETRetrieve a list of contacts
conversations/conversationsGETRetrieve a list of conversations
messages/messagesGETRetrieve a list of messages
tickets/ticketsGETRetrieve a list of tickets
channels/channelsGETRetrieve a list of channels
webhooks/webhooksGETRetrieve a list of webhooks

How do I authenticate with the Trengo API?

Authentication uses API tokens sent in the Authorization header as a Bearer token.

1. Get your credentials

  1. Log into your Trengo account.
  2. Open the dashboard and go to Settings → API.
  3. Click "Create token" and give it a name.
  4. Copy the generated token and store it securely.
  5. Use this token as the value for the Authorization: Bearer header in all API requests.

2. Add them to .dlt/secrets.toml

[sources.trengo_source] api_token = "your_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 Trengo 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 trengo_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline trengo_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 conversations from the Trengo 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 trengo_source(api_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "", "auth": { "type": "bearer", "token": api_token, }, }, "resources": [ {"name": "contacts", "endpoint": {"path": "contacts"}}, {"name": "conversations", "endpoint": {"path": "conversations"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="trengo_pipeline", destination="duckdb", dataset_name="trengo_data", ) load_info = pipeline.run(trengo_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("trengo_pipeline").dataset() sessions_df = data.contacts.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM trengo_data.contacts LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("trengo_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 Trengo 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.


Troubleshooting

Rate Limits

The API allows 120 requests per minute. Responses include rate‑limit headers indicating remaining requests.

Authentication Errors

If the Authorization header is missing or the token is invalid, the API returns a 401 Unauthorized error.

Pagination

The documentation references pagination support; use the provided page and per_page query parameters to navigate through large result sets.

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 Trengo?

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