2025-10-31
Welcome to this new release of Mockoon. It brings many improvements among which: revamped OpenAPI import, support for OpenAPI in the web application, improved cloud logs in the desktop application, new plural request helpers, and many more. Read on to learn more about this release.
Mockoon is proudly independent and open-source, maintained without external funding. We rely on both sponsorships and Mockoon Cloud subscriptions to keep improving the project and building new features. A big thank you to the companies below for supporting our work and helping us grow (and all the sponsors who helped this project over time!):
If you'd like to support Mockoon as well, you can become a sponsor or subscribe to Mockoon Cloud, every contribution helps keep the project alive and evolving. Thank you!
The web application now supports OpenAPI imports and exports. We took the opportunity to refactor the import/export code to share it between the desktop and web applications. It also offers a better experience, letting users import specifications from a URL, file or clipboard, and shows a preview of the specification before importing it.

The new import options are available in the "New environment" menus, and in the command palette (Ctrl/Cmd + P). The OpenAPI export option is available in the command palette and lets the user export in both JSON and YAML formats.

(Issue #1821)
In the desktop application, it is now possible to view both the local and cloud log entries, and to filter them accordingly. (Issue #1808)
In both the desktop and web applications, cloud logs are now reloaded when reopening the application or reloading the web page. Previously, the applications only supported a "live" view of the cloud instance logs as they were created. They were lost after an application or page reload. (Issue #1807)

We removed the possibility to deploy local mocks to a Cloud instance. While we like to offer more flexibility, this feature was barely used and maintaining it was adding unnecessary complexity to the codebase, especially when performing maintenance operations on our servers. To help with the transition, we added a new command in the command palette (Ctrl/Cmd + P) to "Convert a local environment to cloud". This command will create a new cloud mock from the selected local environment, preserving all its data, and linking it to a running Cloud instance.
(Issue #1818)
The audit trail is now available in your Mockoon Cloud dashboard. You can access it from the "Audit Trail" link in the sidebar. It currently logs important team and account events, such as account upgrades, team member invitations or removal. The audit trail will be expanded in future releases to include resource changes such as environment deployments, configuration changes, etc.
Learn more about the audit trail in our documentation.
allOf properties are handled during OpenAPI import. It is now correctly merging the various schema sources instead of parsing the first one only. (Issue #1390)Multiple new request template helpers were added:
headers: returns a key/value object containing all request headers.urlParams: returns a key/value object containing all route parameters.queryParams: returns a key/value object containing all query parameters.These helpers can be used to easily enumerate, filter, transform, these objects. Some examples:
Copy: User ID provided: :
(Issue #1827)
--format flag for the export commandAs part of the OpenAPI import/export revamp, a --format json|yaml option was added to the CLI's export command to specify the export format.
(Issue #1821)
We added a new link in the logs request tab to navigate to the route response which caught the request.

(Issue #1794)
zstd were shown in their compressed format. Now, Mockoon will show them uncompressed in the logs tab and admin API /logs endpoint. This is supported in the desktop and web applications, and in the CLI/libraries, as long as the host environment uses Node.js v22 or higher. (Issue #1577)status template helper is now correctly validating its input instead of causing internal server errors when provided with invalid status codes. (Issue #1840)Expect: 100-continue header is present. (Issue #1126)node_modules folders and reinstall the dependencies using npm install (at the root of the repository). All the relevant scripts and documentation have been updated accordingly. (Issue #1888)A big thank you to the following people who helped to make Mockoon better: