webutilities.tools

Rename JSON Keys then Detect Format

Apply key renaming rules and verify the transformed payload remains structured JSON.

Intermediate~3 minjsontransformmigration

Use case

Use this during contract migrations where field names change between versions.

Workflow overview2 steps0 / 2 completed~3 min

What to expect

Follow the steps from left to right for a quick overview, then use the inline stepper below to run each tool.

Apply key renaming rules and verify the transformed payload remains structured JSON.

Current focusStep 1 · JSON Key Renamer
0% complete
Step 1json-tools Waiting

JSON Key Renamer

JSON → JSON

Rename JSON keys

JSON with keys renamed recursively.

Step 2json-tools Waiting

Format Detection Tool

TEXT → JSON

Detect format

JSON report with detected format and parser confidence.

Workflow steps

Run this workflow inline
Work through each tool step here. Running a step automatically prepares the next step with the correct handoff value.

Workflow shortcut

Next unlocked step: Step 1 · JSON Key Renamer

Progress is stored locally in this browser.
1
Step 1Ready to runjson-tools

JSON Key Renamer

Rename one or more keys across JSON objects.

Open full tool

Rename input (JSON envelope)

Provide { "json": <value>, "renames": { "oldKey": "newKey" } }.

Renamed JSON

JSON with keys renamed recursively.

Run this step to process the current input and prepare the next workflow stage.

2
Step 2Lockedjson-tools

Format Detection Tool

Auto-detect whether input is JSON, XML, YAML, CSV, or plain text.

Open full tool
Complete the previous step first
This step unlocks automatically after all earlier workflow steps are completed successfully.

Unknown payload input

Paste payload text to identify likely format and confidence.

Detection report

JSON report with detected format and parser confidence.

Run this step to process the current input and prepare the next workflow stage.