Choose a route
Create the path your application expects, such as /users, /products or /orders.
Fake API Generator
Turn your JSON into a hosted API endpoint your application can call. Build frontend features, prototypes and demos without creating temporary backend code.
Hosted HTTPS endpoints. No temporary backend server required.
JSON to API
Start with the data structure your interface needs. Instead of importing that data directly into your frontend, return it from a hosted endpoint and exercise the same request flow you will use with the production backend.
Your generated endpoint
/usershttps://apis.getforgeapi.com/YOUR_PROJECT_KEY/users
[
{
"id": 1,
"name": "Alex Morgan",
"email": "alex@example.com",
"role": "Designer",
"active": true
},
{
"id": 2,
"name": "Sam Rivera",
"email": "sam@example.com",
"role": "Developer",
"active": true
}
]How it works
Create the path your application expects, such as /users, /products or /orders.
Define realistic sample data using the same fields and structure planned for your application.
Use the generated HTTPS endpoint from your frontend, prototype, mobile app or test.
Two ways to get started
Build exactly what your application needs from scratch, or start faster with a pre-built Forge API starter project and customize its endpoints and JSON responses.
Create your own route and paste the exact JSON structure your application expects. You control the fields, values and response shape from the beginning.
Choose your own endpoint routes
Use custom objects, arrays and nested JSON
Match your planned production API structure
Need working endpoints immediately? Deploy one of Forge API's ready-made starter projects, then change the routes and JSON responses to match your application.
Deploy multiple useful endpoints at once
Start with realistic sample JSON
Customize the generated project after deployment
Use a starter project when you need realistic API endpoints quickly. Once deployed, you can edit the JSON responses and adapt the project to the screens and data structures your frontend requires.
Use it like a real API
Your generated endpoint is available through HTTPS, so you can call it with fetch, Axios or another HTTP client instead of hard-coding the response inside your application.
const API_BASE_URL =
"https://apis.getforgeapi.com/YOUR_PROJECT_KEY";
const response = await fetch(`${API_BASE_URL}/users`);
if (!response.ok) {
throw new Error(`Request failed: ${response.status}`);
}
const users = await response.json();
console.log(users);curl https://apis.getforgeapi.com/YOUR_PROJECT_KEY/usersA hosted fake API exercises your application's request, loading, parsing and error-handling code. That makes the development flow closer to the eventual backend integration.
Custom JSON
Use field names, values, objects, arrays and nested structures that resemble the response your production API will eventually return.
Populate product cards, detail pages and ecommerce prototypes with predictable sample data.
{
"id": 42,
"name": "Wireless Headphones",
"price": 79.99,
"category": "audio",
"inStock": true,
"rating": 4.7
}Build charts, statistics and dashboard layouts before analytics services or database queries are ready.
{
"revenue": 48250,
"orders": 318,
"customers": 1240,
"conversionRate": 3.8
}Development workflows
Build components and screens against realistic network responses while backend development continues.
Turn static prototypes into interactive applications that load realistic data over HTTP.
Demonstrate application flows without depending on production databases or services.
Use controlled data to repeatedly test how interfaces render expected API responses.
Create working API integrations quickly when there is not enough time to build a complete backend.
Use hosted HTTPS endpoints from simulators, emulators and physical devices without relying on localhost.
Fake API vs mock API
Developers often use the terms interchangeably. In both cases, the goal is to provide predictable API responses without depending on the final production backend.
Forge API focuses on hosted endpoints that your application can call over HTTP. You control the route and response while your frontend continues using a normal API integration.
Build before the production backend exists
Use realistic sample JSON over HTTP
Create predictable demos and prototypes
Avoid exposing production services during development
Share the same test endpoint across devices
Temporary backend, reusable frontend
Keep your API base URL separate from the components that consume your data. During development it can point to Forge API:
const API_BASE_URL =
"https://apis.getforgeapi.com/YOUR_PROJECT_KEY";When the production backend is available, replace that value:
const API_BASE_URL =
"https://api.example.com";If your production backend uses the same routes and response structures, your UI code can continue consuming the same data contract after the base URL changes.
Framework tutorials
Follow a framework-specific tutorial for connecting your application to hosted API endpoints.
Load hosted API data from React components.
Read tutorial →Use configurable API URLs in a Next.js application.
Read tutorial →Use hosted endpoints from mobile devices and emulators.
Read tutorial →Connect a Vue application to hosted test data.
Read tutorial →Call hosted API endpoints using Angular HttpClient.
Read tutorial →Frequently asked questions
A fake API is an API endpoint used during development or testing that returns controlled data instead of depending on a production backend. It lets applications make real HTTP requests while the final backend is unavailable or incomplete.
Create an endpoint, choose its route and HTTP method, add the JSON response you want it to return and use the generated Forge API URL from your application.
The terms are often used for the same development technique. Both describe API endpoints that imitate expected backend responses so applications can be built and tested independently.
Yes. You can define the JSON structure and values returned by your endpoint, including objects, arrays and nested data.
Yes. A hosted fake API is useful for testing request handling, rendering data and different interface states without calling production services.
Yes. Forge API endpoints are hosted HTTPS URLs, so they can be called from web applications, mobile applications and other HTTP clients.
No. Use fictional or non-sensitive sample data for development, prototypes, demonstrations and testing.
Create a hosted endpoint with your own JSON response and connect it to your application without building a temporary backend.