As industrial automation shifts toward Industry 4.0, the demand for seamless connectivity between Operational Technology (OT) and Information Technology (IT) has never been higher. Siemens addresses this need within the WinCC Unified environment by providing a powerful, standards-based REST API.
This guide covers the architecture, authentication, key functionalities, and a practical example of how to interact with the API.
"name": "Pump_Setpoint",
"value": 42.5,
"quality": 192,
"timestamp": "2023-10-27T14:30:05.123Z",
"errorCode": 0,
"errorDescription": ""
Note on Quality Codes: The quality field follows OPC standards. A value of 192 (0xC0) typically means "Good". wincc rest api
Siemens continues to enhance the REST API. Expected future capabilities include:
A data scientist trains a model in Azure Machine Learning. As industrial automation shifts toward Industry 4
GET /WinCC/REST/Tags/TagName
"Name": "Tank_Level",
"Value": 75.4,
"Quality": "Good",
"Timestamp": "2025-03-15T14:32:01Z"
GET /api/v1/history/Tank1_Level?start=2025-03-01T00:00:00Z&end=2025-03-02T00:00:00Z&interval=1m
Exposing industrial controls via REST is powerful but risky. Follow these rules: "name": "Pump_Setpoint", "value": 42
| Do ✅ | Don’t ❌ | |-------|----------| | Use HTTPS only (never HTTP) | Disable certificate validation | | Implement IP whitelisting | Use Basic Auth over unsecured networks | | Rotate API tokens regularly | Expose WinCC directly to the internet (use VPN/gateway) | | Create low-privilege API users (read-only if possible) | Give the same token write access to everything | | Log all API access attempts | Hardcode tokens in client code |
Pro tip: Place an API gateway (like NGINX or Azure API Management) in front of WinCC to add rate limiting, request validation, and additional authentication layers.