Sharing & Scaling

Version History

Every time you save a mock — editing a route, adding one, importing an OpenAPI spec into an existing mock — MockBase quietly saves a snapshot of what it looked like right before that change. Break something, and the Version history panel on the mock's page gets you back.

How it works

There's nothing to turn on. A snapshot (the mock's name and routes) is captured automatically immediately before each save, so the history list holds what the mock looked like right before each edit — not after. The most recent entry in the list is always "one edit ago."

Each entry is compared against the mock's current routes and labeled with what restoring it would actually change: how many routes it would bring back (+), remove (−), or change (~). Expand an entry to see each affected route individually, with a plain-language reason — a status code that would change, a response body, match conditions, or an attached binary file. An entry with no differences is marked as identical to the current state, so you're never guessing what a restore does before you click it.

Click Restore on any entry and the mock's name and routes are replaced with that snapshot. The routes you had a moment ago don't just disappear: restoring saves its own snapshot of what was current first, so a restore shows up as a new entry in the list and can itself be undone the same way any other edit can.

Checkpoints you make on purpose

Automatic snapshots capture the state before each save, which is what you want for undo. Sometimes you want the opposite: a marker for the state as it is right now, before you start a risky stretch of changes.

Save snapshot does that. It captures the mock as it currently stands, immediately, without needing an edit to trigger it. Manual snapshots are marked with a bookmark so they stand out from the automatic ones.

Naming a version

A list of thirty entries all called "Untitled Mock" is not navigable. Click the pencil on any entry to name it — "before the pricing refactor", "last known good" — and that label replaces the mock name in the list. Automatic snapshots start unnamed and can be named after the fact, which is usually when you realize a particular point was worth marking.

Deleting a version

Click the trash icon on an entry to permanently remove it from the list — useful for clearing out snapshots you know you'll never restore, so the ones you actually care about are easier to find. It asks for confirmation first, since this can't be undone the way most other changes here can: a deleted version is gone, not turned into a new entry the way restoring one is.

Deleting a version only removes that snapshot. It doesn't touch the mock's current routes, and doesn't affect any other entry in the list.

What's versioned

Only the name and routes — the things you actually change while editing a mock. Token protection, a claimed subdomain, Record & Replay's target URL, and the default response are managed through their own dedicated controls and aren't part of this history.

Everything inside a route is covered, including its chaos scenarios, rate limit, callout, and any attached binary file — restoring brings back the file's exact bytes, not just its settings.

Limits

History keeps the last 30 versions per mock, for 90 days, whichever comes first — like the Request Inspector, it's a recent-history safety net for catching your own mistakes quickly, not a permanent audit log. Manual snapshots count toward the same 30. Deleting a mock deletes its history along with everything else.

This is free on every mock, not a Pro feature.