Load Omni Analytics data in Python using dltHub
Build a Omni Analytics-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Omni Analytics provides a BI platform and REST API for programmatically managing models, queries, users, connections, and scheduling. The REST API base URL is https://{instance}.omniapp.co/api and all requests require a Bearer token in the Authorization header.
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 Omni Analytics data in under 10 minutes.
What data can I load from Omni Analytics?
Here are some of the endpoints you can load from Omni Analytics:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| models | /v1/models | GET | records | Retrieve a list of models. |
| documents | /v1/documents | GET | records | Retrieve a list of documents. |
| api_tokens | /v1/api-tokens | GET | records | Retrieve a list of API tokens. |
| users | /v1/users | GET | records | Retrieve a list of users. |
| connections | /v1/connections | GET | records | Retrieve a list of database connections. |
How do I authenticate with the Omni Analytics API?
Requests are authenticated by including an API token in the 'Authorization' header using the Bearer scheme, formatted as 'Bearer YOUR_API_KEY'.
1. Get your credentials
Omni Analytics supports two primary methods of API authentication via bearer tokens:\n\n1. Organization API Keys (Recommended for admin/system use):\n - Navigate to Settings > API access > Organization keys.\n - Click Generate new key.\n - Provide a descriptive name and save the key securely, as it will only be displayed once.\n - Note: Requires Organization Admin permissions.\n\n2. Personal Access Tokens (PATs) (Recommended for user-specific access):\n - Ensure an Organization Admin has enabled Personal tokens in Settings > API access.\n - Navigate to your user profile icon > Manage account.\n - Select Generate token (requires Restricted Querier or higher permissions).
2. Add them to .dlt/secrets.toml
[sources.omni_analytics_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 Omni Analytics 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 omni_analytics_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline omni_analytics_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset omni_analytics_data The duckdb destination used duckdb:/omni_analytics.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 v1 and unstable (as in /api/v1/... and /api/unstable/...) from the Omni Analytics 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 omni_analytics_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://{instance}.omniapp.co/api", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "models", "endpoint": {"path": "v1/models", "data_selector": "records"}}, {"name": "documents", "endpoint": {"path": "v1/documents", "data_selector": "records"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="omni_analytics_pipeline", destination="duckdb", dataset_name="omni_analytics_data", ) load_info = pipeline.run(omni_analytics_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("omni_analytics_pipeline").dataset() sessions_df = data.models.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM omni_analytics_data.models LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("omni_analytics_pipeline").dataset() data.models.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 Omni Analytics 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 Omni Analytics?
Request dlt skills, commands, AGENT.md files, and AI-native context.