Software AG Adabas Python API Docs | dltHub
Build a Software AG Adabas-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Software AG Adabas REST APIs expose administration and database access operations over HTTP or HTTPS. The REST API base URL is http(s)://<host>:<port> and JWT bearer token obtained from /login.
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 Software AG Adabas data in under 10 minutes.
What data can I load from Software AG Adabas?
Here are some of the endpoints you can load from Software AG Adabas:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| environments | adabas/rest/env | GET | Retrieve the list of environments. | |
| rest_log | adabas/rest/log | GET | Retrieve the REST server log. | |
| database_records | rest/db/{dbid}/{file} | GET | Read records from an Adabas database file. Query parameters documented include fields, start, limit, sorted_by, search, reference, compact, flatten, descriptor, and xmlnotation. | |
| map_records | rest/map/{name} | GET | Retrieve records through an Adabas Map definition. Query parameters include field selection, start, limit, sorting, and search options. | |
| adabas_configuration | adabas/config/ | GET | Get Adabas configuration. | |
| adabas_version | adabas/version | GET | Retrieve the Adabas/REST service version; exact path should be confirmed against the installed Swagger definition. | |
| database_information | adabas/db/{dbid} | GET | Display Adabas database information; exact path should be confirmed against the installed Swagger definition. | |
| file_list | adabas/db/{dbid}/files | GET | List files for a database; exact path should be confirmed against the installed Swagger definition. |
How do I authenticate with the Software AG Adabas API?
Authenticate by first calling the server's /login endpoint to obtain a signed JWT, then send it on protected requests in the HTTP header Authorization: Bearer . The JWT is time-limited; the documentation does not specify a fixed token string format beyond it being a JWT.
1. Get your credentials
Adabas REST Administration does not use a Software AG cloud dashboard or provisioned API-key credential. Obtain credentials from the administrator of the deployed Adabas RESTful server: (1) identify the server base URL, normally HTTP port 8190 or HTTPS port 8191; (2) ask the administrator for a configured Adabas REST username and password, or have an administrator create one with the installation's service script (service.sh add_user on Linux or service.bat add_user on Windows), which writes the account to configuration/realm.properties; (3) call POST /login (or use the server's Swagger UI login operation) with those credentials; (4) copy the returned JWT; and (5) send it on subsequent requests as Authorization: Bearer . JWT signing keys and expiration are server-side settings in AdabasRestAdministration/configuration/config.xml; they are not generated in a dashboard. For HTTPS, use the administrator-provided HTTPS URL and configured certificate/keystore.
2. Add them to .dlt/secrets.toml
[sources.software_ag_adabas_source] base_url = "https://your-adabas-rest-host:8191" username = "your_adabas_rest_username" password = "your_adabas_rest_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 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 Software AG Adabas 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 software_ag_adabas_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline software_ag_adabas_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset software_ag_adabas_data The duckdb destination used duckdb:/software_ag_adabas.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 /login and /logout from the Software AG Adabas 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 software_ag_adabas_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "http(s)://<host>:<port>", "auth": {"type": "bearer", "token": token}, }, "resources": [ {"name": "database_records", "endpoint": {"path": "rest/db/{dbid}/{file}"}}, {"name": "map_records", "endpoint": {"path": "rest/map/{name}"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="software_ag_adabas_pipeline", destination="duckdb", dataset_name="software_ag_adabas_data", ) load_info = pipeline.run(software_ag_adabas_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("software_ag_adabas_pipeline").dataset() sessions_df = data.database_records.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM software_ag_adabas_data.database_records LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("software_ag_adabas_pipeline").dataset() data.database_records.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 Software AG Adabas 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 Software AG Adabas?
Request dlt skills, commands, AGENT.md files, and AI-native context.