Dataview supports communicating with external services via JSON-RPC

Dataview performs certificate validation by ensuring the certificate Dataview sees is the same as the certificate stored locally. You can create a certificate with and Issuer or Subject, so long as the common name matches and the certificate has not expired. For example, if you wanted to communicate with a server at 172.16.9.101, the following values would be appropriate:

$ openssl req -new -x509 -key server.pem -out cert.pem -days 730
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [AU]:US
State or Province Name (full name) [Some-State]:Washington
Locality Name (eg, city) []:Seattle
Organization Name (eg, company) [Internet Widgits Pty Ltd]:WLNet Dataview
Organizational Unit Name (eg, section) []:WLNet Dataview 
Common Name (e.g. server FQDN or YOUR name) []:172.16.9.101
Email Address []:

The easiest way to add support for additional transports is to implement a JSON-RPC server (or extend one of Dataview's provided JSON-RPC servers) to communicate through your transport. For example if you wanted to communicate over a REST API, you could write a RPC server that defined methods such as do_get do_post etc. and have it perform the HTTP operation within your code.