Development Tools
Dummy API Generator — Test REST Endpoints Live
Explore and call a free REST API sandbox at express-two-umber.vercel.app — auth, users, products & cart endpoints. Not a port scanner — try requests now.
Dummy API Generator on FYN Tools is a free Development Tools utility. Open Dummy API Generator in your browser — no signup required. Browse documented REST endpoints (auth, users, products, cart) against https://express-kieg.onrender.com/apis/v2, fill example JSON bodies, attach Bearer tokens when required, send live requests from the browser, and inspect status, headers, and response JSON — a sandbox, not a port scanner. Related: JWT Decoder.
Privacy & processing: HTTP requests go from your browser directly to the third-party sandbox API on Vercel. Request and response data are visible to that server.
TL;DR: Browse documented REST endpoints (auth, users, products, cart) against https://express-kieg.onrender.com/apis/v2, fill example JSON bodies, attach Bearer tokens when required, send live requests from the browser, and inspect status, headers, and response JSON — a sandbox, not a port scanner.
Reviewed by FYN Tools Editorial · Guides ·
Data input / output
| Inputs | Selected HTTP method/path, optional JSON body, optional Bearer token for protected routes |
|---|---|
| Outputs | HTTP status, response headers, and parsed JSON body with timing |
| Formats | REST JSON over HTTPS; base URL https://express-kieg.onrender.com/apis/v2 |
| Limits | Sandbox data only — not for production secrets; endpoint list fixed in UI; requiresAuth routes need a token from login/register |
| Processing | Server-side target (external REST sandbox on Vercel) |
How to Use the Dummy API Generator
- Browse endpoints by auth, users, products, or cart category.
- Select a method/path to load its description and example body.
- Edit the JSON body if needed for POST, PUT, or PATCH calls.
- For requiresAuth routes, paste a Bearer token from a prior login.
- Click Send Request and read status code and response JSON.
- Copy response data or iterate with different payloads.
What is a Dummy API Generator?
Pick a category — auth, users, products, or cart — and select an endpoint such as POST /auth/login or GET /users. Example JSON bodies pre-fill the request textarea where applicable. Click Send Request to call the live sandbox at https://express-kieg.onrender.com/apis/v2 and view status, headers, and response JSON.
Protected routes show a requiresAuth badge; register or login first, then paste the returned Bearer token into the authorization field. This helps prototype frontend flows against realistic REST shapes. It is not a port scanner or network probe tool.
ENDPOINTS array drives the UI catalog. Requests use fetch with method, headers, and optional JSON body. Responses display in structured cards with copy helpers. Categories group auth (register, login, change-password), users CRUD, products, and shopping cart operations.
How it works
You set code, css values, or structured text in the editor in the live panel. Dummy API Generator then free dummy REST API for students and developers to practice login, CRUD, and authentication testing with live endpoints. Results show as formatted / generated code you can copy.
Explore more tools on our site.
Usage scenarios
- Frontend auth wiring without a backend: Point a React/Vue login form at POST /auth/login, store the returned JWT, and attach Authorization: Bearer … on protected GETs before your real API exists.
- Postman / Hoppscotch classroom lab: Students share the same dummy base URL, practice 401 vs 200 responses, and learn expiresIn options (15m–7d) without provisioning cloud sandboxes.
- CRUD homework checklist: Create a user, list users, update fields, toggle status, then delete — verify each verb against the live tester and screenshot responses for submission.
- Decode the practice JWT: After login, paste the token into JWT Decoder to confirm claims and expiry while learning how Bearer auth connects to JSON Web Tokens.
Input / Output Examples
Input
POST /auth/login · body {"email":"demo@fyn.dev","password":"••••"} · expiresIn: "1h"Output
200 · {"token":"eyJ…","expiresIn":"1h"} — paste token as Authorization: Bearer eyJ…Input
GET /users with valid Bearer token
Output
200 · JSON array of dummy users (id, name, status) for UI table binding
Frequently Asked Questions
Can I use the dummy API in production?+
No. Data is for practice and may be reset. Build real auth, rate limits, and persistence on your own backend before shipping.
How do I authenticate requests?+
Call login/register to receive a JWT, then send Authorization: Bearer <token> on protected routes. Tokens can expire in 15m, 1h, 12h, 1d, or 7d depending on expiresIn.
Which CRUD routes exist?+
Typical practice routes include creating users, listing users, fetching the current account, updating by id, deleting by id, and patching status. Use the on-page endpoint list as the source of truth.
Why am I getting 401 Unauthorized?+
Usually the token expired, the Bearer prefix is missing, or you are calling a protected route before login. Re-login, copy a fresh token, and retry.
Is there a signup fee or API key for FYN’s dummy API?+
The practice surface is free for learning. Treat credentials you create here as disposable test accounts — never reuse real production passwords.
Key Features
- Base URL express-two-umber.vercel.app/apis/v2
- Auth, users, products, cart endpoints
- Example JSON bodies
- Bearer token field
- Send Request with response viewer
Benefits
Build UI against working endpoints before backend delivery.
Learn REST patterns with immediate feedback.
Test JWT-protected calls without deploying your own API.
When to Use Dummy API Generator
- Prototyping a frontend before your real backend exists
- Teaching REST verbs and JSON request bodies
- Testing Authorization header flows with register/login
- Demonstrating cart and product API shapes in workshops
Advantages
- Live REST sandbox with real HTTP round trips
- Categorized endpoint catalog with examples
- Bearer auth support for protected routes
- Response status, headers, and body inspection
Tips
- Register a fresh account before testing change-password or user CRUD.
- Keep sandbox passwords disposable — do not reuse real credentials.
- Read requiresAuth badges before wondering why a call returns 401.
- Use example JSON as a schema guide, then tweak fields incrementally.
Common Mistakes
Expecting open port scanning — this sends HTTP requests to a REST API only.
Calling protected routes without a Bearer token from login.
Storing production secrets in sandbox registration payloads.
Assuming sandbox data persists forever — treat it as disposable.
Summary
Pick a REST endpoint, send live requests to the Vercel sandbox, and inspect JSON responses — API testing, not port scanning.