Mock API: a REST endpoint from any schema

3 November 2026

Turn a schema into a hosted REST API with stored records, so the front end can start before the back end exists.

Waiting for the back end is one of the most common reasons a front end stalls. A Mock API removes the wait: describe the tables once, save, and you get a URL that answers like a real API.

What it does

  • Full CRUD. GET and POST on /users, GET, PUT, PATCH and DELETE on /users/:id. Changes are stored, so what you create is there on the next request.
  • Lists that behave. Pages with ?page=&limit=, sorting with ?sort=field&order=desc, search with ?q=, filters with ?field=value, and the total in X-Total-Count.
  • Related tables. Child records answer under their parent, such as /users/42/orders.
  • Testing the unhappy paths. Add a delay to see loading states, or a share of 500 errors to test retries. Reset the data at any time.
  • Works from anywhere. CORS is open, so local development servers and preview deployments can call it directly.

The records are generated from your schema on the first request, so they look like real users, orders or tickets, not test1, test2.

Limits

Free accounts get 3 mock APIs with 100 records per table. Pro raises that to 25 APIs, 1,000 records and 100,000 requests a day; Team to 100 APIs and 5,000 records. See pricing.

More on the Mock API page.

All updates