Endpoints
0 endpoints
No endpoints yet
Add an endpoint or pick a template
Select an endpoint to edit
Endpoints
0 endpoints
No endpoints yet
Add an endpoint or pick a template
Mock API Builder
Define endpoints, publish a real URL, and build your front end before the backend exists.
What it does
Define endpoints, give each one a response body, and get a real URL you can call from your front end while the actual backend does not exist yet. No account, no local server to run, no Docker.
Responses are templates rather than fixed strings, so a list endpoint can return twenty different-looking records instead of the same one twenty times. That difference matters more than it sounds when you are building a UI: fixed fixtures hide layout bugs that only appear when a name is unusually long or a field is empty.
More detail
Template variables
Two kinds. Path parameters are echoed back from the request, so {{params.id}} in the response returns whatever id was called. Faker expressions generate plausible data: names, emails, numbers, dates, addresses.
The guide has the full list of both, with examples of the syntax.
Conditional responses
An endpoint can return different responses depending on the request, which is how you exercise the paths that are otherwise hard to reach. Point one condition at a missing record and return a 404, another at a specific id and return a 500, and the happy path everywhere else. That is much faster than persuading a real backend to fail on demand.
Limits worth knowing
Mock APIs are public. Anyone with the URL can call them, so do not put real data in a response body.
They expire. The endpoint stays alive while it is being called and is cleaned up once it stops, so a mock you use daily persists and one you set up months ago does not.
There is no persistence between calls. This serves responses; it does not store what you POST to it. If your test needs to create something and then read it back, this is the wrong tool.
Questions
Do I need an account or a running server?
Neither. Define the endpoints in the browser, publish, and call the URL. There is nothing to install and nothing to sign up for.
Can other people call my mock API?
Yes. The URL is public and unguessable rather than private. Treat anything you put in a response as published, and use generated data rather than real records.
Does it remember what I POST to it?
No. Each request is answered from the definition you wrote, with no state carried between calls. A create-then-read test will not work here.
How do I get realistic data instead of the same record repeatedly?
Use the faker expressions in the response template. Each request re-evaluates them, so a list endpoint returns varied records and your UI gets exercised against names and values of different shapes.