>_devtools

JSON Pointer Tester

Resolve RFC 6901 JSON Pointers and URI fragments, see each step, and browse every pointer in a document.

What this does

A JSON Pointer (RFC 6901) is a string that identifies one value inside a JSON document. Type a pointer and the tool resolves it, shows the value, lists each step it took, and prints the pointer in its URI fragment form. The panel below the editors lists every pointer in your document: click one to try it.

Pointer forms

  • (empty string) — The whole document
  • /store/book/0/title — Object keys and array indexes, separated by /
  • /a~1b — A key that contains a slash (~1 stands for /)
  • /m~0n — A key that contains a tilde (~0 stands for ~)
  • #/store/book/0 — The URI fragment form, as used in $ref values
  • #/a~1b/%20 — In a fragment, other characters are percent-encoded

Why a pointer fails

When a pointer does not resolve, the message says where it stopped: a property that does not exist, an array index out of range, an index written with leading zeros (01 is not valid), the special- token that refers to the position after the last array element, or an attempt to read inside a string or number.

Where pointers are used

JSON Pointers appear in JSON Schema $ref values, in JSON Patch (RFC 6902) paths, in OpenAPI references, and in error reports from validators. Unlike JSONPath, a pointer always identifies at most one value, which makes it suitable as a stable address.

Privacy

Pointers are resolved in your browser. Your JSON is never uploaded or stored.