2026-01-13
Welcome to this new release of Mockoon. It brings many improvements among which: CLI self-hosting for cloud environments, relative URL support in callbacks, curl command copying from logs, and 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!
Team and Enterprise Mockoon Cloud subscribers can now self-host Mockoon Cloud environments they collaborate on using Mockoon CLI.
To do so, open the application dialog from the environment dropdown and follow the instructions to pull the environment using the CLI:

You will be able to pull the environment using the mockoon-cli start command and by providing an access token and the Cloud environment identifier. Access tokens can be created from your account settings.
More information about this new feature can be found in the documentation.
Two modifications were made to the CLI to support this feature:
--data flag now accepts Cloud environment identifiers cloud://{uuid} to differentiate them from local environment files.--token flag was added to provide the access token needed to pull Cloud environments.(Issue #1736)
To make it easier to call endpoints within the same mock, relative URLs are now supported in callbacks:

The relative URL will be constructed using the mock's hostname and port, for example: /test-callback will be called as http://localhost:3000/test-callback if the mock is running on localhost:3000.
When using the CLI or Docker image you can customize the base URL using the --public-base-url flag (e.g. mockoon-cli start ... --public-base-url=https://my-mock.example.org). On Mockoon Cloud, the base URL will always be the unique URL assigned to your cloud instance.
(Issue #1730)
You can now copy a curl command from the logs tab to easily reproduce requests made to your mock APIs. Select "Copy as curl" from the log entry context menu to copy the command to your clipboard:

The generated command includes the request method, URL, headers and body, for example:
Copycurl --location --compressed --request GET "https://mock-1234.mockoon.app/test" --header "host: mock-1234.mockoon.app" --header "user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36"
(Issue #1458)
baseUrl templating helper will use the --public-base-url flag value when running with the CLI or Docker image to generate URLs consistent with the mock's public URL. (Issue #1488)/users/{user-id}). (Issue #2012)application/problem+json example response body is now created. (Issue #2009)A big thank you to the following people who helped to make Mockoon better: