Understand API request limits

AVEVA may adjust request limits on a per-minute basis and based on the originating network address.

The service enforces two levels of request limits:

• Service limit: Up to 200 requests per minute to the Integration Service.

• Platform limit: Up to 500 requests per minute across the broader platform infrastructure.

  Note: Requests may be restricted once either limit is reached. When multiple limits apply, the first limit reached takes precedence.

Automatic temporary access restrictions

If traffic exceeds either limit, the following actions occur:

• The originating network address may be temporarily restricted.

• Requests from that address are blocked for five minutes.

• After the restriction period ends, access is automatically restored.

Best practices for managing request limits

To help ensure uninterrupted operation and optimal performance, follow these best practices:

• Spread requests evenly over time and avoid sudden surges in activity.

• If a request is temporarily limited, wait before retrying and gradually increase the delay between retry attempts.

• Reduce unnecessary status checks or repeated requests where possible. Use notification- or event-based approaches when available.

• If multiple systems or users share the same internet connection or gateway, they may also share the same request limits.

Service protection and traffic management

AVEVA may adjust request limits or apply additional traffic management measures as needed to maintain service performance, availability, and security. Integrations must be designed to handle temporary request restrictions gracefully and must not depend on a fixed maximum request rate.