Imply Polaris Python API Docs | dltHub

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

Last updated:

The Imply Polaris API provides access to manage resources like tables, files, and ingestion jobs. Authentication is done via API keys or OAuth. The base URL format is https://ORGANIZATION_NAME.REGION.CLOUD_PROVIDER.api.imply.io/v1/projects/PROJECT_ID. The REST API base URL is https://ORGANIZATION_NAME.api.imply.io (global) or https://ORGANIZATION_NAME.REGION.CLOUD_PROVIDER.api.imply.io (regional). For project‑scoped regional calls include /v1/projects/{projectId} in the path. and Supports API key (recommended) and OAuth; many endpoints accept Bearer or API key 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 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
projects/v1/projectsGETList all projects (global or regional base URL).
api_keys/v1/apikeysGETitemsList all API keys (response uses 'items').
api_key/v1/apikeys/{id}GETGet API key details for given id.
apikey_info/v1/apikeyinfoGETGet details for the API key used to authenticate the request.
audit_events/v1/audit/eventsGETvaluesList audit events (response uses 'values').
customizations_logos/v1/customizations/logosGETGet organization logos (returns object with 'full' and 'favicon' fields).
favorites/v1/projects/{projectId}/favoritesGETList favorites for the authenticated user in a project.
events_push/v1/projects/{projectId}/events/{connectionName}POSTPush (POST) events to a push streaming connection (used for ingestion).

How do I authenticate with the Imply Polaris API?

Polaris supports API key and OAuth authentication. API requests use either an API key (sent as API key auth or in the Authorization header) or bearer OAuth tokens.

1. Get your credentials

In the Polaris UI: go to API Keys (Create API key), give it a name and permissions (e.g. ManageConnections, ManageTables, ManageIngestionJobs for streaming). The API key value is returned when created; copy it and store securely.

2. Add them to .dlt/secrets.toml

[sources.imply_polaris_source] api_key = "your_polaris_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 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 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:

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:

dlt pipeline imply_polaris_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_keys and events_push 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.api.imply.io (global) or https://ORGANIZATION_NAME.REGION.CLOUD_PROVIDER.api.imply.io (regional). For project‑scoped regional calls include /v1/projects/{projectId} in the path.", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "api_keys", "endpoint": {"path": "v1/apikeys", "data_selector": "items"}}, {"name": "events", "endpoint": {"path": "v1/projects/{projectId}/events/{connectionName}"}} ], } 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 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 Imply Polaris?

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