FAKE API FOR TESTING
A fake REST API for testing, live in seconds
Describe the data you want. Get a real HTTPS endpoint that returns it — with full CRUD, custom status codes, and configurable response delays. No backend, no config files, no Docker.
What it looks like
Describe your data in plain English:
Support tickets with priority, status, customer email, and a descriptionYou get a live endpoint returning records shaped like that:
$ curl https://your-project.api.mockmydata.io/api/tickets
[
{
"id": 1,
"priority": "high",
"status": "open",
"customer_email": "ana.beltran@gmail.com",
"description": "Checkout fails on the payment step after applying a discount code."
},
...
]Emails match the names in the same record, dates come back in UTC, and the values look like production data rather than placeholders.
When you’d want a fake API
Build the frontend before the backend exists
Point your React, Vue, or mobile app at a fake API and build the whole UI while the real endpoints are still being designed. When the backend ships, swap the base URL.
Test error states you can't easily reproduce
Set an endpoint to return 500, 403, or 404 on demand. Testing how your app handles a failing server usually means breaking the server — here it's a dropdown.
Test loading states honestly
Add a response delay of up to ten seconds. Your spinners, skeletons, and timeout handling get exercised against a genuinely slow response instead of a setTimeout you added to fake it.
Demos and CI that don't depend on staging
A fake API doesn't go down, doesn't need credentials rotated, and returns the same data every time. Point your demo or your test suite at it and stop debugging someone else's environment.
What you get
- A real HTTPS endpoint on your own subdomain — callable from any app, device, or CI pipeline.
- Full CRUD — GET, POST, PUT, PATCH, and DELETE, with changes that persist.
- AI-generated records — describe the data, or list the field names you need.
- Custom status codes — make an endpoint return 500 or 403 to test your error handling.
- Response delays — up to ten seconds, so loading states get tested against real latency.
Questions
What is a fake API?
A fake API is a server that returns realistic-looking responses without any real business logic behind it. You define what the endpoint should return, and it returns that — so you can develop and test against it exactly as you would a production API.
Is it a real HTTP endpoint?
Yes. Every project gets its own subdomain and a live HTTPS URL. You can call it from your app, from Postman, from cURL, or from a CI pipeline. It is not a local mock library — it's a server on the internet.
Do the changes I POST persist?
Yes. POST, PUT, PATCH, and DELETE modify the stored data, so a record you create is there on the next GET. That makes it usable for testing full create-read-update-delete flows, not just reads.
How is this different from a static placeholder API?
Placeholder APIs give everyone the same fixed posts and users. Here you describe the data you actually need — support tickets with priorities, inventory with SKUs, patients with admission dates — and get records shaped like your real domain.
Is it free?
Yes. The free plan includes one project, unlimited endpoints, 100 API requests a day, and 5 AI generations a day. No credit card required.
Build your fake API now
One project, unlimited endpoints, and 100 requests a day on the free plan.
Or read the documentation first.