APIQuality v2.23 Devportal: New Release Notes of January 2026

Leave a Comment / Release Notes / By

Relase notes

Improvements to the devportal

The devportal has been modified to make it more configurable.

apiportal 

In addition, a custom stage (currently on demand) has been added for automatic deployment on the devportal.

Automatic execution of Newman

More information has been added on how to run Newman without uploading the files, by uploading them directly to the repository. From now on, if we configure the source “Newman properties defined”

 

And it’s not defined; it will give you the possibility of creating the property automatically as long as you have permissions.

Improvements to the API rating dashboard

From now on, the results of stress tests will be displayed directly on the API dashboard.

The result of the mocking will also be shown.

And also more information in the functional tests:

New and improved functionality for editing APIs in APIQuality

From now on, APIs can be designed and modified online without having to re-run the sonar and linter stages, which made the operation quite slow.

If we go to the organization properties, we can activate Redocly Online and Spectral Online

Now we can go and edit an API and we’ll see errors like “Spectral” appear.

This means it is not necessary to keep saving for the stages to be re-executed, as the application will check for errors in the spectral itself in real time.

New fields in the comments in the API definition and sending an email to the owner and followers when the review is being done

When the API is being reviewed from now on, an email will be sent with the

Edit API Template

From now on, you can edit directly from APIquality and create API templates using those loaded by the application by default. To do this, simply click on “create,” select the “Default” template, or “Leave it blank”:

 

And a new template will be created for the APIs

If we click on edit

Improvements to the Kong life cycle

From now on, the configuration saved in the repository will be loaded to ensure there are no discrepancies between git and the database in the kong deployer configuration stage.

In addition, the initializer has been improved to map the tags and service names, so that nothing needs to be modified in the repositories and deployment is automatic.

Before:

Linter Stage Lock Configuration

A new feature has been added that allows you to lock the automatic Linter stage. To do this, simply go to Environments, select the environment where the stage is located, and right-click on “Linter.” Then, select “Lock Stage.”

On the next screen we will select the letter where we want to block.

Global configuration for the openapi2postman stage per environment

From now on, a global configuration will be allowed when configuring the stage, and therefore it is not necessary to configure it for each API.

To configure it, we must go to environments and select the environment to configure.

After that, we can go to the API and generate it without needing to reconfigure it in the API pipeline.

Creating an API manager template configuration

To create a new API manager configuration from an architecture perspective, it is no longer necessary to upload the file; it can be created directly by selecting the name and the API manager to configure.

The editor will then show you a pre-loaded default template:

Deploying imported APIs in Wso2

APIs imported via wso2 can be deployed automatically since not only is OpenAPI being imported, but also the entire API project configuration.

Correlation of initializer and deployer stages

From now on, the deployment stages of the different API managers will display a warning and redirect to the initializer if the stage has not been configured/executed.

Improvements on Github interaction

Uploading JMeter reports to an S3 repository on GitHub stages

From now on, JMeter reports will be uploaded to S3.

New or modified stages

  • The openapi-diff stage has been configured so that it does not fail if there are no changes and there are no previous updates.

 

Improvements in integration with Gitlab

Runner Tagging Configuration

A new organization-level property has been added to configure runner tagging in GitLab.

Bitbucket integration improvements

Domain Configuration

The ability to configure domains in Bitbucket has been added. Previously, domain names were not configurable.

Now, the name will be the same as the domain name:

New stages and updates to existing ones:

  • The openapi-diff stage has been configured so that it does not fail if there are no changes and there are no previous updates.

Improvements in integration with Azure DevOps

New stages and modifications in Azure DevOps

  • New stage of Kong initializer
  • New stage of Kong deployer
  • New Kong validator stage
  • The openapi-diff stage has been configured so that it does not fail if there are no changes and there are no previous updates.

Importing APIs from Standards

It has been configured to allow direct import of OpenBanking and OpenTelco APIs. Simply select “Definition Standard” as the source, choose the standard, and then import the API you wish to use as a template.

Default Stages and Branches

The application has been changed so that when we create new APIs, the following stages and a single branch, development, are created by default:

  • Linter
  • SonarQube
  • Enricher
  • OpenAPI Diffs
  • Sonar2Spectral
  • Microcks
  • OpenApi2Postman
  • Open API Generator
  • Openapi2jmeter
  • Newman
  • jmeter
  • Zap Proxy

Improvements in the Wso2 life cycle

From now on, gateways for deployment can be given an alias to make them more intuitive.

IBM Lifecycle Improvements

The deployment process has been improved to maintain subscriptions when redeploying a version of an API.

Improvements in the Apigee life cycle

The Apigee lifecycle is improved so that the initializer stage performs the following operations:

  1. Create the API proxy workflow using OpenAPI
  2. Apply the templates configured from architecture and selected in the initializer.

This allows you to deploy apiproxies on Apigee without having to edit any lines of code.

In addition, the possibility of configuring targets by name or by URL has been added, thus avoiding changing the default XML files created in the initializer.

Bugs and minor improvements

 Minor improvements

  • The property used to add the repository name to wso2 has been renamed from github_url to github_repo
  • From now on, it is permitted to change the name of the life cycle
  • From now on, when you save the configuration of an API manager, you will be returned to the API manager configuration list screen.
  • The size of the API catalog listing has been increased so that the information can be viewed more clearly.
  • Vertical scrolling has been removed from the import api screen
  • If the system gives an error when saving the openapi edit, the automatic executions will not start.
  • A new button has been created to delete all notifications
  • The decimal places for Microcks have been reduced
  • The default API review has been disabled every time the API is saved in new organizations.
  • A new screen has been added to accept the terms and conditions if they have changed.

1.22.2. Bugs

Now, the name will be the same as the domain name:

Leave a Comment

Your email address will not be published. Required fields are marked *