HCL Domino REST API Python API Docs | dltHub
Build a HCL Domino REST API-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
HCL Domino REST API provides access to Domino documents, views, folders, and agents using OpenAPI 3.0.2 specifications. The REST API base URL is http://localhost:8880/api/v1 and all requests require an Authorization header with a Bearer token.
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 HCL Domino REST API data in under 10 minutes.
What data can I load from HCL Domino REST API?
Here are some of the endpoints you can load from HCL Domino REST API:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| lists | /api/v1/lists/{name} | GET | Retrieves data from a specific Domino view or folder. | |
| query | /api/v1/query | POST | Executes a query against a data source using specific criteria. | |
| auth | /api/v1/auth | POST | Exchanges credentials for a JWT access token. | |
| documents | /api/v1/documents/{unid} | GET | Retrieves a specific document by its UNID. | |
| attachments | /api/v1/attachments/{unid}/{name} | GET | Downloads a document attachment by UNID and filename. |
How do I authenticate with the HCL Domino REST API API?
Authentication is performed by sending a POST request to the /api/v1/auth endpoint with user credentials. Subsequent requests require the JWT returned from the authentication endpoint to be included in the Authorization header as a Bearer token.
1. Get your credentials
- Log in to the Domino REST API Admin UI at http:///admin/ui. 2. Navigate to the 'Application Management' (or 'Applications') page. 3. Click 'Add Application' and provide the required details (Name, Description, Redirect URIs, Scopes). 4. After saving, locate the new application in the list. 5. Click 'Click to Generate Secret'. 6. Note the generated App ID and App Secret immediately, as the secret cannot be retrieved once you navigate away from the page. These credentials are used for OAuth-based authentication.
2. Add them to .dlt/secrets.toml
[sources.hcl_domino_rest_api_source] api_key = "REPLACE_ME"
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 HCL Domino REST API 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 hcl_domino_rest_api_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline hcl_domino_rest_api_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset hcl_domino_rest_api_data The duckdb destination used duckdb:/hcl_domino_rest_api.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 /api/v1/auth and /api/v1/document from the HCL Domino REST API 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 hcl_domino_rest_api_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "http://localhost:8880/api/v1", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "lists", "endpoint": {"path": "api/v1/lists/{name}"}}, {"name": "query", "endpoint": {"path": "api/v1/query"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="hcl_domino_rest_api_pipeline", destination="duckdb", dataset_name="hcl_domino_rest_api_data", ) load_info = pipeline.run(hcl_domino_rest_api_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("hcl_domino_rest_api_pipeline").dataset() sessions_df = data.lists.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM hcl_domino_rest_api_data.lists LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("hcl_domino_rest_api_pipeline").dataset() data.lists.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 HCL Domino REST API 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 HCL Domino REST API?
Request dlt skills, commands, AGENT.md files, and AI-native context.