OpenAPI Mock
github.com
- Free plan
- Windows
- Linux
- Self-hosted
What OpenAPI Mock is
OpenAPI Mock is a free, open-source API mock server that generates random response data from OpenAPI schemas or examples. It supports OpenAPI 3.x specifications in JSON and YAML, loaded from a local file or URL. Response strategy settings can ignore examples, use them when present, or use them exclusively. Content negotiation uses the Accept header. JSON responses are supported, while XML generation is basic and omits XML tags. The server runs as a standalone application on Linux or Windows, or in Docker, with Docker Compose usage documented. Configuration is available through command-line options, environment variables, or YAML and JSON files. A validate command can check whether a specification is handled, including in continuous integration, but reports only critical errors without details. Local references work; remote and URL references do not. Request-data validation and forcing a custom response schema are unsupported. Combined types work except for the not tag and discriminator.
Who it suits
OpenAPI Mock suits developers and teams needing HTTP mock responses from OpenAPI 3.x definitions. Its Linux, Windows, self-hosted, Docker, and CI options support local development and automated workflows.
Good to know, and what to watch
- Free and open source under the MIT License
- Supports OpenAPI 3.x JSON and YAML
- Runs on Linux, Windows, or Docker
- Configurable schema and example response strategies
- Command-line, environment, YAML, and JSON configuration
- Remote and URL references are unsupported
- Request-data validation is unsupported
- XML output lacks XML tags
- Validation reports critical errors without details
The verdict
OpenAPI Mock provides a focused way to generate HTTP responses from OpenAPI definitions, with flexible deployment and configuration. Check its reference, validation, XML, and custom-schema limits against your mock-server needs.
What the maker publishes
- CI use
- The documentation describes a validate command that can check whether a specification can be handled by the application, including for Continuous Integration. source
- CI use
- The usage guide says its specification validation command can be useful for Continuous Integration, but reports only critical errors without details. source
- Configuration
- Settings can be supplied through command-line options, environment variables, or YAML and JSON configuration files. source
- Configuration
- The server can be configured through command-line options, environment variables, or YAML and JSON configuration files. source
- Container integration
- The project documents use with Docker and Docker Compose. source
- Content negotiation
- The server supports content negotiation using the Accept header. source
- Deployment
- The project can run as a standalone application on Linux or Windows, or in a Docker container; it also documents Docker Compose usage. source
- Deployment
- The README says it can run as a standalone application on Linux or Windows, or in a Docker container. source
- License
- The project is licensed under the MIT License. source
- License
- The repository states that the project is licensed under the MIT License. source
- Maker identity
- The repository is published under the GitHub account muonsoft; the repository page does not state a headquarters or founding date. source
- OpenAPI support
- The project states that it supports OpenAPI 3.x specifications in JSON and YAML formats. source
- OpenAPI support
- The project supports OpenAPI 3.x specifications. source
- Purpose
- OpenAPI Mock is an API mock server that generates random response data from specified schemas. source
- Purpose
- OpenAPI Mock is an API mock server that generates random response data from specified schemas. source
- Reference limits
- Remote and URL reference resolving, request-data validation, and forcing a custom response schema are listed as unsupported. source
- Reference support
- Local references are supported, but remote and URL references are not supported. source
- Request validation
- Validating request data is listed as unsupported. source
- Response formats
- JSON responses are supported, while XML response generation has basic support without XML tags. source
- Response formats
- JSON response generation is supported, while XML generation has basic support without XML tags. source
- Response generation
- Mock responses can be generated from schemas or examples, and the configured strategy can ignore examples, use them when present, or use them exclusively. source
- Response generation
- Mock responses can be generated from schemas or examples, with content negotiation based on the Accept header. source
- Schema limits
- Combined types are supported except for the not tag and discriminator, and the application detects response schemas automatically rather than accepting a forced custom response schema. source
- Specification input
- The server can load a specification from a local file or a URL. source
Checked against the maker's pages on 3 Oct 2026.