Skip to the tool
GigaJSON Sample API Responses
All tools
Format and check
View and query
Convert
JSON to code
Encode and decode
Sample files
Guides Open GigaJSON

Sample JSON API responses, in every common shape

Pick a resource, a shape and a size. You get the JSON a real API would send: pages, cursors, JSON:API, HAL, GraphQL or an error, made on your device.

Example JSON responses the way real APIs send them, for mocks, tests and documentation. Pick a resource (users, posts, comments, products, orders, todos, invoices, files, notifications or events), a shape and a size from 1 KB to 1 MB. The same records come as one object, a plain list, a page with links, a cursor page, JSON:API, HAL or a GraphQL connection, and there are error responses too: 404, 401, 422 validation errors, 429, 500 and a GraphQL error. Each one is made in your browser, and the same choice always gives the same JSON. For bigger files, use the Large JSON File Generator.

What people use these files for

Need more than 1 MB? The Large JSON File Generator makes files up to 1 GB.

How to get a sample API response

  1. Pick a resource, such as users or orders.
  2. Pick a shape: one object, a plain list, page numbers, a cursor, JSON:API, HAL, GraphQL, or an error.
  3. Pick a size, then copy the response, download it, or open it in GigaJSON. The address keeps your choice, so you can share a link to it.

Private, and made for big files

This tool runs in your browser, in a background worker: nothing you paste or open is uploaded, and nothing is kept after you leave. JSON and XML input can be up to 1 GB, depending on available memory. Processing runs in a background worker; large analyses can take a minute or more. Already loaded features keep working if your connection drops. Loading another tool or jq for the first time needs a connection. When one tool isn't enough, GigaJSON opens your data with a tree, a table, JSONPath/JMESPath/jq queries, transforms, diff and history.

Sample API response questions

What do the shapes mean?

One object is what GET /users/1 returns. A plain list is a bare JSON array. Page numbers wrap the list as { data, meta, links } with page counts and next/prev links. Cursor is { data, has_more, next_cursor }, close to Stripe's list objects. JSON:API puts each record's fields under attributes with a type and a string id. HAL adds _links and puts the list under _embedded. GraphQL returns a Relay connection: edges with a node and a cursor, plus pageInfo.

Which error format do the errors use?

Problem details (RFC 9457, which replaced RFC 7807): type, title, status, detail and instance, with an errors list for validation and retry_after for rate limits. The GraphQL error follows the GraphQL spec: HTTP 200 with an errors list next to data.

Can I use these in a mock server or tests?

Yes. Download the file and serve it from your mock (json-server, MSW, WireMock, Prism), or paste it into a test fixture. The data is made up: names, emails and URLs use example.com.

Why is a response sometimes bigger than the size I chose?

A response always holds at least one record. A blog post with its comments is already over 1 KB, so at 1 KB you get one post and the page says so.

Is the response the same every time?

Yes. Each record is made from its number, so the same resource, shape and size always give the same JSON.

Is my data uploaded?

No. The tool runs in your browser, in a background worker. Nothing you paste or open goes to a server, and nothing is kept after you leave the page.

All tools