At least one example should be included for each API response

Each array field must contain an "items" property.

Each array field must contain an "items" property.

Each array field must contain an "items" property.

Each array field must contain an "items" property.

Each request or response body property must contain a description.

Each request or response body property must contain a description.

Each request or response body property must contain a description.

Each array field must contain an "items" property.

Each request or response body property must contain a description.

Each request or response body property must contain a description.

Each array field must contain an "items" property.

At least one example should be included for each API response

Each request or response body property must contain a description.

Each array field must contain an "items" property.

Each request or response body property must contain a description.

Each request or response body property must contain a description.

Each request or response body property must contain a description.

Each request or response body property must contain a description.

Each request or response body property must contain a description.

Each request or response body property must contain a description.

Each request or response body property must contain a description.

Each request or response body property must contain a description.

"specifications" property must have required property "Embalagem"

Each request or response body property must contain a description.

Each request or response body property must contain a description.

Each request or response body property must contain a description.

Each request or response body property must contain a description.

Each request or response body property must contain a description.

Each request or response body property must contain a description.

Each array field must contain an "items" property.

Each request or response body property must contain a description.

Each request or response body property must contain a description.

Each request or response body property must contain a description.

Each request or response body property must contain a description.

Each request or response body property must contain a description.

Each request or response body property must contain a description.

Each request or response body property must contain a description.

Each request or response body property must contain a description.

Each request or response body property must contain a description.

Each request or response body property must contain a description.

fatal issues detected. Failing the process.

Endpoint descriptions must include a "Permissions" section, with information about License Manager resources and roles.

All endpoint summaries should use sentence case (capitalize only the first letter) and never contain periods (`.`). Exceptions include product names and some specific terms (e.g., SKU, ID).

All endpoint summaries should use sentence case (capitalize only the first letter) and never contain periods (`.`). Exceptions include product names and some specific terms (e.g., SKU, ID).

Response body fields should not contain the "example" field. The response example corresponds to the whole schema.

Endpoint descriptions must include a "Permissions" section, with information about License Manager resources and roles.

Endpoint descriptions must include a "Permissions" section, with information about License Manager resources and roles.

All endpoint summaries should use sentence case (capitalize only the first letter) and never contain periods (`.`). Exceptions include product names and some specific terms (e.g., SKU, ID).

All endpoint summaries should use sentence case (capitalize only the first letter) and never contain periods (`.`). Exceptions include product names and some specific terms (e.g., SKU, ID).

All endpoint summaries should use sentence case (capitalize only the first letter) and never contain periods (`.`). Exceptions include product names and some specific terms (e.g., SKU, ID).

All endpoint summaries should use sentence case (capitalize only the first letter) and never contain periods (`.`). Exceptions include product names and some specific terms (e.g., SKU, ID).

Response body fields should not contain the "example" field. The response example corresponds to the whole schema.

Endpoint descriptions must include a "Permissions" section, with information about License Manager resources and roles.

Endpoint descriptions must include a "Permissions" section, with information about License Manager resources and roles.

Endpoint descriptions must include a "Permissions" section, with information about License Manager resources and roles.

Endpoint descriptions must include a "Permissions" section, with information about License Manager resources and roles.

All endpoint summaries should use sentence case (capitalize only the first letter) and never contain periods (`.`). Exceptions include product names and some specific terms (e.g., SKU, ID).

Endpoint descriptions must include a "Permissions" section, with information about License Manager resources and roles.

All endpoint summaries should use sentence case (capitalize only the first letter) and never contain periods (`.`). Exceptions include product names and some specific terms (e.g., SKU, ID).

All endpoint summaries should use sentence case (capitalize only the first letter) and never contain periods (`.`). Exceptions include product names and some specific terms (e.g., SKU, ID).

All endpoint summaries should use sentence case (capitalize only the first letter) and never contain periods (`.`). Exceptions include product names and some specific terms (e.g., SKU, ID).

Endpoint descriptions must include a "Permissions" section, with information about License Manager resources and roles.

All endpoint summaries should use sentence case (capitalize only the first letter) and never contain periods (`.`). Exceptions include product names and some specific terms (e.g., SKU, ID).

All endpoint summaries should use sentence case (capitalize only the first letter) and never contain periods (`.`). Exceptions include product names and some specific terms (e.g., SKU, ID).

Endpoint descriptions must include a "Permissions" section, with information about License Manager resources and roles.

Endpoint descriptions must include a "Permissions" section, with information about License Manager resources and roles.

Endpoint descriptions must include a "Permissions" section, with information about License Manager resources and roles.

Endpoint descriptions must include a "Permissions" section, with information about License Manager resources and roles.

All endpoint summaries should use sentence case (capitalize only the first letter) and never contain periods (`.`). Exceptions include product names and some specific terms (e.g., SKU, ID).

Endpoint descriptions must include a "Permissions" section, with information about License Manager resources and roles.

Each request body property should have an example. In case the schema is also used as a response and there is already an example elsewhere, feel free to ignore this alert. If you have chosen to include a complete example of the schema to better represent arrays, feel free to ignore this alert.

All endpoint summaries should use sentence case (capitalize only the first letter) and never contain periods (`.`). Exceptions include product names and some specific terms (e.g., SKU, ID).

All endpoint summaries should use sentence case (capitalize only the first letter) and never contain periods (`.`). Exceptions include product names and some specific terms (e.g., SKU, ID).

Endpoint descriptions must include a "Permissions" section, with information about License Manager resources and roles.

Each request body property should have an example. In case the schema is also used as a response and there is already an example elsewhere, feel free to ignore this alert. If you have chosen to include a complete example of the schema to better represent arrays, feel free to ignore this alert.

Each request body property should have an example. In case the schema is also used as a response and there is already an example elsewhere, feel free to ignore this alert. If you have chosen to include a complete example of the schema to better represent arrays, feel free to ignore this alert.

Each request body property should have an example. In case the schema is also used as a response and there is already an example elsewhere, feel free to ignore this alert. If you have chosen to include a complete example of the schema to better represent arrays, feel free to ignore this alert.

Endpoint descriptions must include a "Permissions" section, with information about License Manager resources and roles.

Each request body property should have an example. In case the schema is also used as a response and there is already an example elsewhere, feel free to ignore this alert. If you have chosen to include a complete example of the schema to better represent arrays, feel free to ignore this alert.

Each request body property should have an example. In case the schema is also used as a response and there is already an example elsewhere, feel free to ignore this alert. If you have chosen to include a complete example of the schema to better represent arrays, feel free to ignore this alert.

Each request body property should have an example. In case the schema is also used as a response and there is already an example elsewhere, feel free to ignore this alert. If you have chosen to include a complete example of the schema to better represent arrays, feel free to ignore this alert.

Each request body property should have an example. In case the schema is also used as a response and there is already an example elsewhere, feel free to ignore this alert. If you have chosen to include a complete example of the schema to better represent arrays, feel free to ignore this alert.

Each request body property should have an example. In case the schema is also used as a response and there is already an example elsewhere, feel free to ignore this alert. If you have chosen to include a complete example of the schema to better represent arrays, feel free to ignore this alert.

Each request body property should have an example. In case the schema is also used as a response and there is already an example elsewhere, feel free to ignore this alert. If you have chosen to include a complete example of the schema to better represent arrays, feel free to ignore this alert.

Each request body property should have an example. In case the schema is also used as a response and there is already an example elsewhere, feel free to ignore this alert. If you have chosen to include a complete example of the schema to better represent arrays, feel free to ignore this alert.

Response body fields should not contain the "example" field. The response example corresponds to the whole schema.

Each request body property should have an example. In case the schema is also used as a response and there is already an example elsewhere, feel free to ignore this alert. If you have chosen to include a complete example of the schema to better represent arrays, feel free to ignore this alert.

Each request body property should have an example. In case the schema is also used as a response and there is already an example elsewhere, feel free to ignore this alert. If you have chosen to include a complete example of the schema to better represent arrays, feel free to ignore this alert.

Each request body property should have an example. In case the schema is also used as a response and there is already an example elsewhere, feel free to ignore this alert. If you have chosen to include a complete example of the schema to better represent arrays, feel free to ignore this alert.

Each request body property should have an example. In case the schema is also used as a response and there is already an example elsewhere, feel free to ignore this alert. If you have chosen to include a complete example of the schema to better represent arrays, feel free to ignore this alert.

Each request body property should have an example. In case the schema is also used as a response and there is already an example elsewhere, feel free to ignore this alert. If you have chosen to include a complete example of the schema to better represent arrays, feel free to ignore this alert.

Each request body property should have an example. In case the schema is also used as a response and there is already an example elsewhere, feel free to ignore this alert. If you have chosen to include a complete example of the schema to better represent arrays, feel free to ignore this alert.

Each request body property should have an example. In case the schema is also used as a response and there is already an example elsewhere, feel free to ignore this alert. If you have chosen to include a complete example of the schema to better represent arrays, feel free to ignore this alert.

Each request body property should have an example. In case the schema is also used as a response and there is already an example elsewhere, feel free to ignore this alert. If you have chosen to include a complete example of the schema to better represent arrays, feel free to ignore this alert.

Each request body property should have an example. In case the schema is also used as a response and there is already an example elsewhere, feel free to ignore this alert. If you have chosen to include a complete example of the schema to better represent arrays, feel free to ignore this alert.

Each request body property should have an example. In case the schema is also used as a response and there is already an example elsewhere, feel free to ignore this alert. If you have chosen to include a complete example of the schema to better represent arrays, feel free to ignore this alert.

Each request body property should have an example. In case the schema is also used as a response and there is already an example elsewhere, feel free to ignore this alert. If you have chosen to include a complete example of the schema to better represent arrays, feel free to ignore this alert.

Each request body property should have an example. In case the schema is also used as a response and there is already an example elsewhere, feel free to ignore this alert. If you have chosen to include a complete example of the schema to better represent arrays, feel free to ignore this alert.

Each request body property should have an example. In case the schema is also used as a response and there is already an example elsewhere, feel free to ignore this alert. If you have chosen to include a complete example of the schema to better represent arrays, feel free to ignore this alert.

Response body fields should not contain the "example" field. The response example corresponds to the whole schema.

Each request body property should have an example. In case the schema is also used as a response and there is already an example elsewhere, feel free to ignore this alert. If you have chosen to include a complete example of the schema to better represent arrays, feel free to ignore this alert.

Each request body property should have an example. In case the schema is also used as a response and there is already an example elsewhere, feel free to ignore this alert. If you have chosen to include a complete example of the schema to better represent arrays, feel free to ignore this alert.

Response body fields should not contain the "example" field. The response example corresponds to the whole schema.

Response body fields should not contain the "example" field. The response example corresponds to the whole schema.

Response body fields should not contain the "example" field. The response example corresponds to the whole schema.

Response body fields should not contain the "example" field. The response example corresponds to the whole schema.

Response body fields should not contain the "example" field. The response example corresponds to the whole schema.

Response body fields should not contain the "example" field. The response example corresponds to the whole schema.

Response body fields should not contain the "example" field. The response example corresponds to the whole schema.

Response body fields should not contain the "example" field. The response example corresponds to the whole schema.

Response body fields should not contain the "example" field. The response example corresponds to the whole schema.

Response body fields should not contain the "example" field. The response example corresponds to the whole schema.

Response body fields should not contain the "example" field. The response example corresponds to the whole schema.

Response body fields should not contain the "example" field. The response example corresponds to the whole schema.

Response body fields should not contain the "example" field. The response example corresponds to the whole schema.