Ephesoft Transact Python API Docs | dltHub

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

Last updated:

Ephesoft Transact REST API documentation is available for testing and reference. The API endpoints allow integration and automation of document processing tasks. The latest version includes new features and improvements. The REST API base URL is https://{host}:{port}/dcma/rest and all requests require HTTP Basic authentication (username and password).

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 Ephesoft Transact data in under 10 minutes.


What data can I load from Ephesoft Transact?

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

ResourceEndpointMethodData selectorDescription
batch_classesrest/v3/batchClassesGETbatchClassesReturns list/details of batch classes (v3)
batch_class_document_typesrest/v3/batchClasses/{batchClassName}/documentTypesGETdocumentTypesGet document types for a batch class (v3)
batch_instancesrest/v3/batchInstancesGETbatchInstancesReturns list of batch instances (v3)
batch_instancerest/v3/batchInstances/{batchInstanceId}GETGet a single batch instance (v3)
ovr_ocr_classify_extractrest/v2/ocrClassifyExtractPOSTOCR/classify/extract endpoint (v2) – workflow optimized
ocr_classify_extract_base64rest/v2/ocrClassifyExtractBase64POSTBase64 file input, returns minimized JSON response

How do I authenticate with the Ephesoft Transact API?

Transact web services support only HTTP Basic authentication (base64‑encoded username:password) supplied in the Authorization header.

1. Get your credentials

  1. Log into your Ephesoft Transact server as an administrator. 2) Create or identify a local Transact user (Users & Roles) with API/webservices privileges. 3) Use that username and password in your client; Transact uses HTTP Basic auth (no API key or token issuance step).

2. Add them to .dlt/secrets.toml

[sources.ephesoft_transact_source] user = "your_transact_username" password = "your_transact_password"

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 Ephesoft 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:

python ephesoft_transact_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline ephesoft_transact_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 batch_classes and batch_instances from the Ephesoft 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 ephesoft_transact_source(password=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://{host}:{port}/dcma/rest", "auth": { "type": "http_basic", "password": password, }, }, "resources": [ {"name": "batch_classes", "endpoint": {"path": "rest/v3/batchClasses", "data_selector": "batchClasses"}}, {"name": "batch_instances", "endpoint": {"path": "rest/v3/batchInstances", "data_selector": "batchInstances"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="ephesoft_transact_pipeline", destination="duckdb", dataset_name="ephesoft_transact_data", ) load_info = pipeline.run(ephesoft_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("ephesoft_transact_pipeline").dataset() sessions_df = data.batch_instances.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM ephesoft_transact_data.batch_instances LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("ephesoft_transact_pipeline").dataset() data.batch_instances.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 Ephesoft 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 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 Ephesoft Transact?

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