Mock Server

In almost every project the frontend depends on the backend, and the backend is rarely finished on time. Instead of waiting idly, you simply mock the API. The Mock Server does exactly that without your own server setup: you describe an endpoint - path, method, status code, response headers and response body - and it answers just as you specified.

A mock endpoint is made of a few details. The path sets the address, the method (GET, POST, PUT, PATCH or DELETE) the verb, the status code the outcome - from 200 OK through 404 Not Found to 500 Internal Server Error. You set the response headers freely, for example Content-Type or custom fields, and in the response body you store the answer, typically as JSON.

The adjustable delay is especially useful. Real APIs do not answer in zero milliseconds, and your loading state, your spinners and your timeouts want testing. With an artificial delay you simulate slow connections and see whether your UI still reacts cleanly when a response takes its time.

Every endpoint you define can be tested directly in the tool. You get the simulated response back with status, headers, body and the actual response time - exactly as it would arrive at your code later. The request logging shows which calls came in, so you can verify that your integration really hits the endpoint.

The typical flow: you model the planned API with a few mock endpoints, wire your frontend against them and later replace the mocks with the real interface once it exists. That decouples frontend and backend development so you do not block each other.

The Mock Server plays well with the API Playground: there you call your mock endpoints and inspect the response in detail, just as if it were a real API. Together they form a small, browser-based bench for everything to do with HTTP interfaces - no Docker, no local Node process, no installation.