The easiest and quickest way to design and run mock APIs locally, with desktop, CLI, and cloud options.
Mockoon is an open-source API mocking tool that allows developers to design and run mock APIs locally without remote deployment or accounts. It solves the problem of dependency on external APIs by providing a controlled testing environment with predictable responses, status codes, and latencies. The tool includes a desktop application for local mock servers, a CLI for headless environments, and a cloud option for team collaboration.
Developers and teams building applications that integrate with third-party APIs, especially those needing to test API integrations, simulate edge cases, or onboard new team members with consistent environments.
Developers choose Mockoon because it is the easiest and quickest way to set up mock APIs locally, with no account required and full control over route definitions. Its open-source nature, combined with desktop, CLI, and cloud options, offers flexibility for both individual and collaborative workflows.
Mockoon is the easiest and quickest way to run mock APIs locally. No remote deployment, no account required, open source.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
No account or remote deployment required, enabling quick setup and local mock servers as highlighted in the README's philosophy.
Offers a desktop app for GUI design, a CLI for headless environments like CI/CD, and serverless packages, providing versatility across development stages.
Supports importing and exporting OpenAPI specifications, allowing seamless integration with existing API design and documentation workflows.
Includes JSON templating, request recording, HTTPS support, and proxy forwarding, enabling realistic and controlled testing scenarios.
Advanced features like real-time team synchronization and cloud deployments require a Mockoon Cloud subscription, limiting free users to local-only work.
The full graphical interface is tied to the desktop application, which may not suit teams preferring web-based or code-centric workflows.
Using the CLI or serverless packages involves npm installation and configuration, which can be more complex than simpler mocking tools or services.