Skip to main content
CuteJSON
↑↓ Navigate Enter Select Esc Close

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.

Back to all tools

Keyboard shortcuts

These work wherever the matching action exists on this page.

Open the command palette
Ctrl/Cmd + K
Run the main action
Ctrl/Cmd + Enter
Format
Ctrl/Cmd + Shift + F
Minify
Ctrl/Cmd + Shift + M
Copy output
Ctrl/Cmd + Shift + C
Open file
Ctrl/Cmd + Shift + O
Download output
Ctrl/Cmd + S
Close this dialog
Esc
Open this dialog
F1 / ?

Local data

Everything below is stored only in this browser, on this device. None of it is ever sent anywhere, and closing this dialog is not required for that to stay true.

Unsaved drafts
Tools with remembered options

Recently opened files

    No files opened yet on this device.

    Share via link

    The content is packed into the part of the link after the # sign, which browsers never send to a server. Nothing here is uploaded to cutejson.com or anywhere else.

    Shares the first input on this page. On a tool with more than one, only that one is included.

    Nothing to share yet. Paste or type something first.

    Input

    Load from a URL

    Fetches the URL directly from your browser and loads whatever text it returns into this pane.

    Paste an API response and press Analyze.

    Runs entirely in your browser. Nothing you paste is uploaded, and you can confirm that in your browser Network tab.

    About this tool

    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.

    How to use

    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.