API

Netuno has its own framework for creating REST APIs in a low-code way, with support for JWT (JSON Web Token) and OpenAPI 3.0.

The entire framework for developing web services in Netuno is very versatile, allowing any type of development.

The framework already provides many features for low-code development, saving many lines of code to meet the most common needs such as sending emails, consuming other REST APIs, integrating with other databases, generating PDF and Excel files, sending SMS, manipulating database data, among many others.

And when there are no solutions in Netuno's framework, it is possible to easily integrate existing Java, Kotlin, or even JavaScript libraries to develop custom resources and integrate them with Netuno's framework.

JWT - JSON Web Token

JWT.io is the specification of the standard for passing session context data to the client via a JSON object.

Thus, the server does not need to store the sensitive data of logged-in users in the session; instead, it becomes a token that is transmitted to the client, and later, on each request, this token must be returned.

This token undergoes some security checks, such as its expiration time and a process that allows creating a new token without requiring re-authentication.

Netuno has integrated support for JWT; it is simple and easy to use, and it also works integrated with Netuno's native users and authentication.

OpenAPI 3.0

After the success of Swagger v1 and v2, which long ago became a standard for developing web service definitions and generating client code.

Thus, Swagger made its definition open and became OpenAPI 3.

Where it remains the foundation for defining the standard for how the API is documented and how clients are generated to consume the API.

Netuno already provides full integration with OpenAPI 3.0 and uses the OpenAPI definition together with JSON Schema validation.

This means that Netuno also allows validating the input and output of web services, using validation of the JSON schema obtained and returned, thus for:

• Input: If there is a call to the web service that does not comply with the structure and validations, then it is rejected
• Output: If it returns data that does not comply with the defined structure and validations, then an alert is generated that the web service is not compliant.

Thus, Netuno both saves the creation of many ifs in code for validating received data and also guarantees validation of the result that the web service is generating, performing a unit test.

The structure of the OpenAPI generated by Netuno can also be used with the Swagger Editor to generate the testing interface, documentation, and client code for the API in other technologies.

Basic

Netuno also supports creating web services and authentication without complications, meaning it is not mandatory to use JWT or OpenAPI, although it is the standard recommendation.

Often, to speed up API creation or in situations involving server-to-server communication, one chooses to simplify as much as possible and save time.

Netuno supports HTTP authentication.