Introduction to PureWL APIs

1- Platform Independence

The API’s RESTful architecture ensures compatibility across multiple programming languages and platforms. Any application capable of sending and receiving RESTful messages can interact with the API. Built on open standards, the API allows you to select any technology that meets your requirements, such as J2EE, .NET, PHP, ASP, etc., for integrating with PureWL.

2 – Ease of Integration

The application builds a RESTful request message which encodes your connection request, sends it via HTTPS to the web service, and waits for a RESTful response message. The response contains your connection requests status. Since RESTful and HTTPS are designed to be lightweight protocols, building requests and parsing responses is a straightforward. Furthermore, rarely do you have to do this manually, since there are a number of libraries available in various technologies. Building a RESTful request and handling the response is reduced to a few lines of code.

Integrators of the PureWL API should have a working knowledge of Web Service, RESTful and JSON; in addition to a full understanding of how to integrate data into an application or web site. All supporting software needed to support API should be installed in a development environment prior to Web Service implementation. The Integrator must be proficient in their selected programming language.

3 – Security

All communication between your application and PureWL API is SSL-encrypted. Your application has a client certificate, which identifies it uniquely with the web service. The API holds a server certificate, which your application checks to ensure that it is communicating with the API. These security mechanisms guarantee that the connection request data sent to PureWL API stays private and is available only to your application.