Pro Feature

Stateful Servers

Your mock API actually remembers things. Create a user via POST, fetch it with GET, update it with PUT, delete it with DELETE — and MockRoute keeps track of every change, just like a real backend.

Start Free Trial View Pro Plans

Static mocks aren't enough

Traditional mock servers return the same canned response every time. That's fine for simple GET requests, but it breaks down the moment your frontend makes a POST and expects to see the new data reflected in a subsequent GET.

Stateful Servers solve this. MockRoute maintains an in-memory store for each endpoint. Every write operation (POST, PUT, PATCH, DELETE) mutates the store. Every read (GET) reflects the current state.

POST /api/users → Creates user, stores in memory

GET /api/users/1 → Returns the user you just created

PUT /api/users/1 → Updates name, email in state

DELETE /api/users/1 → Removes from state, 204 response

GET /api/users/1 → 404 — user was deleted!

Key capabilities

In-memory data store

Each endpoint gets its own isolated store. Data persists across requests during your session and can be reset at any time.

Auto-generated IDs

MockRoute auto-assigns UUIDs to created resources. Reference them in subsequent requests just like a real API.

Collection endpoints

GET /resources returns the full list. GET /resources/:id returns a single item. Pagination and filtering included.

Reset anytime

One click to wipe the store and start fresh. Great for running repeatable tests in CI/CD pipelines.

Schema validation

Define a JSON schema for your resource. MockRoute validates incoming POST/PUT bodies and returns 422 on invalid data.

Seed data

Pre-populate your store with fixture data so your app has realistic content to work with from the first request.