Realistic, ready-to-use JSON for users, e-commerce, API responses, maps, messaging and config files. Copy one, download it, or open it straight in the Formatter or Tree Viewer.
36 examples · 6 categories
Users & Auth
Accounts, sign-in responses, roles and settings - the objects nearly every app starts with.
user-profile.json22 lines · 542 B
User profile
A typical account object with nested address, preferences and timestamps.
A security event recording who did what, from where, and what changed.
{"eventId":"evt_20260920_000173","action":"user.role.updated","actor":{"id":"usr_admin01","type":"user"},"target":{"id":"usr_1d0b77","type":"user"},"changes":{"roles":{"from":["viewer"],"to":["editor"]}},"ip":"203.0.113.24","userAgent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 14_5)","occurredAt":"2026-09-20T14:05:37.412Z"}
E-commerce
Products, carts, orders and payments, including money amounts and variant options.
product.json22 lines · 403 B
Product
A catalog item with price in minor units, images, ratings and stock status.
An error in the RFC 9457 "problem details" format used by many HTTP APIs.
{"type":"https://api.example.com/problems/insufficient-funds","title":"Insufficient funds","status":402,"detail":"Your balance is 30.00 but the transfer requires 50.00.","instance":"/transfers/trf_7781","balance":3000,"required":5000}
validation-errors.json22 lines · 453 B
Validation errors
Field-level errors returned when a submitted form or request body is invalid.
{"status":422,"message":"The request body failed validation.","errors":[{"field":"email","code":"invalid_format","message":"Must be a valid email address."},{"field":"password","code":"too_short","message":"Must be at least 12 characters.","min":12},{"field":"birthDate","code":"required","message":"This field is required."}]}
cursor-pagination.json18 lines · 282 B
Cursor-based pagination
Pagination with opaque cursors instead of page numbers - stable for changing data.
A service status report with per-dependency checks and latency.
{"status":"degraded","version":"3.14.2","uptimeSeconds":864215,"checks":{"database":{"status":"ok","latencyMs":4},"cache":{"status":"ok","latencyMs":1},"emailProvider":{"status":"failing","error":"timeout after 5000ms"}},"checkedAt":"2026-09-21T08:05:00Z"}
Geo & Maps
GeoJSON features and location data. Note that GeoJSON coordinates are [longitude, latitude].
geojson-point.json14 lines · 214 B
GeoJSON Point
A single location as a GeoJSON Feature with properties.
Posts, threads, notifications and messages - deeply nested, relationship-heavy data.
post-with-comments.json35 lines · 624 B
Post with comments
A post, its author, reaction counts and a nested list of comments.
{"id":"post_5521","author":{"id":"usr_1d0b77","handle":"@trivera"},"text":"Finally shipped dark mode 🌙","media":[],"reactions":{"like":128,"celebrate":31},"comments":[{"id":"cmt_1","author":"@mchen","text":"Looks great!","likes":4},{"id":"cmt_2","author":"@abello","text":"Contrast is perfect.","likes":2,"replies":[{"id":"cmt_3","author":"@trivera","text":"Thanks!"}]}],"createdAt":"2026-09-19T21:14:00Z"}
chat-thread.json32 lines · 615 B
Chat conversation
A direct-message thread with participants, read receipts and an attachment.
{"conversationId":"conv_88a","participants":["usr_8f3a2c","usr_c29e41"],"messages":[{"id":"m1","from":"usr_8f3a2c","text":"Can you review the spec?","sentAt":"2026-09-21T09:00:00Z","readBy":["usr_c29e41"]},{"id":"m2","from":"usr_c29e41","text":"Sure - notes attached.","sentAt":"2026-09-21T09:07:30Z","attachments":[{"name":"review.pdf","sizeBytes":184320,"mimeType":"application/pdf"}],"readBy":[]}]}
notifications.json29 lines · 535 B
Notification feed
Mixed notification types sharing a common shape, plus an unread count.
An email represented as JSON: headers, recipients, body parts and attachments.
{"messageId":"<20260921.1432@mail.example.com>","from":{"name":"Billing","address":"billing@example.com"},"to":[{"name":"Maya Chen","address":"maya.chen@example.com"}],"cc":[],"subject":"Your September invoice","body":{"text":"Hi Maya, your invoice is attached.","html":"<p>Hi Maya, your invoice is attached.</p>"},"attachments":[{"filename":"invoice-2026-09.pdf","sizeBytes":52110}],"labels":["inbox","finance"]}
event-invite.json17 lines · 337 B
Event with RSVPs
A calendar-style event with location, time zone and attendee responses.
Code-editor preferences, including language-specific overrides.
{"editor.fontSize":14,"editor.tabSize":2,"editor.formatOnSave":true,"files.trimTrailingWhitespace":true,"[json]":{"editor.defaultFormatter":"vscode.json-language-features"},"workbench.colorTheme":"Default Dark Modern"}
feature-flags.json23 lines · 373 B
Feature flags
Flags with rollout percentages and targeting rules per environment.
Yes. Every example on this page was written for JSONEdit and uses fictional data, so you can copy them into tests, mocks, documentation or demos.
Why are prices written as whole numbers like 1800?
Many payment and commerce APIs store money in the smallest currency unit (cents) to avoid floating-point rounding errors. 1800 means 18.00 in the given currency.
Why do GeoJSON coordinates put longitude first?
The GeoJSON standard orders positions as [longitude, latitude]. Many other formats use latitude first, so mixing them up is a common cause of points appearing in the wrong place on a map.
Should dates in JSON be strings or numbers?
JSON has no date type. ISO 8601 strings such as "2026-09-21T08:00:12Z" are the most common choice because they are readable and sort correctly; Unix timestamps (numbers) are also used, especially in tokens.
How do I check that my own JSON is valid?
Open it in the JSON Formatter: it validates as you type, shows the parser error message, and can beautify or minify the result. To check structure as well as syntax, use the JSON Schema Validator.
What is the difference between null and a missing key?
A key set to null says "this field exists but has no value"; a missing key says nothing about it. APIs often use null to clear a value in an update, while omitting the key leaves it unchanged.