Everything an OpenAPI mock server should do
Mockzilla generates a mock API from your OpenAPI spec, or serves the JSON files you wrote, and hosts it on a URL your whole team can call. Make it slow, make it fail, proxy the real backend, or give every pull request a mock server of its own.
OpenAPI mock server
Point it at a spec and every path answers. The data comes from your schemas, not from a placeholder.
- Schema-generated responses
- Request validation
- Several APIs, one URL
Hosted mock server
Nothing to run locally. One URL, placed close to the people calling it and stable for as long as you need it.
- One stable URL
- Multi-region hosting
- API key or team only
Latency and error simulation
Make the API slow, make it fail, and find out whether your retry and fallback code actually runs.
- Delay in milliseconds
- Error rate injection
- Per service or per endpoint
API proxy with mock fallback
Forward to the real backend and fall back to the mock for anything it does not serve yet.
- Real and mocked on one URL
- Nothing to change in your app
- Response caching
PR preview environments
A mock server for every pull request, updated on each push and removed when the branch is gone.
- A URL per branch and PR
- GitHub Action
- Cleaned up automatically
Request history and replay
Every call recorded with status and timing. Send any of them again without touching your app.
- Full request history
- Replay one or a set
- Export and import
Fake JSON API
No spec needed. Drop JSON files at the paths you want and get those exact responses back.
- Files become routes
- Your own data
- Mixes with a spec
Bring a spec. Get a mock server.
It costs nothing to start. Dedicated infrastructure when you need it.