Open Liberty Python API Docs | dltHub
Build a Open Liberty-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Open Liberty supports REST API documentation via OpenAPI 3.1 and MicroProfile OpenAPI for JAX-RS applications. It provides standardized mechanisms for generating structured API documentation. Open Liberty APIs allow building, deploying, and managing Java applications. The REST API base URL is http://localhost:9080 and no built-in API auth for the /openapi endpoint (server-local); application APIs use whatever auth the app defines (none by default).
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 Open Liberty data in under 10 minutes.
What data can I load from Open Liberty?
Here are some of the endpoints you can load from Open Liberty:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| openapi_document | /openapi | GET | (OpenAPI JSON/YAML object) | Return generated OpenAPI document for deployed application(s). |
| openapi_ui | /openapi/ui | GET | (HTML) | Swagger UI for interactive API exploration. |
| inventory_systems | /inventory/systems | GET | systems | Example app: returns InventoryList object; 'systems' key contains array of records. |
| inventory_system | /inventory/systems/{hostname} | GET | (object) | Example app: returns properties object for hostname; 200 returns JSON object, 404 returns JSON {"error":...}. |
| inventory_properties | /inventory/properties | GET | (object additionalProperties) | Example app: returns JVM system properties as an object of key->string. |
How do I authenticate with the Open Liberty API?
Open Liberty exposes the generated OpenAPI document at /openapi and the UI at /openapi/ui on the server (default HTTP port 9080). The OpenAPI endpoint itself does not require a token by default; authentication for individual application endpoints is application-specific and must be configured in the application or server (e.g., basic, JWT, etc.).
1. Get your credentials
Open Liberty's OpenAPI document is served from the server; there are no provider-managed API credentials. To secure application endpoints, configure authentication in the application (JAX-RS security annotations, MicroProfile JWT, or server security-constraints) and obtain credentials from the application/service owner or identity provider as configured.
2. Add them to .dlt/secrets.toml
[sources.open_liberty_source] # Open Liberty OpenAPI has no global API token by default # If your app requires auth, add the matching secret here, e.g. for bearer tokens: # token = "your_jwt_or_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 Open Liberty 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 open_liberty_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline open_liberty_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset open_liberty_data The duckdb destination used duckdb:/open_liberty.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline open_liberty_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 inventory/systems and inventory/properties from the Open Liberty 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 open_liberty_source(no_auth=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "http://localhost:9080", "auth": { "type": "none", "": no_auth, }, }, "resources": [ {"name": "inventory_systems", "endpoint": {"path": "inventory/systems", "data_selector": "systems"}}, {"name": "inventory_properties", "endpoint": {"path": "inventory/properties"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="open_liberty_pipeline", destination="duckdb", dataset_name="open_liberty_data", ) load_info = pipeline.run(open_liberty_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("open_liberty_pipeline").dataset() sessions_df = data.inventory_systems.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM open_liberty_data.inventory_systems LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("open_liberty_pipeline").dataset() data.inventory_systems.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 Open Liberty 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 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 Open Liberty?
Request dlt skills, commands, AGENT.md files, and AI-native context.