Question 1

What is a mock API and why would I use one?

Accepted Answer

A mock API is a fake HTTP endpoint that returns responses you define, without a real backend. Developers use one to build and test a frontend before the backend is ready, to reproduce specific responses like errors or slow requests, and to develop offline. With MockBase you create a live mock endpoint in seconds and point your app at it.

Question 2

How do I mock a REST API without writing any backend code?

Accepted Answer

Create a mock in MockBase, add a route such as GET /users, and set the JSON body and status code it should return. Your app calls the generated URL and gets that response. No server, no code, no deployment.

Question 3

Can I test how my frontend handles errors and slow responses?

Accepted Answer

Yes. You can set any status code, add latency to simulate a slow network so you can see your loading states, and use chaos injection to make an endpoint fail randomly at a chosen rate.

Question 4

Does it support dynamic responses based on the request?

Accepted Answer

Yes. You can return different responses based on query parameters, headers, or the request body, use templates to echo request data back, and enable a stateful CRUD mode where a resource behaves as if it has real state.

Question 5

Can I import an existing OpenAPI or Swagger spec?

Accepted Answer

Yes. Paste an OpenAPI 3.x document in JSON or YAML and MockBase generates the routes for you, and you can export any mock back to an OpenAPI document.

Question 6

Is MockBase free?

Accepted Answer

You can try it without signing in, and every feature is free during the beta. There is a Pro tier for custom subdomains, API token protection, chaos testing, and a higher request quota, which is unlocked for free while the beta is running.

Notes from building MockBase.

Why 169.254.169.254 Should Scare You

You're Probably Using "Mock" Wrong