Skip to content
Pretty Payload
All guidesWorkflows

Workflows

Trim a JSON Payload Into a Useful Debugging Example

Edit values, remove keys you do not need, undo mistakes, and copy a smaller JSON example for tickets or fixtures - without calling it redaction.

Pretty Payload3 min read

A full webhook body is honest. It is also a terrible attachment for a ticket. You need a smaller example: the fields that reproduce the bug, fictional values where needed, and nothing that confuses the next reader.

Pretty Payload lets you edit values, remove keys, undo, and copy pretty or minified JSON - all as manual editing, not automatic redaction or anonymization. This walkthrough uses the current viewer controls.

Keep the original

Before you trim anything:

  1. Save or leave untouched a copy of the real payload (or a complete fictional reproduction).
  2. Work on a duplicate in the web demo or the Chrome extension.
  3. Remember: removing a key in the viewer does not prove the document is safe to share. You are shaping an example, not running a compliance tool.

Identify necessary fields

Ask what the next person must see. Typical keepers:

  • Request or event id
  • Status or error object
  • The nested field that failed
  • One representative item from an array

Drop telemetry blobs, duplicate debug mirrors, and unused configuration once you have confirmed they are irrelevant to this bug.

Fictional order (starting point):

{
  "request_id": "demo_1042",
  "status": "needs_review",
  "customer": {
    "name": "Example Company",
    "email": "[email protected]"
  },
  "items": [
    { "sku": "DEMO-01", "quantity": 2 }
  ],
  "debug_note": "Sample data only",
  "internal_trace": {
    "token": "sample_token_not_real",
    "verbose": true
  }
}

Suppose the ticket only needs request_id, status, customer.name, and items.

Edit a fictional value

In the viewer:

  • Click the ✎ control on a leaf value (tooltip: Edit this value (or double-click it)), or double-click the value.
  • Change needs_review to failed if that matches the scenario you are documenting.
  • Prefer invented emails and tokens ([email protected], sample_token_not_real) when the example might be shared broadly.

Editing updates the in-memory document you will copy. It does not rewrite the source system.

Remove irrelevant keys

Hover a row and use the ✕ control (tooltip: Remove this key and everything inside it - or Remove this item… inside arrays).

For the sample:

  1. Remove debug_note.
  2. Remove internal_trace (the whole object goes with it).
  3. Optionally remove customer.email if the bug does not involve contact fields.

A toast confirms the removal and reminds you that Undo restores it: Removed "debug_note" - Undo to restore.

Undo a removal

Click Undo in the toolbar (or Ctrl+Z) to reverse the last edit or removal. Undo is there so aggressive trimming stays reversible while you shape the example.

Copy pretty or minified output

  • Copy JSON - pretty-printed text for tickets and docs
  • Copy Minified - single-line JSON for fixtures or chat pastes

Optional: A↓Z sorts keys alphabetically in the view for this document. Sorting changes how you browse; it does not promise sorted key order in the copied output. Copied JSON keeps the document’s key order.

Check the output before sharing

Read the clipboard contents once:

  • Are only the intended fields present?
  • Are values clearly fictional?
  • Does minified vs pretty match the destination?

For a local-first workflow overview, see the free online viewer. If you bounce between paste sites and an extension daily, Chrome extension vs paste sites compares the loops.

A little less payload. A little more clarity. That is the whole trim.

Try it

  1. Paste the sample into prettypayload.com/try/.
  2. Edit status, remove debug_note and internal_trace, hit Undo once to see restore, then remove again.
  3. Copy JSON and paste into your notes.

For clipboard-first debugging, add Pretty Payload to Chrome (10 free opens, then a 30-day email trial with no card).

All guides