Scenario
A webhook payload contains a field that looks like keyboard mash — } "ko" : "sutats" ... — while the rest of the payload parses fine. Before you file it as corruption or garbage data, notice the shape: balanced braces on the wrong ends, quoted fragments, colons. That is what JSON looks like after a buggy string-manipulation step reverses it character by character. Reversal bugs are cheap to check and surprisingly common around string builders and log pipelines.
Broken input
} "ko" : "sutats" ,"321-cba" : "di" {
Goal
Use Reverse Text to flip the suspicious string and see whether recognizable structure appears. A one-second reverse either recovers the data or rules out the theory — both outcomes move the debugging forward.
Tool sequence
- Open Reverse Text.
- Paste the garbled field exactly as received — trimming "stray" punctuation first destroys the very characters that reverse into valid JSON syntax.
- Reverse by character and scan the output for structure.
- The result reads
{ "id" : "abc-123", "status" : "ok" }— an ordinary JSON object; the field was reversed, not corrupted. - Confirm the recovered text actually parses by running it through JSON Validator before anyone consumes it.
Checkpoint output
} "ko" : "sutats" ,"321-cba" : "di" {
→ { "id" : "abc-123", "status" : "ok" }
The reversed string is a valid-looking JSON object with id and status fields — evidence of a reversal bug upstream, not data loss.
Common mistakes
- Cleaning punctuation before reversing and destroying the evidence.
- Assuming reversed text is encrypted or encoded when the character set is plainly readable.
- Trusting the recovered result without validating its syntax — a reversal can still hide a second defect.
- Fixing the one reversed field without finding the string operation that reversed it.
Related tools and lessons
- Case Converter - Convert text between cases instantly.
- ASCII / Unicode Explorer - Inspect characters, code points, bytes, and escapes.
- Word Frequency Counter - Analyze word frequency in any text.
- Related lesson: Normalize API Field Names Before Mapping JSON
- Related lesson: Find the Character That Broke a Copy-Paste Flow