API Mock Server
Mock REST API routes with rules, delays, scenarios and a temporary public endpoint
Related Tools
What the API Mock Server does
Define routes with several responses, pick how a response is chosen (fixed, rules, sequence or random), add delays and failure statuses, and test everything in the browser. When public endpoints are enabled, you can start a temporary URL that serves the same routes to any client and shows a live request log.
Matching and precedence
Paths support literal segments, :params and a trailing * wildcard. The most specific route wins, so /users/me beats /users/:id regardless of creation order. Rules inspect the method, path parameters, query, headers, the raw or JSON body, the request count and scenario state.
Privacy and limits
The editor and Test request run in your browser. A started endpoint stores the config and the last 100 requests on CodingTool servers for at most 60 minutes, or 15 minutes without requests, and deletes them when you stop it. Cookies are never read or stored, and credential header values such as Authorization and API keys are masked before storage.
What it does not do
It never forwards requests to real APIs, never redirects, never sets cookies and never runs code. Only JSON and plain text are served, always inline and with a sandbox policy; other content types are served as plain text, and only custom X- headers and a few caching and rate-limit headers can be set.
