: Secure endpoint access utilizing standard web security protocols. Authentication and Security Protocols
write_url = f"wincc_host/WinCCUnified/WriteTagValue"
REST fits the “easy integration, moderate speed, occasional access” sweet spot.
that allows external applications to interact with SCADA data using standard HTTP methods and JSON. It serves as a modern bridge between industrial OT (Operational Technology) and IT environments, enabling AI agents, web dashboards, or custom applications to read and write tag values and configuration data. 1. Key Capabilities Data Access : Read and write both Runtime data (live tag values) and Configuration data (project setup). Standardized Methods wincc rest api
: A built-in JSON configurator helps users define endpoints and trigger methods based on specific tags or alarms.
When deploying applications that rely on the WinCC REST API in production environments, keep these best practices in mind:
Because industrial systems control physical machinery, security is paramount. The WinCC REST API enforces strict security measures: : Secure endpoint access utilizing standard web security
import requests import json # Configuration variables WINCC_HOST = "192.168.1.50" PORT = "443" API_URL = f"https://WINCC_HOST:PORT/api/v1/tags" AUTH_TOKEN = "Bearer YOUR_ACCESS_TOKEN_HERE" headers = "Authorization": AUTH_TOKEN, "Content-Type": "application/json" # Define the tags we want to monitor params = "names": "Oven_Temp_Zone1,Conveyor_Speed" try: # Making the GET request (ignoring self-signed SSL certs common in local OT networks) response = requests.get(API_URL, headers=headers, params=params, verify=False) if response.status_code == 200: data = response.json() for tag in data.get("tags", []): print(f"Tag: tag['name'] | Value: tag['value'] | Status: tag['quality']") else: print(f"Failed to connect. HTTP Status Code: response.status_code") print(response.text) except requests.exceptions.RequestException as e: print(f"An error occurred: e") Use code with caution. Use Cases for the WinCC REST API
The shift toward Industry 4.0 has made the WinCC REST API an essential tool for digital transformation.
Monitoring system health requires a direct line into the WinCC Alarm Logging system. External applications can poll for active alarms or push acknowledgments back to the control room. : https:// /api/v1/alarms/active Method : GET Common Use Cases for WinCC REST Integration Enterprise Resource Planning (ERP) Syncing It serves as a modern bridge between industrial
API access is bound to the WinCC User Management system. You can create specific API users with restricted "Read Only" access to prevent external systems from accidentally changing critical machine setpoints.
The WinCC REST API bridges the classic SCADA world with modern web and cloud ecosystems. It’s not the right tool for every job (stay away from high-speed control loops), but for dashboards, reporting, ERP integration, and remote monitoring, it’s a game-changer.
: The REST service typically operates on port 34568 by default.
This technical guide explores how to leverage the WinCC REST API to read process values, acknowledge alarms, and seamlessly connect your shop floor to enterprise applications like ERPs, MESs, and cloud analytics. Understanding the WinCC REST API Architecture
An authorized API user account (e.g., username: api_user , password: SecretPassword123 ).