VisualCron is a powerful tool for automation of software processes. It also allows for user interactions using a Web API (Application Programming Interface). It is a REST and SOAP API. In this article we look at what these terms mean, and how VisualCron implements them.
An Application Programming Interface, as the name suggests, works as a channel between two programs (or applications), allowing them to exchange information. This information usually travels one way, as in, the client software pulling information from the API doesn’t push the information to the API server.
REST APIs are the interfaces that are designed with Representational State Transfer system architectural style. The access to information is provided via resources, rather than request commands. The messages are self-descriptive, meaning that there is no need to interpret every message in context. The connection is also stateless, meaning that every message has all the information necessary to justly interpret it.
Also, how the data is represented internally in the server, is not exactly how the data is represented to the client. Hyperlinks also play a central role in interaction with any REST system. In the initial, and every message transaction, the server includes hyperlinks, which can then be used to gain further information.
Once you enable the Web API by allowing it from the “Server Tab” of the “Server settings”, you can choose to use unencrypted or encrypted ports. As the REST service communicates through the HTTP protocol, and outputs in plain text format, XML, and JSON. You can also set which columns are included in the message. In addition, you can also use the SOAP Web service. You can find the WSDL URL in the Web API tab in the server settings.
As you will see, the web API is an easy way of extracting information and logs from VisualCron local server. The best thing about this is that, in addition to being another way of interacting with the software, it requires no programming expertise on part of the operator. Now you can implement the knowledge gained in making the VisualCron more useful to your company’s needs. For more information on this and other uses of Visual Cron, consider reading the latest blog posts, or take a look at the documentation.