Mock REST API

Paste a JSON (or any) response, pick a status and content-type, and get a stable public endpoint that returns it. Free fake API. No signup.

published

  • [FREE]
  • [NO_SIGNUP]
  • [SAVES_DATA]

⚠ Unlike most of the site, this tool sends your input to a server and stores it to work. It tells you exactly what it keeps and why — see the tool and the privacy page.

A mock REST API lets you stand up a fake endpoint in seconds: paste a response, get a stable public URL that returns it. Useful for front-end work before the backend exists, or to pin a specific response in a test.

Why this tool has a server

A fake API is, by definition, a reachable URL that returns a response — something a browser-only page can’t provide. So this tool uses a small backend (Cloudflare Pages Functions + a D1 database) to store your response and serve it at a stable URL with CORS enabled.

What you control

  • Body — any JSON, text, HTML, XML, or CSV (up to 100 KB).
  • Status — any HTTP code (200, 201, 404, 422, 500…), handy for testing error paths.
  • Content-Type — the header senders receive.

The endpoint answers any method with that canned response and sends permissive CORS headers, so a browser front-end can call it directly. It lives for 30 days, then is deleted.

The URL is public — random and unguessable, but not secret. Don’t return real secrets or personal data.

Frequently asked questions

What is this for?

When you're building a front-end or integration before the real API exists (or to reproduce a specific response in a test), you need a URL that returns a fixed payload. Paste your response, pick the status code and content-type, and you get a stable public endpoint that returns exactly that — to any HTTP method, with permissive CORS so it works from a browser app.

Why does this need a server?

A "fake API" is by definition a reachable URL that returns a response from anywhere — that cannot exist inside your browser. This uses a small backend (Cloudflare Pages Functions + D1) to store your response and serve it at a stable URL.

How long does the endpoint live?

Up to 30 days, then it is deleted automatically. Recreate it if you need it longer. The response body is capped at 100 KB.

Does it support CORS?

Yes — the endpoint returns Access-Control-Allow-Origin: * and handles OPTIONS preflight, so you can fetch it directly from a browser front-end during development.

Which methods does it respond to?

All of them — GET, POST, PUT, PATCH, DELETE. It returns the same canned response regardless of method (classic mock-server behavior). The status code and content-type are whatever you set.

Is the endpoint private?

No. The URL is random and unguessable but public — anyone with it gets your response. Don't put secrets or personal data in the response body.