Fix the broken JSON

About Payload Patch

Each round shows an input payload, an expected payload, and a list of candidate transformations. Pick the cleanest fix (rename, change type, add/remove field, wrap/unwrap). For real work, see JSON Formatter, JSON Diff, JSON Patch & Pointer, and JSON Schema Validator.

Runs locally in your browser. Progress is stored only in this browser.

What this challenge teaches

Fix the broken JSON is a short drill for JSON payload repair. A payload is close to correct but one transformation is needed: rename a field, apply a JSON Patch, normalize an array, or fix a type mismatch.

Example reasoning path

• Read the prompt and identify the artifact type before looking at the answer choices.
• Compare the expected target with each candidate result and eliminate options that are only formatting changes.
• Check whether the target path exists and whether the change preserves the original data meaning.

After you solve it

Open JSON Patch & Pointer to apply the same skill to your own data. For a broader practice loop, return to Skill Challenges or open Workflow Gallery when the task needs multiple tools.

Challenge state stays local to this browser. Do not paste production secrets into practice prompts.

Practice notes for real projects

Use this page as a warm-up before touching real project data. Read the prompt, write down the signal you are looking for, and only then compare answer choices. That habit carries over to production debugging, where the first visible error is often a symptom rather than the root cause.

After the challenge, recreate the same pattern in the linked tool with a harmless sample. For example, replace real tokens, user identifiers, hostnames, and request bodies with safe values, then verify that the same reasoning still works. This keeps practice useful without exposing private data.

• Save time by checking the smallest artifact that reproduces the issue.
• Write one sentence explaining why the wrong answers fail; that explanation is the skill to reuse later.
• If the challenge involves security, treat decoded or inspected data as untrusted until a separate verification step confirms it.

Quick review prompt

Before replaying the challenge, explain the rule in plain language: what input pattern matters, what output shape is expected, and which mistake would cause the wrong answer. That short explanation makes the drill useful outside the game, because it turns a one-click answer into a reusable debugging checklist for code review, QA notes, and incident follow-up.