InfinityQS Python API Docs | dltHub

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

Last updated:

InfinityQS Enact is a cloud-based quality management platform that provides a REST API for accessing quality data and KPIs. The REST API base URL is https://api.infinityqs.com/enact/ and all requests require OAuth 2.0 authentication with a subscription key 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 InfinityQS data in under 10 minutes.


What data can I load from InfinityQS?

Here are some of the endpoints you can load from InfinityQS:

ResourceEndpointMethodData selectorDescription
kpi_data/enact/{kpi}/{id}.jsonGETRetrieves published KPI data for a specific aggregation event.
acknowledgement/enact/{kpi}/{id}/acknowledgePOSTConfirms retrieval of KPI data, allowing removal from Enact.
events/enact/eventsGETRetrieves published event data.
event_acknowledgement/enact/events/{id}/acknowledgePOSTConfirms retrieval of event data.
lot_data/enact/lot-dataGETRetrieves published lot data.

How do I authenticate with the InfinityQS API?

The Enact API uses OAuth 2.0 and OpenID Connect for authentication, requiring a subscription key, client ID, client secret, and a refresh token to obtain access tokens. Requests typically require the subscription key to be passed in the headers.

1. Get your credentials

InfinityQS Enact does not appear to use a self-service API-key dashboard. For the documented publishing API: (1) sign in to Enact with an authorized account; (2) open the Publishing configuration page for KPI/aggregate or event publishing; (3) enable the relevant publishing option; (4) enter your HTTPS receiver URL; (5) create and enter an Access Key of up to 128 characters using the documented allowed characters; (6) in the Subscription Key field, select Copy and provide the copied key to the application administrator. The client application must send that Subscription Key in the OCP-APIM-Subscription-Key header on API GET and acknowledgement POST requests. If the Publishing page or key is unavailable, contact the Enact system administrator or InfinityQS support; the public documentation does not describe a general developer-dashboard API-key workflow.

2. Add them to .dlt/secrets.toml

[sources.infinityqs_source] api_key = "your_enact_subscription_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 InfinityQS 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 infinityqs_pipeline.py

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

Pipeline infinityqs_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset infinityqs_data The duckdb destination used duckdb:/infinityqs.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 KPI data retrieval and acknowledgement from the InfinityQS 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 infinityqs_source(subscription_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.infinityqs.com/enact/", "auth": {"type": "bearer", "token": subscription_key}, }, "resources": [ {"name": "kpi_data", "endpoint": {"path": "enact/{kpi}/{id}.json", "data_selector": "data"}}, {"name": "acknowledgement", "endpoint": {"path": "enact/{kpi}/{id}/acknowledge", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="infinityqs_pipeline", destination="duckdb", dataset_name="infinityqs_data", ) load_info = pipeline.run(infinityqs_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("infinityqs_pipeline").dataset() sessions_df = data.kpi_data.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM infinityqs_data.kpi_data LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("infinityqs_pipeline").dataset() data.kpi_data.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 InfinityQS 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 InfinityQS?

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