Temenos Transact Python API Docs | dltHub

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

Last updated:

Temenos Transact provides RESTful APIs for core banking operations including account management, customer data, transactions, and payment processing. The REST API base URL is https://api.temenos.com/transact/v1 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 add "dlt[hub]" and start loading Temenos Transact data in under 10 minutes.


What data can I load from Temenos Transact?

Here are some of the endpoints you can load from Temenos Transact:

ResourceEndpointMethodData selectorDescription
transactions/holdings/accounts/{accountId}/transactionsGETbodyList account transactions
currencies/reference/currenciesGETbodyList available currencies
countries/reference/countriesGETbodyList available countries
products/product/productsGETbodyList product catalog
customers/party/customersGETbodyList customers

How do I authenticate with the Temenos Transact API?

Temenos Transact APIs use OAuth 2.0 Bearer token authentication, which requires a JWT provided in the Authorization header as 'Bearer '.

1. Get your credentials

To obtain credentials for the Temenos Transact REST API, you must use the Temenos Developer Portal. First, navigate to the portal and click the Log In button in the top-right corner. You can authenticate using existing credentials for the Temenos Customer Support Portal (TCSP), Partner Support Portal (TPSP), or by registering for the Temenos Community if you are not an existing customer. Once logged in, click your username in the top-right corner, select 'API Key' from the drop-down menu, and click 'Request an API Key'. For customers, partners, and employees, the key is typically generated automatically; community users may experience a pending approval process. The resulting API key is used for sandbox testing.

2. Add them to .dlt/secrets.toml

[sources.temenos_transact_source] temenos_api_key = "your_api_key_here" temenos_bearer_token = "your_jwt_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 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 Temenos Transact 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 temenos_transact_pipeline.py

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

Pipeline temenos_transact_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset temenos_transact_data The duckdb destination used duckdb:/temenos_transact.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 holdings/accounts and order/fundTransfers from the Temenos Transact 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 temenos_transact_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.temenos.com/transact/v1", "auth": {"type": "bearer", "token": access_token}, }, "resources": [ {"name": "transactions", "endpoint": {"path": "holdings/accounts/{accountId}/transactions", "data_selector": "body"}}, {"name": "currencies", "endpoint": {"path": "reference/currencies", "data_selector": "body"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="temenos_transact_pipeline", destination="duckdb", dataset_name="temenos_transact_data", ) load_info = pipeline.run(temenos_transact_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("temenos_transact_pipeline").dataset() sessions_df = data.transactions.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM temenos_transact_data.transactions LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("temenos_transact_pipeline").dataset() data.transactions.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 Temenos Transact 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 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 Temenos Transact?

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