← Back to all docs

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.

By Alex Klarfeld•May 30, 2026
AVEVA API

What is AVEVA?

AVEVA is a global industrial software company that provides AI-powered solutions to help organizations optimize engineering, operations, and performance across energy, manufacturing, and infrastructure. Industrial operators use AVEVA to deliver capital projects, run plants and facilities, historize and analyze process data, and share data securely across an extended ecosystem—anchored by the AVEVA PI System and the open CONNECT industrial intelligence platform, with thousands of certified developers and ecosystem partners building on top of it.

Core solution areas include:

  • Engineering (capital project delivery to operations, on-time and on-budget)
  • Operations (operational efficiency, collaboration, and value-leak elimination)
  • Data Management (data integration and business optimization across the supply chain)
  • AVEVA PI System (operational data historian: tags, Asset Framework elements, attributes, events, streams)
  • CONNECT (industrial intelligence platform for secure data sharing and ecosystem integration)

Common data entities:

  • PI Points/Tags, Streams, time-series values, and snapshots
  • Asset Framework Elements, Attributes, Templates, and hierarchies
  • Events, Event Frames, and alarm/notification records
  • CONNECT Tenants, Namespaces, Types, and Sequential Data Store streams
  • Assets, equipment, and units mapped across engineering and operations models

The AVEVA Integration Challenge

Operators run mission-critical industrial workloads on AVEVA every day, but turning historian- and platform-driven data into reliable API-driven automation is non-trivial:

  • Split surfaces: on-prem PI Web API and cloud CONNECT data services each have their own object models, base URLs, and authentication—integrations must bridge both
  • Authentication variability: PI Web API supports Basic, Kerberos, and Bearer/OAuth, while CONNECT uses OAuth client-credentials clients registered per tenant
  • Tenant and namespace isolation: CONNECT divides each tenant into distinct namespaces with separate data stores, so access must be scoped correctly per namespace
  • Asset Framework complexity: AF hierarchies, templates, and attribute mappings differ per site, so generic tag pulls break without model-aware navigation
  • High-volume time-series: process historians emit dense, high-frequency data that needs efficient batched reads, paging, and compression to move at scale
  • Version and deployment drift: endpoint coverage varies by PI Web API version, CONNECT release, and whether the estate is on-prem, hybrid, or fully cloud

How Supergood Creates AVEVA APIs

Supergood reverse-engineers authenticated PI Web API flows and CONNECT data services interactions to deliver a resilient, normalized API layer over your AVEVA estate—spanning the on-prem historian and the cloud platform.

  • Handles Basic, Kerberos, and Bearer/OAuth for PI Web API plus OAuth client-credentials for CONNECT in a managed session
  • Navigates Asset Framework hierarchies, templates, and attributes so you query by asset and meaning, not raw tag IDs
  • Normalizes responses across tags, streams, elements, events, and CONNECT namespaces so you integrate once against consistent objects
  • Batches and pages high-frequency time-series reads with retry and backoff tuned to historian and tenant limits

Use AVEVA with AI agents: AVEVA MCP Server →

Getting Started

  • Schedule Integration Assessment

Book a 30-minute session to confirm your PI System version, CONNECT tenant and namespaces, and authentication model.

  • Supergood Generates and Validates Your API

We deliver a production-ready AVEVA adapter tailored to your historian, Asset Framework, and CONNECT configuration.

  • Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as AVEVA evolves.

aveva

API Endpoints

Authentication

POST/authenticate

Authenticate to PI Web API (Basic, Kerberos, or Bearer/OAuth) or CONNECT data services (OAuth client credentials) and obtain a session token for downstream calls.

Time-Series

GET/tags

List PI Points/tags and stream metadata with filters for name, point source, descriptor, and data type.

Time-Series

GET/streams

Read recorded, interpolated, or summary time-series values for a stream over a time range with paging.

Asset Framework

GET/elements

Navigate Asset Framework elements, attributes, and templates to retrieve assets by hierarchy and meaning.

Time-Series

POST/write_values

Write or update time-series values to a PI Point or CONNECT stream with timestamp and quality handling.

Events

GET/events

Retrieve event frames, alarms, and notification records with status, severity, and time-range filters.

Use Cases

Centralize historian data in your warehouse

- Pull tags, streams, and AF element attributes from PI System into a single analytics warehouse - Stream recorded and interpolated time-series values to downstream BI and ML tools - Reconcile asset hierarchies across sites for a unified operational data model

Bridge on-prem PI System and CONNECT

- Sync PI Web API streams with CONNECT data services namespaces and Sequential Data Store types - Map tags and AF elements to CONNECT streams for cloud analytics and sharing - Keep hybrid estates consistent as data moves between historian and platform

Automate alarm and event workflows

- Pull event frames, alarms, and notifications into incident and maintenance systems - Trigger downstream workflows on severity, status, and acknowledgement changes - Correlate events with time-series context for root-cause analysis

Push values and configuration back into AVEVA

- Write calculated or third-party values back to PI Points and CONNECT streams - Update AF attributes and metadata from external systems of record - Provision streams and types programmatically across tenants and namespaces

Technical Specifications

Authentication

PI Web API Basic, Kerberos, and Bearer/OAuth plus CONNECT OAuth client-credentials, handled in a managed session

Connectivity

Authenticated PI Web API (REST over HTTPS) and CONNECT data services REST calls to the Sequential Data Store

Response format

Normalized JSON across tags, streams, AF elements, attributes, events, and CONNECT namespaces

Rate limits

Adaptive throttling tuned to your historian and CONNECT tenant to avoid server-side limits

Session management

Automatic token refresh, Kerberos ticket handling, and credential rotation across PI and CONNECT

Data freshness

Near real-time reads on snapshot and recorded values with optional scheduled batch syncs

Security

Encrypted credential vault, scoped access tokens, namespace-aware access, and audit logging

Webhooks

Event-style callbacks for alarms, event frames, and stream value changes

Latency

Sub-second reads on cached and snapshot data; multi-second for large historical time-series pulls

Throughput

Horizontally scaled workers sized to high-frequency historian volume across many tags and streams

Reliability

Retry, backoff, paging, and idempotency keys for high-volume reads and value writes

Adaptation

Continuous monitoring of PI Web API versions, CONNECT releases, and per-site Asset Framework drift

Frequently asked questions

Yes. Supergood works against both the on-prem PI Web API (tags, streams, Asset Framework, events) and CONNECT data services (tenants, namespaces, types, and Sequential Data Store streams), normalizing them into a single API surface.

PI Web API supports Basic, Kerberos, and Bearer/OAuth, while CONNECT uses an OAuth client-credentials client registered in your tenant. Supergood manages both in a single authenticated session with automatic refresh.

Yes. Supergood walks AF elements, templates, and attributes so you can query by asset and meaning rather than memorizing PI Point IDs, preserving each site's model.

Reads are batched and paged with retry and backoff tuned to historian and tenant limits, and support recorded, interpolated, and summary value modes to move dense data efficiently.

Yes. Supergood adapts to your deployment model—operating against the on-prem PI Web API, CONNECT in the cloud, or a hybrid estate—with network configuration tuned to your environment.

Related APIs in Manufacturing & Distribution ERP

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

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.

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?