Pular para o conteudo principal
CuteJSON
↑↓ Navegar Enter Selecionar Esc Fechar

API Response Analyzer

Paste an API response and see what stands out: nulls, type disagreements, duplicate keys, oversized sections, plus a candidate schema and types.

Voltar para todas as ferramentas

Atalhos de teclado

Estes funcionam onde a acao correspondente existe nesta pagina.

Abrir a paleta de comandos
Ctrl/Cmd + K
Executar a acao principal
Ctrl/Cmd + Enter
Formatar
Ctrl/Cmd + Shift + F
Minimizar
Ctrl/Cmd + Shift + M
Copiar saida
Ctrl/Cmd + Shift + C
Abrir arquivo
Ctrl/Cmd + Shift + O
Baixar saida
Ctrl/Cmd + S
Fechar este dialogo
Esc
Abrir este dialogo
F1 / ?

Dados locais

Tudo abaixo e armazenado apenas neste navegador, neste dispositivo. Nada e enviado a lugar nenhum, e fechar este dialogo nao e necessario para que isso continue verdade.

Rascunhos nao salvos
Ferramentas com opcoes lembradas

Arquivos abertos recentemente

    Nenhum arquivo aberto ainda neste dispositivo.

    Compartilhar via link

    O conteudo e empacotado na parte do link apos o #, que navegadores nunca enviam a um servidor.

    Compartilha a primeira entrada nesta pagina.

    Nada para compartilhar ainda.

    Entrada

    Carregar de uma URL

    Busca a URL diretamente do seu navegador.

    Paste an API response and press Analyze.

    Funciona inteiramente no seu navegador.

    Sobre esta ferramenta

    This composes engines already used elsewhere on the site rather than a second, possibly disagreeing implementation of the same thing: the candidate schema and TypeScript types come from the same inference the Schema Generator and the JSON to TypeScript tool use, and every JSONPath example shown is run against your own document before being suggested, so it is guaranteed to match something. The structural checks are new: a null finding distinguishes a field that was null in every sample from one that was only sometimes null, an inconsistent type finding is a field whose non-null values disagreed in kind across samples, an inconsistent array finding is an array whose elements either disagreed in kind or did not all carry the same keys, a duplicate key finding is an object key repeated in the source text (which a normal parser would silently resolve by keeping the last one), and a large section finding is a container past a byte or item count threshold. Every check is a description of what this one document contains, not a guess about a fourth sample you have not pasted yet.

    Como usar

    1. Paste an API response, or load the sample.
    2. Press Analyze.
    3. Read the sections that found something first: an empty section stayed collapsed on purpose.