Imply Polaris Python API Docs | dltHub

Build a Imply Polaris-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

Imply Polaris is a managed service for Apache Druid that allows users to ingest, query, and visualize data via a REST API. The REST API base URL is https://ORGANIZATION_NAME.REGION.CLOUD_PROVIDER.api.imply.io and all requests require an Authorization header using either Basic (for API keys) or Bearer (for OAuth tokens) authentication schemes.

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 Imply Polaris data in under 10 minutes.


What data can I load from Imply Polaris?

Here are some of the endpoints you can load from Imply Polaris:

ResourceEndpointMethodData selectorDescription
api_keys/v1/apikeysGETitemsList all API keys
api_key/v1/apikeys/{id}GETGet API key details for given id
apikey_info/v1/apikeyinfoGETGet details for the API key used to authenticate
audit_events/v1/audit/eventsGETvaluesList audit events
favorites/v1/favoritesGETList favorites for authenticated user

How do I authenticate with the Imply Polaris API?

Polaris supports Basic authentication using API keys (header: Authorization: Basic <API_KEY>) and Bearer token authentication (header: Authorization: Bearer <ACCESS_TOKEN>).

1. Get your credentials

To obtain an API key for Imply Polaris, navigate to the Polaris console. Go to the API keys page within the UI to create a new key. Ensure the key is assigned either the 'AdministerApiKeys' or 'ManageApiKeys' permission. Once created, store the key securely, as it serves as the authentication credential for your API requests. For detailed management, refer to the documentation on creating and managing API keys.

2. Add them to .dlt/secrets.toml

[sources.imply_polaris_source] imply_polaris_api_key = "your_api_key_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 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 Imply Polaris 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 imply_polaris_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline imply_polaris_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset imply_polaris_data The duckdb destination used duckdb:/imply_polaris.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/apikeys and /v1/apikeys/ID from the Imply Polaris 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 imply_polaris_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://ORGANIZATION_NAME.REGION.CLOUD_PROVIDER.api.imply.io", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "api_keys", "endpoint": {"path": "v1/apikeys", "data_selector": "items"}}, {"name": "audit_events", "endpoint": {"path": "v1/audit/events", "data_selector": "values"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="imply_polaris_pipeline", destination="duckdb", dataset_name="imply_polaris_data", ) load_info = pipeline.run(imply_polaris_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("imply_polaris_pipeline").dataset() sessions_df = data.api_keys.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM imply_polaris_data.api_keys LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("imply_polaris_pipeline").dataset() data.api_keys.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 Imply Polaris data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample 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 Imply Polaris?

Request dlt skills, commands, AGENT.md files, and AI-native context.

Available Pipelines