Mockoon release v9.6.0

2026-04-01

Welcome to this new release of Mockoon. It brings many improvements, including OpenAPI re-import, no more server restarts, and live updates for cloud mocks. Read on to learn more about this release.


 Support us!

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!):

GitHub Localazy
SerpApi TestMu AI

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!

sponsor button subscribe to cloud button

 OpenAPI re-import

You can now re-import an OpenAPI specification in an existing mock to update it with the new specification content:

view of the re-import OpenAPI summary

The option is available in each mock's dropdown menu and will show a summary of the changes that will be applied to the mock before confirming the re-import.

Currently, the following changes can be applied when re-importing an OpenAPI specification:

  • new routes, based on the path and method.
  • new responses, based on the status codes present in each route.

Learn more about OpenAPI re-import

(Issue #765)

 Goodbye server restarts!

Starting with this release, mock servers no longer need to be restarted when you make changes to most of the mock configuration. view of the restart needed arrow icon

In the past, part of the changes made to the mock configuration were applied immediately (responses, callbacks, headers, rules, etc.) while other changes like adding or removing a route, or changing a route path and method, required a server restart to be applied.

All changes are now applied immediately without the need to restart the server, which should make the development experience smoother and faster. This includes modifications made to data buckets, adding, removing, reordering, or modifying a route (e.g. updating the path or method), changing the server prefix or latency, enabling/disabling the proxy, etc. The only changes that still require a server restart are related to TLS configuration and the hostname/port of the server.

This behavior is always enabled in the desktop application. When self-hosting with the CLI or Docker image, the running mock can be updated in the same way using the admin API endpoints. For our Cloud users, the running mock is automatically updated when the live update option is enabled (see below).

[⚠️ potential breaking change] To achieve this, we reimplemented route matching using the path-to-regexp library instead of relying on Express.js routing. We decided to use the latest version, which includes some breaking changes (also part of Express 5), notably wildcards requiring a name: /*/*wildcard. We ensured backward compatibility by automatically converting old syntaxes to the new ones allowing you to use the one you prefer (Express 4 or Express 5 style). However, some regex syntaxes are no longer supported, especially the one using brackets, /[discussion|page], which should be replaced by a parameter, a wildcard, or a rule. You will find more details about the supported route path syntaxes in our updated routing documentation.

(Issue #2078)

 Cloud live updates

Until now, updating a Cloud mock from the desktop application or the web application did not produce the same result: the desktop application always required a manual redeploy to apply changes, while the web application propagated changes immediately without redeploying. With this release, we are aligning the behavior of both applications by introducing a new live update option in the deployment dialog:

view of the deployment dialog showing the new live update option

When enabled, the live update option allows you to apply changes to your Cloud mock immediately without needing to redeploy it. This means that any changes made to the mock configuration are propagated to the running mock in real time, including changes that previously required a redeploy (e.g. adding a route, changing a route path, or changing a route method, see above). When disabled, the behavior remains the same as before, and you need to redeploy the mock manually to apply changes.

(Issue #2135)

 Command palette - Recently used commands

The command palette now shows a list of recently used commands, allowing you to quickly access and execute them again:

view of the recent commands in the command palette

(Issue #2036)

 Improvements

  • "Header" rules now support auto-completion for header names and values. (Issue #2038)
  • Two new helpers were added to encode/decode to and from URL safe base64: {{base64url}} and {{base64urlDecode}}. (Issue #2058)
  • Two new helpers were added to replace one or all occurrences of a string: {{replace}} and {{replaceAll}}. (Issue #2059)
  • Support was added for number enums when importing OpenAPI specifications. (Issue #2113)
  • The oneOf template helper now supports a simplified syntax: {{oneOf 'value1' 'value2' 'value3'}}. The old syntax {{oneOf array}} (where array is an array of values coming from another helper or variable) is still supported. Newly imported OpenAPI specifications will use the simplified syntax. (Issue #2109)

 Fixes

  • stringify template helper compatibility with other helpers was improved. (Issue #2060)
  • The request Content-Type check, on which JSON parsing depends, is now case-insensitive. (Issue #2093)
  • (Partially) fixed an issue where the Mockoon Snap version was unable to start correctly since v9.4.0. (Issue #1909)
  • Fixed desktop application installation failing on some Linux distributions due to conflicting files. (Issue #2064)
  • Logs now contain a UUID field to uniquely identify and deduplicate them. (Issue #2037)
  • Switching between "CERT" and "PFX" settings in the TLS configuration now correctly uses the self-signed certificate even when PFX settings are filled. (Issue #2118)

 Chores

  • We updated the libraries and application dependencies to their latest versions to fix several vulnerabilities.
  • We updated the application to Angular 21 which allowed us to remove some dependencies. (Issue #2127)

 Thank you

A big thank you to the following people who helped to make Mockoon better:

  • @rohanakode490: Command palette's recently used commands, header rules auto-completion, URL safe base64 helpers, string replace helpers, stringify helper improvements.