Let's see an example where we have a RESTful service (in fact it's a Business Component exposed as a Rest service). Suppose that we want to build a consumer for that service.
We've activated the Generate OpenAPI interface property so the default.yaml file is available for us. As we need to implement a consumer, the documentation will help us for that purpose.
Note that the information of the OpenAPI (Swagger) docs can be easily read using the OpenAPI import tool.
However, here we explain how the same process could be done (with a rational analysis effort) using the Swagger UI tool.
Let's start looking at the Product BC structure and properties:
- Expose as Web Service= TRUE
- Web Service Protocol= Rest Protocol
We'll concentrate here on the HTTP POST method. In particular for that HTTP verb, the default.yaml file includes the following lines:
summary: "Inserts a Product"
- name: "ProductId"
description: "Product Id"
- name: "Product"
description: "SDT of Product"
description: "Successful operation"
description: "Not found"
Graphically, it is represented as follows by the Swagger UI:
You can click on "Try this operation", and complete the request form that appears, which looks as shown in this example:
After completing the form you have the following summary of the HTTP Request, where you can get information about the HTTP headers used to execute the HTTP POST verb, and the JSON body format.
The JSON Body can be imported in GeneXus using the JSON Import tool (Tools > Application integration), and the correct SDT for that JSON format will be automatically created in the KB.