DiagramPreview
Analisador básicoSem IAPrévia localExportarDepuração

Testador JSONPath

Cole conteúdo para Testador JSONPath e gere uma prévia local revisável para depurar configurações, respostas de API, arquivos de SEO e snippets gerados por AI.

Exemplos
Matched valuesPronto
Your JSONPath matches will appear here.

Continue com uma ferramenta relacionada

Leve esta prévia para um fluxo próximo para converter, depurar ou exportar.

SQL to ER Diagram

Convert CREATE TABLE SQL into a Mermaid ER diagram.

Abrir
JSON Schema Visualizer

Inspect JSON Schema properties, types, required fields, and composition groups.

Abrir
Prévia de formulário JSON Schema

Prévia de formulário JSON Schema: Pré-visualize e depure esta fonte em uma superfície local para documentação técnica.

Abrir

Como usar

  1. 1Paste a representative JSON payload and keep the first line as the JSONPath expression.
  2. 2Use samples such as email extraction, first order total, or recursive duration to learn the expected input shape.
  3. 3Check match count, first match, and result rows before copying the expression into tests or documentation.
  4. 4If the result is empty, simplify the expression one segment at a time until the path starts matching again.

Casos de uso

API response debuggingWebhook payload reviewTest assertion designAI JSON output validationNested array inspection

FAQ

Why does my JSONPath return no matches?

The most common causes are a missing root selector, an array segment that needs [*], a field name typo, or a payload shape that differs from the example used to write the expression.

How do I debug a complex JSONPath expression?

Start with $ or a known top-level field, then add one segment at a time. Confirm the match count after each step before adding filters or recursive selectors.

Is this a replacement for a production JSONPath library?

No. Use it as a preview and review surface, then verify final behavior with the same JSONPath library used by your application or tests.

JSONPath Tester helps you inspect API responses, fixture files, webhook payloads, and AI-generated JSON without writing a temporary script.

The preview highlights matched values, result shape, and a match table so you can confirm whether an expression is selecting the field you expected.

It is especially useful for test assertions, monitoring payload checks, documentation examples, and debugging nested arrays where a wrong wildcard silently returns too much or nothing.

Demo: extract user emails from a nested API response

A practical JSONPath review starts with a payload that looks like production but removes sensitive values. The tester should show both the matched values and the path shape so you can turn the expression into a test assertion.

  • Use $..email when email fields can appear at different depths.
  • Use $.users[*].email when the schema is stable and you want stricter matching.
  • Prefer strict paths for tests and recursive paths for exploration.
$.users[*].email
{
  "users": [
    {"id": 1, "email": "ada@example.com"},
    {"id": 2, "email": "grace@example.com"}
  ]
}

The first line is the expression; the rest is the JSON payload to inspect.

JSONPath mistakes worth catching before code review

A JSONPath expression can look correct while selecting the wrong level of a nested payload. Previewing the result makes these mistakes visible before they become flaky tests or broken docs.

  • Recursive selectors can match fields from unrelated objects.
  • Array indexes such as [0] are fragile when examples do not represent production order.
  • Filters should be checked against payloads with both matching and non-matching records.

Checklist de revisão para Testador JSONPath

Use Testador JSONPath para inspecionar visualmente conteúdo de origem antes de publicar documentação, notas de PR, incidentes ou handoffs. Testador JSONPath: Pré-visualize e depure esta fonte em uma superfície local para documentação técnica.

Antes de exportar, confira legibilidade, relações, dados sensíveis e se a prévia ainda faz sentido após editar a entrada.

Limites e solução de problemas

Se a prévia falhar, reduza a entrada ao menor exemplo completo, valide a sintaxe e adicione as partes de volta aos poucos.

Trate a prévia como superfície de revisão, não como fonte de verdade. Resultados críticos ainda exigem validação humana.

Entradas de exemplo

  • User emails: $.users[*].email --- { "users": [ {"id": 1, "email": "ada@example.com", "role": "admin"}, {"id": 2, "email": "lin@example.com", "role": "viewer"} ] }
  • First order total: $.orders[0].total --- { "orders": [ {"id": "ord_1", "total": 49.9}, {"id": "ord_2", "total": 19.5} ] }
  • Recursive duration: $..durationMs --- { "trace": { "durationMs": 340, "spans": [{"name": "api", "durationMs": 120}, {"name": "db", "durationMs": 180}] } }

Maturidade da ferramenta

Analisador básico

Analisador básico

Esta ferramenta prioriza inspeção rápida de estrutura. Use para revisão e depuração, depois valide resultados críticos.

O rótulo indica se a ferramenta é melhor para exportação estável, depuração, análise rápida ou geração com AI.