Talon.One Python API Docs | dltHub
Build a Talon.One-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Talon.One provides a suite of APIs including an Integration API, a Management API, and a Third-party API for managing campaigns, loyalty programs, and customer data across distinct deployment domains. The REST API base URL is https://yourbaseurl.talon.one and All requests require an Authorization header using a specific credential prefix..
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 add "dlt[hub]" 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:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| applications | /v1/applications | GET | applications | List all applications |
| application_events | /v1/applications/{applicationId}/events | GET | data | List application events |
| campaigns | /v1/campaigns | GET | data | List campaigns |
| loyalty_programs | /v1/loyalty_programs | GET | data | List loyalty programs |
| customer_profiles | /v1/customer_profiles | GET | data | List customer profiles |
How do I authenticate with the Talon.One API?
Talon.One APIs require an Authorization header. Depending on the API surface, you must use one of three prefixes followed by a space and the credential: 'ApiKey-v1' for the Integration API, 'ManagementKey-v1' for the Management API, or 'Bearer' for session-based authentication.
1. Get your credentials
To obtain your API credentials for the Talon.One Integration API: 1. Log in to your Talon.One account. 2. Navigate to your specific Application. 3. Go to Settings > Integration API Keys. 4. Click Create API Key. 5. In the drawer, select the Key type (e.g., Production). 6. Enter a unique Key name. 7. Click Create API Key. 8. Copy the generated key immediately, as it cannot be viewed again after closing the drawer.
2. Add them to .dlt/secrets.toml
[sources.talon_one_source] talon_one_api_key = "your_generated_api_key_here" talon_one_base_url = "https://your-company.talon.one"
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 init uv add "dlt[hub]"
1. Install the dlt AI harness:
uv run dlthub 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:
uv run dlthub ai toolkit install rest-api-pipeline
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:
uv run 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:
uv run dlthub 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=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://yourbaseurl.talon.one", "auth": {"type": "api_key", "api_key": api_key, "name": "Authorization", "location": "header"}, }, "resources": [ {"name": "application_events", "endpoint": {"path": "v1/applications/{applicationId}/events", "data_selector": "data"}}, {"name": "campaigns", "endpoint": {"path": "v1/campaigns", "data_selector": "data"}} ], } 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.application_events.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM talon_one_data.application_events LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("talon_one_pipeline").dataset() data.application_events.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:
| Destination | Example 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 harness:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-platform— Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform
Was this page helpful?
Community Hub
Need more dlt context for Talon.One?
Request dlt skills, commands, AGENT.md files, and AI-native context.