跳转到主要内容
CuteJSON
↑↓ 导航 Enter 选择 Esc 关闭

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.

返回所有工具

键盘快捷键

这些快捷键在页面上对应操作存在时有效。

打开命令面板
Ctrl/Cmd + K
运行主要操作
Ctrl/Cmd + Enter
格式化
Ctrl/Cmd + Shift + F
压缩
Ctrl/Cmd + Shift + M
复制输出
Ctrl/Cmd + Shift + C
打开文件
Ctrl/Cmd + Shift + O
下载输出
Ctrl/Cmd + S
关闭此对话框
Esc
打开此对话框
F1 / ?

本地数据

以下所有内容仅存储在此浏览器、此设备上。

未保存的草稿
记住选项的工具

最近打开的文件

    此设备上尚未打开任何文件。

    通过链接分享

    内容被打包在链接 # 号之后的部分。

    分享此页面上的第一个输入。

    暂无可分享的内容。

    输入

    从 URL 加载

    直接从浏览器获取 URL。

    Paste an API response and press Analyze.

    完全在您的浏览器中运行。

    关于此工具

    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.

    使用方法

    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.