Industrial App Store Python API Docs | dltHub

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

Last updated:

The Industrial App Store API allows registered apps to execute data retrieval requests, manage transactions, and access user information from Intelligent Plant App Store data sources. The REST API base URL is https://api.intelligentplant.com/datacore/swagger and all requests require a Bearer token obtained via OAuth2 flow.

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 Industrial App Store data in under 10 minutes.


What data can I load from Industrial App Store?

Here are some of the endpoints you can load from Industrial App Store:

ResourceEndpointMethodData selectorDescription
data_sourcesapi/v1/data-sourcesGETRetrieve list of available data sources
tagsapi/v1/tag-searchGETSearch for tags on a specific data source
raw_valuesapi/v1/data/rawGETRequest raw values for a tag
processed_valuesapi/v1/data/processedGETRequest aggregated values for a tag
plot_valuesapi/v1/data/plotGETRequest a best-fit curve of tag values

How do I authenticate with the Industrial App Store API?

The API is secured via OAuth 2.0. Requests require an 'Authorization' header with a 'Bearer' token.

1. Get your credentials

  1. Register as a developer on the Intelligent Plant Industrial App Store website. 2. Log in to your Industrial App Store account. 3. Navigate to the Developer menu and select Applications. 4. Register a new application to generate your App ID (Client ID) and App Secret (Client Secret). 5. Configure authorized redirect URLs in the application settings as required by your specific authentication flow.

2. Add them to .dlt/secrets.toml

[sources.industrial_app_store_source] client_id = "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 venv && source .venv/bin/activate uv pip install "dlt[workspace]"

1. Install the dlt AI harness:

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:

dlthub 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 Industrial App Store 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 industrial_app_store_pipeline.py

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

Pipeline industrial_app_store_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset industrial_app_store_data The duckdb destination used duckdb:/industrial_app_store.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

dlt pipeline industrial_app_store_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 UserInfo and DataCore (Data Core API endpoints are typically accessed via api/v1/... routes relative to the data source URL) from the Industrial App Store 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 industrial_app_store_source(client_id=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.intelligentplant.com/datacore/swagger", "auth": {"type": "bearer", "token": client_id}, }, "resources": [ {"name": "tags", "endpoint": {"path": "api/v1/tag-search", "data_selector": "tags"}}, {"name": "data_sources", "endpoint": {"path": "api/v1/data-sources", "data_selector": "data_sources"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="industrial_app_store_pipeline", destination="duckdb", dataset_name="industrial_app_store_data", ) load_info = pipeline.run(industrial_app_store_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("industrial_app_store_pipeline").dataset() sessions_df = data.tags.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM industrial_app_store_data.tags LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("industrial_app_store_pipeline").dataset() data.tags.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 Industrial App Store 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.
dlthub ai toolkit data-exploration install dlthub ai toolkit dlthub-platform install

Was this page helpful?

Community Hub

Need more dlt context for Industrial App Store?

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

Available Pipelines