Zowe Python API Docs | dltHub
Build a Zowe-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Zowe API reference details REST APIs for the Zowe API Gateway service and ZLUX Plug-in. Versioning is managed by specifying major versions. Node.js must be installed separately on z/OS for Zowe components. The REST API base URL is https://{gatewayHost}:{port}/api/v{majorVersion} and JWT Bearer token authentication.
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 Zowe data in under 10 minutes.
What data can I load from Zowe?
Here are some of the endpoints you can load from Zowe:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| api_services | gateway/api/v1/services | GET | apiml.apiInfo | Returns information about all discovered services; 'apiInfo' array holds API definitions. |
| auth_keys_public | gateway/api/v1/auth/keys/public | GET | keys | Returns public JWK set for verifying JWT signatures. |
| auth_check | gateway/api/v1/check | GET | Validates a JWT token and returns a boolean status. | |
| auth_login | gateway/api/v1/login | POST | Exchanges user credentials for a JWT access token. | |
| api_service | gateway/api/v1/services/{serviceId} | GET | apiml.instances | Returns details for a specific service, including instance information. |
How do I authenticate with the Zowe API?
Obtain a JWT by POSTing credentials to /gateway/api/v1/login and include it in subsequent requests as Authorization: Bearer .
1. Get your credentials
- Get a valid Zowe user ID and password from your z/OS administrator.
- (If using OIDC) Register a client with your identity provider (e.g., Keycloak, Okta) and obtain client_id/client_secret.
- POST the credentials (or OIDC code) to /gateway/api/v1/login to receive a JWT access token.
- Save the token and include it as a Bearer token in the Authorization header for all API calls.
2. Add them to .dlt/secrets.toml
[sources.zowe_source] token = "your_zowe_jwt_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 Zowe 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 zowe_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline zowe_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset zowe_data The duckdb destination used duckdb:/zowe.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline zowe_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 api_services and auth_keys_public from the Zowe 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 zowe_source(auth_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://{gatewayHost}:{port}/api/v{majorVersion}", "auth": { "type": "bearer", "token": auth_token, }, }, "resources": [ {"name": "api_services", "endpoint": {"path": "gateway/api/v1/services", "data_selector": "apiml.apiInfo"}}, {"name": "auth_keys_public", "endpoint": {"path": "gateway/api/v1/auth/keys/public", "data_selector": "keys"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="zowe_pipeline", destination="duckdb", dataset_name="zowe_data", ) load_info = pipeline.run(zowe_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("zowe_pipeline").dataset() sessions_df = data.api_services.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM zowe_data.api_services LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("zowe_pipeline").dataset() data.api_services.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 Zowe 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 Zowe?
Request dlt skills, commands, AGENT.md files, and AI-native context.