Our Web API solution runs as a service and provides a doorway to push and pull information from a System Five database. This technology will work with both onPrem installations and our System Five on Cloud deployments.

The following is an explanation for retrieving and using the Swagger 2.0 documentation from all available endpoints of the Windward Web API.

There are multiple endpoints available for the Windward Web API each providing different functions for the Web API. These endpoints are the following:

1. APBill
2. Category
3. Customer
4. Inventory
5. Invoice
6. Keyword
7. Units
8. Vendors
9. VirtualInventory
10. TServerMethodsWebAPI (Most methods in this endpoint are deprecated)

All of these endpoints can be accessed with either of the following URLs:

• http://API_IP_ADDRESS:API_PORT/Windward/WebAPI/ENDPOINT
• http://API_IP_ADDRESS:API_PORT/datasnap/rest/ENDPOINT

The 6.2.2 released versions of the Web API has a maximum limit of 32 concurrent connections. This limit has been removed in the 6.2.7 beta version and is now limited by how much available memory is on the server or workstation running the API.

The Swagger documentation for a particular endpoint can be retrieved by using a method of the endpoint. Using your preferred method or app (we suggest Postman), send a GET request to one of the following URLs:

• http://API_IP_ADDRESS:API_PORT/Windward/WebAPI/ENDPOINT/Swagger
• http://API_IP_ADDRESS:API_PORT/datasnap/rest/ENDPOINT/Swagger

The contents of the response from the calls is the Swagger 2.0 documentation, after copying the response text and saving it into a text file use your preferred Swagger editor (we suggest editor2.swagger.io) to view the Swagger documentation.

1. Open Postman.
2. Set the request type to GET.
3. Enter one of the URLs, substituting the API_IP_ADDRESS, API_PORT and ENDPOINT placeholders with the appropriate information for your Web API installation:
   • http://API_IP_ADDRESS:API_PORT/Windward/WebAPI/ENDPOINT/Swagger
   • http://API_IP_ADDRESS:API_PORT/datasnap/rest/ENDPOINT/Swagger
4. Set the authorization type to Basic and enter your Web API credentials.
5. Send the request.
6. Copy the complete text in the Response area and save it as a text file.

1. Open the json file in a text editor and copy the contents to your clipboard
2. Open a web browser (Google Chrome, for example) and navigate to the following URL:
   • editor2.swagger.io
3. Click on the 'File' menu.
4. Click on 'Paste JSON'.
5. In the Swagger 2.0 documentation dialog Right click and choose Paste from your clipboard
6. Click on 'Import' button.
7. The list of available methods are now listed on the right side of the screen. Each method has two sections, a Parameters and a Response section, these sections outline the format for both the request parameters and the response.

1. As of Beta 6.2.7, The Swagger 2.0 documentation can be viewed and interacted with through a browser.
2. Using a set of options in the S5WebAPISvc.ini file, the configuration of the Swagger publishing can be set and changed.
   1. 
3. Once the S5WebAPISvc.ini options have been set, and the WebAPI service is running, open a web browser and enter localhost:PORT/index.html into the address bar
   1. Where PORT is the port under the Swagger Publishing options in S5WebAPISvc.ini
4. After entering the WebAPI credentials and clicking the 'Submit' button, the swagger-ui page will be shown.
5. On this page, edit the contents of the search/explore bar. Changing the values for PORT, and ENDPOINT
   1. PORT is the port that the WebAPI is listening on (specified in S5WebAPISvc.ini, under the HTTP/HTTPS option)
   2. ENDPOINT is any one of the endpoints of the WebAPI.
6. After clicking on the 'Explore' button and waiting for the Swagger 2.0 documentation to load, click on the 'Authorize' button and reenter the WebAPI credentials, this must be done before being able to call any of the endpoint's methods.
7. Once authorized the Swagger 2.0 documentation and WebAPI service can be interacted with.
   1. By clicking on an API method, the page will show more information for the method.
   2. Clicking the 'Try It Out' button allows users to enter parameters, and run the method.
   3. Clicking the 'Execute' button will send the method and it's parameters (if any) to the API, giving back the API's response.