Read tag/resource data from a water utility's Ignition SCADA gateway via its REST/OpenAPI Gateway API
domain: inductiveautomation.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm the target Ignition Gateway version (8.3+) since the dynamically generated OpenAPI spec is documented at docs.inductiveautomation.com/docs/8.3/platform/gateway/openapi
Fetch the gateway's live OpenAPI specification from its /openapi endpoint to enumerate the specific routes exposed by that gateway's installed modules
Call the relevant documented Gateway REST route over HTTPS, depending on installed modules (e.g., Perspective, Tag Historian)
Authenticate per the gateway's configured security/identity-provider integration
Parse returned resource/tag data according to the OpenAPI schema returned by that specific gateway instance
Known gotchas
The set of exposed routes is dynamic per-gateway and depends on installed modules, so there is no single fixed global API surface to hard-code against
Inductive Automation's documentation warns that Gateway API misuse can cause loss of configuration/tags/projects or degrade Gateway performance; this is an operational control-system interface, not a passive reporting API
HTTPS/SSL is mandatory for all endpoints; the API cannot be called over plain HTTP
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?