A mock backend for frontend teams

Build the interface. Let the backend catch up.

Define an API contract, get a real endpoint, and keep shipping while the service is still in progress. Exercise success, empty, and failure states with responses you control.

Create your first API Explore dashboard

Define mock APIs with real HTTP methods and routes

Generate production-like endpoints instantly

Test loading, empty, and error states before backend is ready

Capture request logs for debugging and QA

Demo project

GET/users200 OK

{

"success": true,

"data": [

{ "id": 1, "name": "Abhishek", "email": "abhishek@example.com" }

]

}

Example endpointGET · 200

https://your-app.com/api/mock/px_project_key/users

Real endpoints

Turn definitions into working HTTP routes with realistic responses and delays.

Scenarios

Create success, error and empty states for every API contract.

Fast iteration

Validate loading states, status handling and UI flows before backend integration.

Developer workflow

Document and share endpoints with QA, frontend and backend teams in one place.

How it works

DEFINE API → GENERATE REAL ENDPOINT

Step 1

Define API

Set method, path, status code and response JSON

Step 2

Generate endpoint

Share a short URL that reads the saved API from Supabase

Step 3

Consume in UI

Hook it into your frontend and exercise edge cases

Step 4

Swap later

Replace the mock base URL with the real backend when ready

Developer-first docs

Use mock data in the real app flow

Open dashboard

const response = await fetch(

"https://your-app.com/api/mock/px_project_key/users"

);

const data = await response.json();

Made for the in-between

Keep your frontend moving while services take shape.

Build against realistic response shapes, cover edge cases early, then switch to the production API when it is ready.

Start building

Frontend teams

QA and test flows

Backend integration

Design prototypes

Frequently asked

A few useful details

Where is my mock data stored?

Your projects, API definitions, and request previews are stored in your Supabase database and are available when you sign in on another device.

Can I generate realistic collections?

Yes. Add a representative JSON object and use Generate 20+ random records to expand arrays while keeping the same response structure.

What happens when the backend is ready?

Replace the mock base URL in your frontend with the production service. Your definitions stay in Supabase for later development and QA.