What resource types can I generate?

Four common REST resources: user (id, name, email, role, timestamps), product (sku, name, category, price, rating, stock), order (order number, status, line items, total) and event (analytics-style type, ids and properties). Each field uses a realistic value and the correct JSON type.

Is the JSON valid and well-formed?

Yes. The output is produced with JSON.stringify and pretty-printed with two-space indentation, so it parses cleanly in any JSON tool, language, or mock server without manual cleanup.

What does the data and meta envelope do?

When enabled, an array of records is wrapped as { data: [...], meta: { total, page, per_page } }. This mirrors the pagination envelope that many REST and JSON:API style backends return, which makes your mock closer to the real response shape.

Are the records realistic enough for demos?

They are designed to look plausible — real-sounding names, valid-format emails, ISO 8601 timestamps, two-decimal prices and UUID-style ids. They are fake placeholder values, so never treat them as real user data.

Does anything get sent to a server?

No. All generation runs locally in your browser. The tool never contacts a backend, so you can mock responses offline and nothing you generate is transmitted anywhere.

Random API Response Generator

Mock a backend before it exists

The Random API Response Generator produces plausible JSON for the resources a typical REST API returns — users, products, orders and analytics events. It lets frontend work continue before the real endpoint is built: paste the output into a mock server, a fixture file, or a fetch stub and develop against a realistic response shape.

How it works

Each resource type has a template describing its fields and the JSON type of each one. For every requested record the generator fills that template from curated value pools — names, product titles, categories, currencies — and from small helpers that emit a UUID-style id, an ISO 8601 timestamp, or a two-decimal price. Orders additionally build a nested items array and sum the line totals so the total field is internally consistent. The whole structure is serialized with JSON.stringify and indented, which guarantees the result is valid, parseable JSON.

A seeded pseudo-random source keeps a given configuration stable between renders; pressing Regenerate advances the seed for a fresh set. Turning on the envelope option wraps a multi-record array as { data, meta } to match the pagination shape many APIs use.

Tips and example

For a single-object endpoint such as GET /users/:id, set the count to one and leave the envelope off to get a bare object.
For a list endpoint such as GET /products, raise the count and enable the envelope so your mock includes meta.total for pagination logic.
A generated order keeps its total equal to the sum of its line items, so it is safe to test cart and checkout rendering against it.
Treat every value as placeholder data — the names and emails are synthetic and must never stand in for real records.