Load Industrial App Store data to Microsoft Fabric

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. Everything needed to build a working Industrial App Store → Microsoft Fabric pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.

---

Build your Industrial App Store to Microsoft Fabric pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Industrial App Store API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.

---

Industrial App Store API at a glance

These values come from the Industrial App Store API reference — the authoritative source if anything here looks out of date.

---

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

Copy
[sources.industrial_app_store_source]
client_id = "REPLACE_ME"

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.

---

What Industrial App Store data can I load into Microsoft Fabric?

These are the Industrial App Store endpoints dlt can load into Microsoft Fabric:

---

How do I load only new Industrial App Store records?

The Industrial App Store API reference does not document a timestamp or sequence field for these endpoints, so there is nothing to advertise here as verified. Pick a field from the endpoints table above that increases with every write, then set it as the cursor_path.

Copy
{"name": "tags", "endpoint": {
    "path": "api/v1/tag-search",
    # Replace with a field that increases on every write.
    "incremental": {"cursor_path": "REPLACE_ME", "initial_value": "2024-01-01T00:00:00Z"},
}}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.

---

What does the generated Industrial App Store pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading 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 Microsoft Fabric:

Copy
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 load_industrial_app_store_to_fabric() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="industrial_app_store_pipeline",
        destination="fabric",
        dataset_name="industrial_app_store_data",
    )
    load_info = pipeline.run(industrial_app_store_source())
    print(load_info)


if __name__ == "__main__":
    load_industrial_app_store_to_fabric()

Run it with python industrial_app_store_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.

---

How do I query Industrial App Store data in Microsoft Fabric?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("industrial_app_store_pipeline").dataset()
df = data.tags.df()
print(df.head())

SQL:

Copy
SELECT * FROM industrial_app_store_data.tags LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the Industrial App Store to Microsoft Fabric pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

• Deploy & schedule — run the pipeline as a managed job with automatic retries.
• Monitor — observable job queues, alerting, and load metrics for every run.
• Transform — promote raw Industrial App Store loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load Industrial App Store data to?

dlt loads into any of these — only the destination argument changes:

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.

---

Next steps

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack