Wincc Rest Api < 2027 >
Using the POST method in the WinCC REST API (introduced in WinCC V8.0) is primarily used for writing tag values to the Runtime or for initial authentication. Key Uses for POST
Real-time patterns
- If REST supports only polling, implement efficient poll intervals and delta checks.
- Use push-based alternatives when supported (WebSockets, SignalR, OPC UA Pub/Sub, MQTT gateways) for lower-latency, scalable designs.
Then came the WinCC REST API — officially introduced with WinCC Professional (TIA Portal V15+ and later). At first glance, it sounds like a magic wand: “HTTP? JSON? Great, my web developer can now talk to a power plant.” wincc rest api
REST API (Server Role): Introduced in WinCC V7.5 SP2 and enhanced in WinCC V8.0, this acts as a passive interface. External applications (like AI agents, ERP systems, or custom web dashboards) can "pull" data from WinCC or "push" values to it. Using the POST method in the WinCC REST
- Check the box: "Enable REST API".
- Set the port number (default is 80 for HTTP, 443 for HTTPS). Ensure no other service conflicts.
REST Service (Inbound): External apps call WinCC to request or update data. If REST supports only polling, implement efficient poll
Tokens usually expire after a configurable time (default 8 hours).
Now, when the plant manager looks at their smartphone, they aren't just seeing a static screenshot; they are seeing live, JSON-formatted data pulled directly from the WinCC Runtime
# Configuration url = "https://wincc-server:443/api/v1/tags/Pump_Setpoint" user = "WinCCOperator" password = "SecurePassword123"