5.0.0 July 24, 2025

Scheduled to release on July 24.

What's New

New Systems
Versioning
Builder Credentials
API Common Fields
Default API URL

Features/Improvements

Systems and System Builder

A new version of system is being introduced with major improvements and architectural changes. The existing version of system will also work without any issues till the new system version gets stable.

New Systems and System Builder (Beta)

Until version 4.4.0, users could build or use systems from the same Systems section. To improve user experience, the builder and user capabilities have been separated. A new System Builder section is introduced for building private systems, while the existing Systems section is now focused on using both public and private systems.

Versioning in Beta Systems

Versioning is now supported for every beta system, enabling upgrades and downgrades. System Builders must create and publish a version before it can be used. Users can choose to upgrade to the latest version whenever a new one is released. Example: Adobe Commerce 2.4.5, 2.4.6, etc.

Builder Credentials in Beta Systems

Builder Credentials are introduced to help System Builders test the system and its APIs during development, before publishing. These credentials are only for builders and won’t be accessible to system users.

Credential Inputs in Beta Systems

Credential Inputs let System Builders define input fields like hostname or other dependencies that need to be collected from users. These inputs will be requested from the user when adding a credential. Builders can access these fields in API Manager like {{inputs.input_name}} .

API Common Fields in Beta Systems

The API Common Fields section lets builders define reusable headers and parameters to be used across all APIs. This avoids the need to redefine them for each API.

API URL in Beta Systems

API URLs are now streamlined for consistency. Instead of using absolute or relative URLs, all URLs will start with the hostname by default. Builders only need to provide the relative URL, ensuring uniformity across all APIs.

Improved Token Authentication in Beta Systems

Dynamic tokens can now be generated through a series of URLs in sequence. Previously, only one token URL was supported, but now users can call multiple URLs one after another to generate a token. The final token can be accessed in API Manager like {{token.access_token}}.

Minor Bug Fixes

A few internal bugs were fixed to improve overall stability.

Last updated

Was this helpful?