osisoft-pi · Rate Limits

Osisoft Pi Rate Limits

PI System APIs do not publish per-account rate limits. PI Web API throughput is governed by customer-deployed PI Server / IIS capacity. AVEVA CONNECT Data Services limits are enterprise-customer-specific and disclosed under contract.

2 Limits Throttle: 429

Rate LimitingIndustrialTime SeriesProcess Historian

Limits

PI Web API - Customer-Hosted deployment

varies

bounded by customer-deployed PI Server and IIS configuration

PI Web API runs on customer infrastructure; throughput depends on installation sizing rather than a vendor-set quota.

AVEVA CONNECT Data Services tenant

varies

see AVEVA CONNECT documentation behind developer login

Cloud service limits are tenant-specific and disclosed under enterprise agreement.

Policies

Customer-Operated Throttling

Because PI Web API is typically self-hosted, throttling, retry, and backoff decisions are made by the customer's API gateway or proxy in front of PI Server.

Backoff

Standard exponential backoff with jitter is recommended on any 429 / 503 response.

Sources

https://www.aveva.com/en/products/aveva-pi-system/