Sharing & Scaling

Request Inspector

Every request to your mock shows up live in the Request Inspector — no refreshing, no polling. It's a WebSocket stream, so a request appears the moment it happens.

What you see per request

  • Method and path
  • Status code returned
  • Latency
  • Headers and body of what was sent, and the body of what was sent back
  • The calling client's IP address

Sensitive headers — Authorization, X-Mock-Token, Cookie, Proxy-Authorization — are shown as [redacted] rather than their real value, so a captured request never leaks a token or session cookie into the inspector, even one you're actively testing. A very large body is truncated with a preview rather than shown in full. A binary response logs a byte count instead of the raw file, since dumping binary data into the log wouldn't be readable anyway.

Filtering the list

Once a few requests have come in, a filter row appears above the list: a text box to match against the path, a method dropdown, and a status dropdown grouped by class (2xx, 3xx, 4xx, 5xx). All three combine — narrowing by path and status at once, for example, finds only the failed calls to one specific route.

Filtering only changes what's displayed. It doesn't delete anything or affect what the inspector captures, so clearing a filter always brings the rest of the list back.

How much history you get

The inspector keeps the last 500 requests per mock, for 7 days, whichever comes first. It's for confirming what just happened and picking up where you left off after a weekend — not a permanent audit log. Deleting a mock clears its history immediately.

Why it matters

It's the fastest way to confirm your app is actually calling the endpoint you think it is, with the payload you think it's sending — especially useful right after wiring up a new integration, or when a response isn't what you expected and you need to see the exact request that produced it, and exactly what your mock sent back.

It's also the quickest way to diagnose an unexpected 404: compare what the inspector shows was actually sent against the route's match conditions. A condition that doesn't match is by far the most common reason a route you're sure exists doesn't answer.