Mockoon

OpenAPI re-import is now available in Mockoon v9.6.0 🔄 Keeping mock environments in sync with evolving API specifications is a constant challenge. To simplify this, we've added the ability to re-import OpenAPI files into existing mocks. How it works: The option is located in each mock's dropdown menu. Before any changes are made, Mockoon provides a diff summary so you can review exactly what will be added to your environment. Currently supported updates: - New routes: Detected and added based on path and method. - New responses: Automatically created for new status codes. This allows you to evolve your API design in your specification file and pull those changes into Mockoon without losing your existing configuration or having to recreate the environment from scratch. Full details in the docs: https://lnkd.in/dwFMpWXz #Mockoon #OpenAPI #DeveloperTools #APIMocking

Following our work with the GitHub Secure Open Source Fund, we've made Software Bill of Materials (SBOM) a standard part of the Mockoon release process. For our users, security is a top priority. By publishing an SBOM, we provide a full, verifiable inventory of every dependency in our stack. What this means for your team: - Instant vulnerability tracking: easily scan our releases against your own security tools. - Supply chain integrity: complete transparency into the code running in your environment. - Compliance ready: simplifies the vetting process for security teams in regulated industries. SBOMs are published in all our GitHub releases starting with v9.4.0. Read more about how we've hardened Mockoon's security: https://lnkd.in/dCj8Zva4

Mockoon v9.6.0: OpenAPI re-import and goodbye server restarts! 🚀 The latest version of Mockoon is here, and it's all about speed and smoother workflows. We've tackled some of the most frequent friction points to help you build and test APIs faster. Key highlights: 🔄 OpenAPI re-import: You can now update an existing mock with a new OpenAPI specification. Mockoon will show you a summary of new routes and responses before applying the changes. ⚡ Goodbye server restarts: Most configuration changes, including adding/removing routes, changing paths, or updating data buckets, are now applied immediately. No more manual restarts to see your changes in action! ☁️ Cloud live updates: We've aligned the Desktop and Web apps. With the new "Live update" option, your changes to Cloud mocks are propagated in real-time without needing a manual redeploy. 🎨 Command palette improvements: Access your most frequent actions even faster with the new "Recently used commands" list. This release also includes new templating helpers ({{base64url}}, {{replace}} and {{replaceAll}}), improved OpenAPI enum support, and several fixes. Check out the full changelog and update now: https://lnkd.in/dZSBw-F5

New in Mockoon: Copy as curl from the logs tab You can now easily reproduce any request made to your mock APIs by copying it as a curl command directly from the logs. Just open the logs tab, open a request dropdown menu, and select “Copy as curl”. The generated command includes everything you need: method, URL, headers and body. Perfect for debugging, sharing a request with a teammate, or replaying it outside of Mockoon. Small feature, but one that saves time quickly when working with APIs. Learn more: https://lnkd.in/dSiynwak

We're happy to share that SerpApi is now a Platinum Sponsor of Mockoon 🎉 Their support helps us continue building and maintaining Mockoon as a sustainable open-source project. A big thank you to the SerpApi team for backing the project 🙌

☁️ New in Mockoon v9.5.0: Self-host your Cloud environments with the CLI Team and Enterprise Mockoon Cloud subscribers can now self-host the environments they collaborate on using the Mockoon CLI. This makes it much easier to run Cloud-managed mocks locally, in CI, or inside your own infrastructure while still keeping the environment managed and shared through Mockoon Cloud. To start an environment from the CLI, simply provide the Cloud environment identifier and an access token: mockoon-cli start --data cloud://{environment-uuid} --token <access-token> Access tokens can be created from your account settings, and the application now provides the exact pull instructions directly in the environment dialog. More info: https://lnkd.in/dJr9DWDH

☁️ New in Mockoon v9.5.0: Self-host your Cloud environments with the CLI Team and Enterprise Mockoon Cloud subscribers can now self-host the environments they collaborate on using the Mockoon CLI. This makes it much easier to run Cloud-managed mocks locally, in CI, or inside your own infrastructure while still keeping the environment managed and shared through Mockoon Cloud. To start an environment from the CLI, simply provide the Cloud environment identifier and an access token: mockoon-cli start --data cloud://{environment-uuid} --token <access-token> Access tokens can be created from your account settings, and the application now provides the exact pull instructions directly in the environment dialog. More info: https://lnkd.in/dJr9DWDH

It's official: Mockoon is now significantly more secure, thanks to the GitHub Secure Open Source Fund. Back in September, we joined the 3rd edition of the program and took part in a focused 3-week security sprint with guidance from GitHub's security team and partners. This helped us strengthen Mockoon's security posture with concrete improvements across our repositories and release process, including better workflow and branch protections, CodeQL scanning, Dependabot and secret scanning, improved incident response and CVE processes, and our first release including an SBOM. A big thank you to the GitHub team and everyone in the cohort for supporting open-source security! Read our accouncement: https://lnkd.in/dCj8Zva4

🚀 Mockoon v9.5.0: Callbacks now support relative URLs This makes it much easier to trigger endpoints within the same mock environment without having to hardcode full URLs. For example, you can now configure a callback like this: /test-callback Mockoon will automatically resolve it using the mock's hostname and port. So if your mock is running on http://localhost:3000, the callback will be called as: http://localhost:3000/test-callback For CLI / Docker users, you can customize the base URL using the new --public-base-url flag: --public-base-url=https://lnkd.in/drhnsgbr On Mockoon Cloud, the base URL is always the instance's assigned unique URL. This improvement should make environments more portable and easier to deploy! v9.5.0 changelog: https://lnkd.in/dFg25Q7k

Two small but very useful improvements landed in Mockoon v9.4.0 👇 ✅ Quick navigation from logs to route response In the Logs > Requests tab, you can now jump directly to the route response that handled a request. Super handy when debugging large environments (see screenshot). ✅ Zstandard (zstd) support for proxied requests Mockoon now properly handles zstd-compressed responses coming from proxied endpoints. Before, these responses appeared in their compressed form in the logs. Now they're automatically decoded and readable in the logs tab and via the admin API GET /logs endpoint. Supported in desktop + web apps, and also in the CLI/libraries (requires Node.js v22+ in the host environment). More details in the release notes: https://lnkd.in/eppYPXMn