Talon.One Python API Docs | dltHub

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

Last updated:

Talon.One provides Third-party, Integration, and Management REST APIs for sending external information to its Rule Engine and retrieving data in high-load environments. The REST API base URL is https://integration.talon.one and Authentication for Talon.One APIs can be done using an API Key for the Third-party API or a Bearer token for the Management API..

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


What data can I load from Talon.One?

Here are some of the endpoints you can load from Talon.One:

ResourceEndpointMethodData selectorDescription
third_party_api_v2_infov2/infoGETGet information about the API
third_party_api_v2_customer_sessionsv2/customer_sessionsGETGet customer sessions
third_party_api_v2_customer_profilesv2/customer_profilesGETGet customer profiles
third_party_api_v2_eventsv2/eventsGETGet events
third_party_api_v2_couponsv2/couponsGETGet coupons

How do I authenticate with the Talon.One API?

For the Third-party API, authentication requires an API key in the Authorization HTTP header, prefixed with ApiKey-v1. For the Management API, a bearer token obtained from the createSession endpoint is used in the Authorization header, prefixed with Bearer.

1. Get your credentials

To obtain a Third-party API key: 1. Log in to the Campaign Manager. 2. Navigate to the section for creating API keys. 3. Click 'Create API Key'. 4. In 'Third-party integration', select 'Yes'. 5. Click 'Create API Key'. 6. Copy the generated key for use, as it cannot be viewed or copied after closing the drawer.

2. Add them to .dlt/secrets.toml

[sources.talon_one_source] api_key = "your_third_party_api_key_here" bearer_token = "your_management_bearer_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 Talon.One 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 talon_one_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline talon_one_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 customer_sessions and customer_profiles from the Talon.One 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 talon_one_source(api_key, bearer_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://integration.talon.one", "auth": { "type": "api_key, bearer", "api_key, token": api_key, bearer_token, }, }, "resources": [ {"name": "customer_sessions", "endpoint": {"path": "v2/customer_sessions"}}, {"name": "customer_profiles", "endpoint": {"path": "v2/customer_profiles"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="talon_one_pipeline", destination="duckdb", dataset_name="talon_one_data", ) load_info = pipeline.run(talon_one_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("talon_one_pipeline").dataset() sessions_df = data.customer_sessions.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM talon_one_data.customer_sessions LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("talon_one_pipeline").dataset() data.customer_sessions.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 Talon.One 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 Management API has a rate limit of 3 requests per second for each endpoint. Exceeding this limit may result in errors.

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 Talon.One?

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