Overview
inSCADA API (20260422-7)
Section titled “inSCADA API (20260422-7)”Authentication
inSCADA uses Bearer token authentication for API access.
Standard login flow:
- Call POST /login — returns
access_tokenandrefresh_token. - Click Authorize above and enter the
access_token. - Use POST /refresh with your
refresh_tokento get a new token pair before expiry. - Call POST /logout to invalidate the current token.
OTP login flow (if OTP is enabled for the user):
- Call POST /login — returns
otp_required: true,otp_type, andusername. - Call POST /validate with the received
usernameand the OTP code. - On success,
/validatereturnsaccess_tokenandrefresh_token— proceed as normal.
Multi-Space
If your inSCADA instance has multiple spaces, include the X-Space header with the space ID on every API request. The available space IDs are returned in the spaces field of a successful login response.
X-Space: <spaceId>
Note for browser users: If you are already logged into the inSCADA web app in this browser, your session cookie takes precedence over any Bearer token entered here. To test with a specific Bearer token, use a private window or a separate HTTP client such as Postman or curl.
- inSCADA: https://www.inscada.com - info@inscada.com
- OpenAPI version: 3.1.0
Authentication
Section titled “ Authentication ”bearerAuth
Section titled “bearerAuth ”Security scheme type: http
Bearer format: JWT