← Back to all docs

AspenTech API

AspenTech (Aspen Technology) is industrial asset optimization software for the process industries, spanning process engineering, manufacturing & supply chain, and asset performance management—including the Aspen InfoPlus.21 historian, aspenONE Process Explorer, and Aspen Mtell prescriptive maintenance. An unofficial API lets you programmatically pull process historian tags and time-series, assets and equipment health, Mtell anomaly/failure agents, work-order-driving alerts, and KPI/dashboard data—and push acknowledgements, asset metadata, and maintenance triggers back into AspenTech.

By Alex Klarfeld•May 30, 2026
AspenTech API

What is AspenTech?

AspenTech (Aspen Technology) is an industrial software company whose asset optimization products span process engineering, manufacturing & supply chain, asset performance management, digital grid management, subsurface science & engineering, and an industrial data fabric. Process manufacturers in energy, chemicals, and engineering & construction use AspenTech to simulate and design processes, run advanced process control, plan and schedule production, historize plant data, and predict and prevent equipment failures.

Core product areas include:

  • Process Engineering (Aspen HYSYS, Aspen Plus, Aspen PIMS simulation and design)
  • Manufacturing & Supply Chain (Aspen DMC3 Builder advanced process control, Aspen GDOT, Aspen Unified PIMS, Aspen Unified Scheduling)
  • Aspen InfoPlus.21 (IP.21) process historian for archiving plant time-series data
  • aspenONE Process Explorer (A1PE), a web and mobile environment for monitoring and analyzing IP.21 and other plant data
  • Asset Performance Management with Aspen Mtell prescriptive and predictive maintenance using AI/ML agents

Common data entities:

  • Historian Tags, Time-Series Records, Trends, Aggregates (IP.21)
  • Assets, Equipment, Areas, Process Units
  • Mtell Agents, Anomaly/Failure Signatures, Alerts, Cases
  • Process Explorer Dashboards, Plots, KPIs
  • APC Controllers, Limits, and Move Plans (DMC3)
  • Events, Acknowledgements, Notifications

The AspenTech Integration Challenge

Plants run AspenTech around the clock, but turning historian- and desktop-centric workflows into clean API-driven automation is non-trivial:

  • On-premise, OT-network deployments: IP.21 historians and Mtell servers typically live inside plant networks behind firewalls, not on a public cloud endpoint
  • Fragmented access methods: Data is reached through SQLplus, ODBC, OPC DA/HDA, and product-specific web APIs rather than one unified REST surface
  • Version and module variability: Endpoint and connector coverage differs across aspenONE versions, A1PE web server configuration, and which suites a site has licensed
  • Authentication complexity: Windows/domain authentication and per-server web API configuration complicate headless, automated access
  • High-cardinality time-series: Historian tags number in the tens or hundreds of thousands per site, so pulling and aligning data efficiently is a real engineering problem
  • Mtell agent context: Anomaly and failure agent outputs must be tied back to specific assets, equipment, and maintenance cases to be actionable downstream

How Supergood Creates AspenTech APIs

Supergood reverse-engineers AspenTech's authenticated web flows—including aspenONE Process Explorer—and its data access paths (SQLplus, ODBC, OPC, and product web APIs) to deliver a resilient, normalized API layer for your AspenTech deployment, whether it runs on-premise or in a hosted environment.

  • Handles Windows/domain and web-app authentication, including MFA, in a managed session
  • Maintains session continuity with automated refresh and change detection across plant networks
  • Normalizes historian tags, asset health, Mtell agent outputs, and Process Explorer KPIs into consistent JSON objects so you integrate once
  • Aligns with site-specific tag namespaces, asset hierarchies, and licensed modules to ensure accurate, scoped access

Use AspenTech with AI agents: AspenTech MCP Server →

Getting Started

  • Schedule Integration Assessment

Book a 30-minute session to confirm your AspenTech suites, deployment model, and authentication setup.

  • Supergood Generates and Validates Your API

We deliver a production-ready AspenTech adapter tailored to your historian, asset hierarchy, and licensed modules.

  • Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as AspenTech releases and site configuration evolve.

aspentech

API Endpoints

Authentication

POST/authenticate

Authenticate to an AspenTech deployment using Windows/domain or web-app credentials, including MFA, and obtain a session token for downstream calls.

Historian

GET/tags

List Aspen InfoPlus.21 historian tags with filters for area, process unit, and data type.

Historian

GET/timeseries

Retrieve raw and aggregated time-series values for one or more IP.21 tags over a specified time range.

Assets

GET/assets

Pull assets, equipment, and process-unit hierarchy along with current health status.

Asset Performance

GET/alerts

Retrieve Aspen Mtell agent alerts, anomaly and failure signatures, and case status for monitored equipment.

Events

POST/acknowledge_alert

Acknowledge an Mtell alert or push a maintenance trigger and disposition back into AspenTech.

Use Cases

Stream historian data into your data platform

- Pull IP.21 tags and time-series into a warehouse or lakehouse on a schedule - Align high-cardinality tags to asset and process-unit context - Feed downstream analytics, dashboards, and ML pipelines with consistent JSON

Drive predictive maintenance from Mtell agents

- Stream Aspen Mtell anomaly and failure agent alerts to your CMMS or work-order system - Tie each alert to the specific asset, equipment, and case for actionable routing - Acknowledge alerts and push maintenance triggers back into AspenTech

Centralize plant KPIs and asset health

- Pull aspenONE Process Explorer KPIs and asset health into a single operational view - Reconcile equipment status across IP.21, Mtell, and asset hierarchies - Surface degradation and downtime events to reliability and operations teams

Unify multi-site process data

- Normalize tags, assets, and alerts across multiple plants and aspenONE versions - Integrate once against a stable API rather than per-site SQLplus, ODBC, and OPC connectors - Keep site-specific namespaces and hierarchies intact while presenting consistent objects

Technical Specifications

Authentication

Windows/domain and web-app credentials, including MFA, handled in a managed session

Connectivity

Authenticated web flows plus IP.21 access paths (SQLplus, ODBC, OPC DA/HDA) and product web APIs where exposed

Response format

Normalized JSON across historian tags, time-series, assets, Mtell alerts, and Process Explorer KPIs

Rate limits

Adaptive throttling tuned to your historian and plant network to avoid overloading on-premise servers

Session management

Automatic session refresh, MFA replay handling, and credential rotation

Data freshness

Near real-time tag and alert pulls with optional scheduled batch syncs for historical ranges

Security

Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging

Webhooks

Event-style callbacks for Mtell alerts, anomaly detections, and asset status changes

Latency

Sub-second reads on cached tags and assets; multi-second pulls for large time-series ranges

Throughput

Horizontally scaled workers sized to high-cardinality tag volumes across multiple sites

Reliability

Retry, backoff, and idempotency keys for alert acknowledgements and write-backs

Adaptation

Continuous monitoring of aspenONE releases, A1PE configuration, and site-specific tag and asset drift

Frequently asked questions

Yes. Most AspenTech historians and Mtell servers run inside plant networks behind firewalls. Supergood operates against those authenticated surfaces with network configuration tuned to your environment, so you get a stable API without exposing OT systems publicly.

The API surfaces data from Aspen InfoPlus.21, aspenONE Process Explorer, and Aspen Mtell, with asset and process-unit context. Coverage of specific modules depends on what your site has licensed and deployed; we profile your environment during the assessment.

AspenTech exposes data through SQLplus, ODBC, OPC DA/HDA, and product web APIs rather than one unified REST endpoint. Supergood reverse-engineers and normalizes these paths into a single consistent API so you integrate once.

Yes. Mtell agent alerts, anomaly and failure signatures, and case status are exposed through the normalized API and tied to specific assets, so you can route them into a CMMS, acknowledge them, and push maintenance triggers back.

Supergood pulls and aligns high-cardinality tags with adaptive throttling and horizontally scaled workers, mapping them to asset and process-unit context so downstream systems receive consistent, query-ready objects.

Related APIs in Manufacturing & Distribution ERP

Manufacturing & Distribution ERP

AVEVA API

AVEVA is an industrial software company whose platform spans engineering, operations, and data management for energy, manufacturing, and infrastructure, anchored by the AVEVA PI System and the CONNECT industrial intelligence platform. An unofficial API lets you programmatically pull time-series tags, assets, elements, attributes, events, streams, and alarm data—and push values, configuration, and stream updates back into PI System and CONNECT data services across your industrial estate.

Manufacturing & Distribution ERP

Accolent ERP API

Accolent ERP, from ADS Solutions, is a cloud-based, browser-delivered ERP suite for wholesale distributors and light manufacturers, hosted on AWS and spanning order management, inventory, warehouse management, eCommerce, purchasing, and full GAAP accounting. An unofficial API lets you programmatically pull customers, orders, invoices, inventory, purchase orders, and general-ledger data—and push updates like new orders, invoices, and inventory adjustments back into Accolent.

Manufacturing & Distribution ERP

Aptean Food API

Aptean Food & Beverage ERP is an industry-specific cloud ERP built on Microsoft Dynamics 365 Business Central, delivering lot traceability, recipe and quality management, catch weight, and supply chain operations for food and beverage manufacturers and distributors. An unofficial API lets you programmatically pull items, lots, recipes, inventory, sales and purchase orders, and customer/vendor records—and push updates like new orders, production batches, and quality results back into Aptean Food.

Manufacturing & Distribution ERP

BatchMaster API

BatchMaster is an industry-specific ERP and manufacturing platform built for formula-based, process manufacturers in food and beverage, chemicals, nutraceuticals, pharmaceuticals, and personal care. An unofficial API lets you programmatically pull formulas, batches, lots, inventory, sales and purchase orders, and quality results—and push updates like new orders, production batches, and QC results back into BatchMaster.

Manufacturing & Distribution ERP

BlueLink ERP API

Blue Link ERP is a cloud-based accounting and inventory management platform for small-to-medium wholesalers and distributors in North America and the Caribbean, spanning financials, inventory, warehouse, order entry, CRM, and specialized pharmaceutical compliance. An unofficial API lets you programmatically pull inventory, sales orders, purchase orders, invoices, customers, and vendors—and push updates like new orders, shipments, and payments back into Blue Link.

Manufacturing & Distribution ERP

Cetec ERP API

Cetec ERP is a cloud-based, all-in-one manufacturing ERP that unifies quoting, MRP, inventory and traceability, shop floor control, quality/compliance, purchasing, and accounting for electronics, machine shop, medical device, and aerospace manufacturers. Its JSON-based REST API lets you programmatically pull orders, quotes, parts, inventory, invoices, and customer records—and push new orders, quotes, BOMs, and updates back into Cetec ERP.

Ready to get a real API?