Telq Tele Python API Docs | dltHub

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

Last updated:

TelQ's REST API allows for automated SMS testing and integration, providing detailed test results and configurations for SMS delivery. The API supports various parameters for customization and includes a TTL validity for test requests. For setup and usage, refer to the official documentation and integration guides. The REST API base URL is https://api.telqtele.com/v3/client and all requests require a Bearer token obtained with App ID and App Key.

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


What data can I load from Telq Tele?

Here are some of the endpoints you can load from Telq Tele:

ResourceEndpointMethodData selectorDescription
testsclient/testsGETcontentRetrieve paged MT test results (supports from/to, page, size, order)
sessionsclient/sessionsGETcontentRetrieve paged sessions
suppliersclient/suppliersGETcontentRetrieve paged suppliers
sessions_suppliersclient/sessions-suppliersGETcontentRetrieve suppliers status list
cli_networksclient/cli/networksGETGet list of CLI networks (top-level array)
test_by_idclient/tests/{id}GETn/aGet individual test result by ID
cli_test_by_idclient/cli/tests/{testId}GETn/aGet CLI test result by ID
tokenclient/tokenPOSTn/aObtain Bearer token using appId and appKey

How do I authenticate with the Telq Tele API?

TelQ uses App ID and App Key to obtain a short-lived Bearer token via the /client/token endpoint; include the token in the Authorization header as 'Authorization: Bearer ' for all subsequent requests (token TTL 86400 seconds).

1. Get your credentials

  1. Log in to app.telqtele.com. 2) Go to Integration Settings > API (or API Menu). 3) Enable API if disabled, click Generate next to 'App key' and copy App ID and App Key. 4) Use these to call POST https://api.telqtele.com/v3/client/token with JSON body {"appId": , "appKey": ""} to receive the Bearer token.

2. Add them to .dlt/secrets.toml

[sources.telq_tele_source] app_id = "your_app_id_here" app_key = "your_app_key_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 Telq Tele 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 telq_tele_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline telq_tele_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 tests and cli_networks from the Telq Tele 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 telq_tele_source(app_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.telqtele.com/v3/client", "auth": { "type": "bearer", "token": app_key, }, }, "resources": [ {"name": "tests", "endpoint": {"path": "client/tests", "data_selector": "content"}}, {"name": "networks", "endpoint": {"path": "client/cli/networks"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="telq_tele_pipeline", destination="duckdb", dataset_name="telq_tele_data", ) load_info = pipeline.run(telq_tele_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("telq_tele_pipeline").dataset() sessions_df = data.tests.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM telq_tele_data.tests LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("telq_tele_pipeline").dataset() data.tests.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 Telq Tele 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 Telq Tele?

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