Skip to content


In order to access your OneAPI fleet’s resources with your application, you need an auth client for it. Each client comes with its own OAuth 2.0 client credentials (client_id and client_secret).

If you have multiple applications that require access to the INVERS OneAPI, it is recommended to use separate clients for each application. This not only provides better transparency, but also allows for different sets of permissions for each auth client, thereby increasing overall security.

Please refer to the FleetControl documentation for further information on how to create and manage your auth clients.