Inductive Automation Forum Python API Docs | dltHub
Build a Inductive Automation Forum-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
The REST API in Ignition uses JSON for all arguments and returns, and it's served through the WebDev module. It supports authentication via Active Directory. For encryption, Kerberos is used for secure communication. The REST API base URL is https://<gateway-host>:8088/data/api/v1 and All requests require an X-Ignition-API-Token header for 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 Inductive Automation Forum data in under 10 minutes.
What data can I load from Inductive Automation Forum?
Here are some of the endpoints you can load from Inductive Automation Forum:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
gateway_info | /gateway-info | GET | Returns gateway configuration details such as version, edition, and hostname. | |
resources_list | /resources/list/{moduleId}/{typeId} | GET | Lists configuration resources for a given module and type. | |
latest_build | /latestBuild | GET | Provides an array of the latest module IDs and their versions. | |
system_gwinfo | /system/gwinfo | GET | Returns system‑level gateway information; can be accessed with Kerberos authentication. | |
openapi | /openapi | GET | Returns the OpenAPI specification JSON for the API. |
How do I authenticate with the Inductive Automation Forum API?
Obtain an API token from the Gateway’s Security > API Keys page and include it in every request using the X-Ignition-API-Token header.
1. Get your credentials
- Log into the Ignition Gateway web UI.
- Navigate to Platform → Security → API Keys.
- Click Create New Key, give it a name, and save.
- Copy the generated token value.
- Optionally, use the
getAPIKey()function in a script to retrieve the key for a specific user. - Store the token securely for use in API calls.
2. Add them to .dlt/secrets.toml
[sources.inductive_automation_forum_source] api_key = "YOUR_IGNITION_API_TOKEN"
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 Inductive Automation Forum 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 inductive_automation_forum_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline inductive_automation_forum_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset inductive_automation_forum_data The duckdb destination used duckdb:/inductive_automation_forum.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline inductive_automation_forum_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 gateway_info and resources_list from the Inductive Automation Forum 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 inductive_automation_forum_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://<gateway-host>:8088/data/api/v1", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "gateway_info", "endpoint": {"path": "gateway-info"}}, {"name": "resources_list", "endpoint": {"path": "resources/list/{moduleId}/{typeId}"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="inductive_automation_forum_pipeline", destination="duckdb", dataset_name="inductive_automation_forum_data", ) load_info = pipeline.run(inductive_automation_forum_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("inductive_automation_forum_pipeline").dataset() sessions_df = data.gateway_info.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM inductive_automation_forum_data.gateway_info LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("inductive_automation_forum_pipeline").dataset() data.gateway_info.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 Inductive Automation Forum data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example 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 Inductive Automation Forum?
Request dlt skills, commands, AGENT.md files, and AI-native context.