Format, minify, validate, inspect, and copy a safe API response report for JSON payloads without sending them to a server.
Input / Output
Input, output, and copy actions stay in this main surface. Examples and reference checks are separated below.
Local session
Input state is saved only in this browser so you can restore the last workspace without an account.
Open examples, checks, and related tools only after the primary input/output flow is done.
Extract a JSON field
Format the payload, test a path with wildcards or recursive keys, then keep the shape for code.
Format and validate the pasted response before selecting fields.
Test dot paths, bracket keys, wildcards, and recursive key searches.
Create a starter type once the field shape is clear.
Format an API response
Clean a pasted JSON payload, inspect paths, then create types or schema checks.
Validate and format the payload, then copy a compact API response report.
Pull the exact field path needed by code or docs.
Turn the sample shape into a starter interface.
Verify a webhook signature
Generate the HMAC output, copy a safe signature report, and inspect payload shape or encoding before changing webhook code.
Before copying
Common failure cases
Related tools
Guides
Open examples, checks, and related tools only after the primary input/output flow is done.
{"status":"ok","items":[1,2,3]}{"user":{"id":123,"roles":["admin"]},"active":true}[{"id":1,"name":"Bob"},{"id":2,"name":"Alice"}]JSON examples
Root type
object
Top-level items
2
Nested depth
4
Output lines
9
JSON diagnostics
Review sensitive-looking keys, empty values, duplicate keys, and large arrays before copying or sharing.
Input bytes
85
Sensitive keys
0
Empty values
0
Duplicate keys
0
API response report
Copy a compact handoff report with structure, diagnostics, useful JSON paths, and safe sharing checks.
Root type
object
Top-level items
2
Nested depth
4
Output lines
9
Sensitive keys
0
Duplicate keys
0
Safe handoff checklist
# API response report
- Checked at: Browser copy time
- Root type: object
- Top-level items: 2
- Nested depth: 4
- Output lines: 9
- Input bytes: 85
## Review notes
- No obvious JSON structure warnings detected. Still redact production identifiers before sharing.
## Useful JSON paths
- `$` (object) - 2 keys
- `$.status` (string) - "ok"
- `$.items` (array) - 1 items
- `$.items[0]` (object) - 2 keys
- `$.items[0].id` (number) - 1
- `$.items[0].name` (string) - "Bob"
## Safe handoff checklist
- Redact tokens, cookies, customer identifiers, and internal URLs before sharing.
- If the response is invalid, include the exact parse error line and column in the bug report.
- For large or deeply nested responses, share a JSONPath-focused sample instead of the full payload.
- Confirm duplicate keys before trusting downstream parser output.
- Attach a formatted sample only after removing production-only values.JSON structure
Review the root shape before copying the formatted payload.
JSON path preview
Copy common paths before moving into JSONPath or TypeScript generation.
$object2 keys$.statusstring"ok"$.itemsarray1 items$.items[0]object2 keys$.items[0].idnumber1$.items[0].namestring"Bob"Path inspector
Extract one value from the formatted JSON with dot or bracket paths.
Supported: $, .key, [0], and ["key with spaces"].
BobUseful next steps
Copy-ready output
{
"status": "ok",
"items": [
{
"id": 1,
"name": "Bob"
}
]
}