Wincc Rest Api New! Now

The WinCC REST API (and the related REST Connector) is a modern interface introduced primarily in WinCC V8.0 and WinCC Unified to bridge the gap between industrial OT (Operational Technology) and standard IT environments. It allows external applications to interact with SCADA data using standard web protocols like HTTP and JSON. Core Functionality WinCC handles REST in two distinct ways:

WinCC REST Service (Passive): Acts as a server. External applications (like custom web dashboards, AI agents, or mobile apps) send HTTP requests to WinCC to read or write tag values and configuration data.

WinCC REST Connector (Active): Acts as a client. WinCC "actively" sends data out to external systems, such as pushing production metrics to a cloud service or a third-party web API. Key Features & Methods The API uses standard HTTP methods to manage resources:

GET: Used to read runtime values (tags) and project configuration data. wincc rest api

POST: Typically used for sending multiple values in one request body.

PUT: Used for write access to specific resources, such as updating a tag value or sending data to a cloud endpoint. Technical Requirements

Licensing: Generally requires the WinCC/Connectivity Pack or a similar option to enable the service. The WinCC REST API (and the related REST

Security: Supports HTTPS and secure authentication. You must configure certificates via the WinCC Certificate Manager and can assign specific read/write authorizations per tag.

Configuration: The service is activated in the WinCC Configuration Studio under "Computer" settings, where you define the Host name and Port (default is often 34568). Common Use Cases

AI Integration: Feeding real-time process data into Python-based AI models for predictive maintenance. Authentication & security

External Reporting: Pulling historical or live data into tools like Power BI or Excel for business analytics.

Cross-Platform Apps: Building lightweight mobile or web apps that don't need a full WinCC client installation.

Cloud Connectivity: Using the REST Connector to push data to IoT hubs or AWS/Azure endpoints.

0 or Unified, or perhaps a code snippet to get started with a GET request? WinCC V8.0 REST API Overview | PDF - Scribd

5. Retrieve Historical Data (Archives)

GET /api/v1/history/Tank1_Level?start=2025-03-01T00:00:00Z&end=2025-03-02T00:00:00Z&interval=1m

Authentication & security

• Supported auth methods vary by product/version: Windows Integrated Authentication (Kerberos/NTLM), Basic over HTTPS, and token-based schemes in newer releases. Always use HTTPS — do not send credentials over plain HTTP.
• Use least-privileged accounts for API access. Prefer service accounts with scoped read/write rights.
• If using Basic auth, restrict to TLS and rotate credentials regularly.
• Consider network-level protections: IP allowlists, VPN, and reverse proxy with WAF for exposed endpoints.

Response Format (JSON)

  "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".

2. Write to a Tag

curl -X PUT "https://192.168.1.100/api/v1/tags/Tank1_Level" \
     -H "Authorization: Bearer <token>" \
     -H "Content-Type: application/json" \
     -d '"value": 50.0'