Hi,

I would maybe need a bit of a clarification why you are asking about REST? OPC UA as a technology has nothing to do with REST. The “API” to talk with an OPC UA Server is OPC UA.

Technically there exists a thing called “opc.https” as an alternative transport layer to opc.tcp, but the only thing it does is use the same binary procol as opc.tcp, but inside the TLS channel of the https. So it basically has nothing to do with “web https” (to which I categorize REST to belong) and can only be used with OPC UA Clients that specifically support that transport channel (not many, nor many servers support opc.https, basically best is to just forget it exists).

None of our apps or SDKs offer any REST interface at the moment.

Nothing prevents you from building a HTTP(S) client/server providing REST etc, but that is basically completely application specific logic that you would do yourself and is outside of OPC UA and our SDKs. Like, there might be applications, that support e.g. REST along OPC UA, but they are separate “protocols” so to say (though, OPC UA provides also the information modeling logic outside of the “talk with a server protocol”).