MockJet — Create Fake REST APIs Instantly, No Backend Needed
Spin up live HTTPS mock endpoints in seconds. Set any status code, latency, or response body — no backend, no installs, no waiting.
No credit card. No setup. Works in under 60 seconds.
Build Mock APIs from Your
AI Assistant
Connect Claude, Codex, Cursor or VS Code once with one URL. Describe the API you need — your assistant creates endpoints, responses, and error cases live in your MockJet project.
-
One URL to connect Add
https://mockjet.io/mcpto any MCP client — no API keys, no install. -
Sign in with OAuth, no API keys Approve access in your browser once. Disconnect any time from your dashboard.
-
Same rules as the dashboard Plan limits, team roles, and request logs all apply. The assistant cannot delete anything.
mockjet.io/m/7c1f…/login. Returns a token by default and 401 when the password is wrong.
Backend not ready?
You shouldn't be blocked.
Frontend and mobile teams waste days waiting for APIs that aren't ready. Every existing mock API solution is either too complex to set up or too limited to be useful.
Waiting on the backend team
Feature development stalls because the mock API endpoints you need aren't ready yet. Sprint velocity tanks while you wait for a backend that may ship weeks later.
Local mock servers are fragile
json-server, hardcoded JSON files, and if-statements in your fetch logic are messy. They only work on your machine, break on merge, and can't simulate real network latency or errors.
Enterprise API mocking tools are overkill
WireMock requires a JVM. Mockoon requires a desktop install. Postman mock servers are buried behind a paid plan. All of this for a fake REST API that should take 60 seconds to create.
The mock API server for
every developer who can't wait
MockJet is used by frontend developers, QA engineers, mobile teams, and full-stack teams who need a fake REST API running now — not after the backend ships.
Frontend developers
Build React, Vue, or Angular components against a real live HTTPS endpoint before the backend exists. No more hardcoded JSON or conditional fetch logic — swap the mock URL for the real one when it's ready.
QA & test engineers
Simulate every edge case your real API won't reliably produce — 429s, 503s, slow responses, empty arrays, malformed JSON — on demand, every time, without touching a staging environment.
Mobile developers
Develop iOS and Android apps against stable mock API endpoints. Share URLs across the team without running a local server or opening ngrok tunnels. Works from any device on any network.
CI/CD pipelines
Point integration tests at a MockJet endpoint to decouple your pipeline from flaky third-party APIs or unstable staging environments. Consistent responses, zero setup, always available.
Designers & prototypers
Wire real data into Figma prototypes, demos, and client presentations. Create a fake API endpoint in under a minute and show stakeholders a working product — no engineer required.
Full-stack teams
Agree on an API contract upfront, publish it as a mock server, and let frontend and backend build in parallel. No more blocked sprints, no more "waiting for the backend" stories in your backlog.
How MockJet Works: Four Steps to a Live Mock API
No CLI, no config files, no Docker. Just your browser.
Create a project
Sign in with Google and create a project. You get a unique base URL instantly.
Add endpoints
Choose the HTTP method, path, and set up one or more response variants.
Configure responses
Set status codes, headers, body JSON, delays, and simulate timeouts.
Hit the URL
Point your app at the mock URL. Watch live request logs stream in real-time.
Prefer to stay in your editor? Connect your AI assistant and describe the endpoints instead.
Everything a mock API server
should do, nothing it shouldn't
MockJet packs every feature a real mock API server needs — response modes, latency simulation, live logs, Postman and OpenAPI import/export, and an MCP server for AI assistants — with zero configuration overhead.
Instant mock API endpoints
Create fake REST API endpoints in seconds — any HTTP method, path, status code, and JSON body. Your live HTTPS mock URL is ready the moment you save.
Response modes
Static always returns the same response. Sequential rotates through a list. Random picks one unpredictably — simulate real-world variance.
Latency & timeout simulation
Add a custom delay in milliseconds to any mock response. Enable timeout mode to return a 504 and test how your app handles slow or failing APIs — no real slow API needed.
Request logs
See every incoming request in real-time. Method, headers, body, IP, and which response was returned. Debug without guessing.
Postman import & export
Import an existing Postman Collection v2.1 to scaffold your project in one click. Export back to Postman anytime.
OpenAPI & Swagger import & export
Import any OpenAPI 3.0/3.1 or Swagger 2.0 spec — JSON or YAML — and MockJet scaffolds every endpoint, with response bodies taken from your examples or generated from your schemas. Export back out as openapi.json or openapi.yaml for Swagger UI, a client generator, or your API gateway.
MCP server for AI assistants
Connect Claude Code, Claude, Codex, Cursor, or VS Code to MockJet's remote MCP server and just describe the API you need. Your assistant creates the endpoints, conditional responses, and error cases, and reads request logs, all live in seconds. Secure OAuth sign-in, no API keys. Set up the MCP server →
Team collaboration
Invite teammates as editors or viewers. Share projects without sharing credentials. Role-based access control built in.
Custom headers
Set any response headers per response — Content-Type, Authorization, CORS headers, rate-limit headers, anything your client expects.
curl command export
Copy a ready-to-run curl command for any endpoint, including request body example and correct headers. Perfect for sharing with teammates.
Path parameters
Define routes with named parameters like /users/:id. MockJet matches them all and routes to the right mock.
Conditional response routing
Return different responses based on what's in the request. Match on body fields, headers, or query params using rules like body.role eq admin or header.Authorization not_exists. Test auth flows, validation errors, and edge cases — no backend code needed.
Dynamic response templating
Every response body can contain live template variables that resolve fresh on each request — {{uuid}}, {{randomEmail}}, {{randomInt(1,999)}}, {{timestamp}}, and more. Realistic random data, zero effort.
Webhook inspector
Get a unique HTTPS URL, send any HTTP request to it, and watch it arrive instantly. Full headers, body, IP, and geo-location streamed live. History persists in your browser — never lose a request. Configure the exact response the URL returns to the sender. A free webhook.site and RequestBin alternative.
MockJet in Practice: Your Mock API, Your Way
Point any HTTP client at your MockJet URL. Here's what that looks like.
Simple, honest pricing
Start free. Upgrade when you need more. Cancel anytime.
- 2 projects
- 3 endpoints per project
- 2 responses per endpoint
- 100 requests / day
- 1 day log retention
- 1 team member
- 5 projects
- 10 endpoints per project
- 10 responses per endpoint
- 500 requests / day
- 3 days log retention
- 5 team members
- 5 webhooks
- Unlimited projects
- Unlimited endpoints
- Unlimited responses
- Unlimited requests / day
- 7 days log retention
- Unlimited team members
- Unlimited webhooks
MockJet FAQ — Frequently Asked Questions
Yes — this is called conditional response routing. You attach match rules to any response. A rule has three parts: where to look (body, header, or query), what field to check, and which operator to use.
Available operators: eq, neq, contains, not_contains, regex, exists, not_exists.
Examples:
- Return HTTP 401 when
header.Authorizationnot_exists - Return admin data when
body.roleeqadmin - Return HTTP 422 when
body.emailnot_exists - Return an empty list when
query.filtereqnone
Rules are evaluated in sort order — the first response whose rules all pass is returned. Responses with no rules are catch-alls, handled by the endpoint's fixed/random/sequential mode. No code, no backend.
MockJet supports dynamic response templating. Place {{variable}} tokens anywhere in your response body — they resolve to fresh values on every request.
Available tokens:
{{uuid}}— UUID v4{{timestamp}}— ISO 8601 UTC timestamp{{timestamp_ms}}— Unix milliseconds{{randomBool}}— true or false{{randomInt(1,1000)}}— integer in range{{randomFloat(0.5,99.9,2)}}— decimal with precision{{randomName}}— full name{{randomEmail}}— email address{{randomPhone}}— phone number{{randomItem(pending,processing,complete)}}— pick from list
Example: {"id":"{{uuid}}","name":"{{randomName}}","created":"{{timestamp}}"} returns unique realistic data on every hit.
MockJet gives you two approaches:
1. Conditional routing — add a rule to any response so the error only fires when the request matches. For example: return HTTP 401 when header.Authorization not_exists, return HTTP 429 when body.qty regex ^[5-9]\d{2,}, or return HTTP 500 for a specific endpoint path. This lets you test your error-handling UI against a real HTTPS endpoint with no backend.
2. Static error response — just create a response with status code 400, 401, 403, 404, 422, 429, 500, 502, or 503 and set it as the active response. Switch between happy-path and error-path with one click in the dashboard.
You can also enable timeout mode to make the endpoint hang for a configurable delay and then return a 504 Gateway Timeout — useful for testing loading states and request cancellation.
Yes. Using conditional response routing, you can make a single endpoint behave exactly like an auth-aware API. A common setup looks like this:
- Response 1 — 401 Unauthorized: rule
header.Authorization not_exists - Response 2 — 403 Forbidden: rule
body.role eq viewer - Response 3 — 200 Admin data: rule
body.role eq admin - Response 4 — 200 Default: no rules (catch-all)
MockJet evaluates rules in sort order — the first match wins. Your frontend team can test the full auth flow — missing token, insufficient permissions, valid admin token — against a live HTTPS URL from day one. No backend, no token issuance, no staging environment.
Yes. MockJet includes a built-in webhook inspector. You get a unique HTTPS URL that accepts any HTTP request from any sender. Open the inspector page and incoming requests stream in real-time — showing the full method, path, headers, body, sender IP address, and geo-location (country, city, ISP).
Request history is persisted in your browser's localStorage so you never lose it on page reload. You can:
- Copy any incoming request as a curl command
- Add notes to individual requests
- Filter by method, IP, path, or body content
- Configure the response the URL returns to the caller (status code, JSON body, delay)
No install, no linking required — just create a webhook, copy the URL, and start sending requests.
Yes. Like webhook.site and RequestBin, MockJet gives you a unique HTTPS URL that captures any incoming HTTP webhook request and displays full headers, body, method, and sender IP in real-time.
MockJet adds on top:
- Live SSE streaming — requests appear instantly, no polling or page reload
- localStorage history — survives navigation; requests buffered in DB while your browser is closed
- Multi-tab sync — all open tabs update simultaneously via BroadcastChannel
- Geo-IP lookup — country, city, and ISP for every request
- Configurable response — set the status code, JSON body, and delay returned to the sender
All features are available on the free plan with no install required.