External application authentication via client credentials
- Last UpdatedJul 30, 2026
- 1 minute read
- Engineering
- Integration Service 4.1
- Integrators
External applications can authenticate with the AIS CONNECT API using the OAuth 2.0 Client Credentials flow.
To perform this authentication, provide the configured Client ID and Client Secret to obtain an OAuth access token. This token is used to interact with the AIS CONNECT API.
The example below illustrates an application configured to generate a token using the Client Credentials flow.

Note: Always use the Data API URL for integration purposes. The Config API and Web App URLs are provided for reference only.
AIS CONNECT Service Endpoints
|
Endpoint |
URL |
|---|---|
|
Data API (Use for integration) |
https://eu.ais.connect.aveva.com/data |
|
Config API |
https://eu.ais.connect.aveva.com/config |
|
Web App |
https://eu.ais.connect.aveva.com/web |
-
The Client ID and Client Secret are generated from the CONNECT portal (refer Create service applications).
-
The OAuth token obtained via the Client Credentials flow must be included as a Bearer token in the Authorization header of all API requests.
-
Tokens are time-limited and must be refreshed upon expiry.