JSON unique key names

Client

Discover schema-like key sets from sample API payloads before writing pick or rename maps.

Learn more: unique keys

Walks objects and arrays recursively; array indices are not listed as keys.

Local processing

Parsing and output formatting run entirely in your browser—nothing is uploaded for this transform.

Input

?
Paste JSON, then read transformed output below.

Nearby workflows on Toolcore

  • JSON path list — Enumerate leaf paths ($ / dot / brackets); optional RFC 6901 pointers, filter, and stats—local only. once JSON text parses on this page.
  • JSON pick or omit keys — Keep or drop top-level keys on an object or array of objects—case-sensitive; local only. once JSON text parses on this page.
  • JSON rename keys — Map old property names to new—deep rename at every object level; local only. once JSON text parses on this page.
  • JSON statistics — Depth, key counts, object/array totals, and value-type breakdown—local only. once JSON text parses on this page.

Common use cases

  • Discover schema-like key sets from sample API payloads before writing pick or rename maps.

Common mistakes to avoid

  • Invalid JSON

    Fix parse errors before expecting output.

FAQ

Is data uploaded?

No—all parsing and transforms run locally.

How is this different from jq?

This page focuses on one deterministic task without a filter language.

More tools

Related utilities you can open in another tab—mostly client-side.