Test a JSON change from a bookmark

Preview a patch against a saved response, then check whether the next request actually received it.

Try the empty-description state

Suppose the app needs to display a fallback when a movie description is empty. Bookmark a read-only request to your test catalog whose response has a nested movie.shortDescription field. Unlike a live rewrite, a bookmark rewrite starts from the saved response: unrelated fields do not update from the backend on each retry.

  1. In Bookmarks, select the exact endpoint the app calls. Open Saved Response JSON, find the description, and use Add Field Rewrite on that field to start with its actual path.
  2. Set the value to an empty string. Turn on Preview Patches. A green check means the path exists in the saved response; a warning means the patch would be skipped. Neither means the app has received anything.
  3. Start the proxy, choose Enable for Session, then refresh in the target app. Find the new request in Table. Check its rewrite source and returned field, then check whether the app displayed the fallback.

No change? Compare the actual path with the bookmark, and check session enablement if you restarted the proxy. Once finished, disable the rewrite and refresh again to verify the ordinary response. To alter one field while keeping the rest of a fresh upstream response instead, see live overrides.