Frequently asked questions

Forge API is a hosted mock JSON API platform. It lets you create projects, define endpoints, configure JSON responses, and call those endpoints from websites, mobile apps, automated tests, prototypes, and development environments.

No. Forge API is fully hosted. You can create and manage your APIs from the dashboard, then use the generated public URL directly from your application.

Create an account, open the dashboard, create a project, and then add an endpoint. Choose the HTTP method, enter the endpoint path, provide a JSON response body, and save it. Your endpoint will then be available through its generated public URL.

Forge API is useful for frontend development, mobile app development, prototypes, demos, automated testing, teaching, proof-of-concept projects, and any situation where a real backend is not ready or not required.

Yes. Forge API includes a Free plan that allows you to create a limited number of projects and endpoints and make a limited number of requests each month.

A project is a container for related mock API endpoints. For example, you could create one project for an ecommerce application and another for a mobile banking prototype.

An endpoint is a specific API route inside a project. It includes an HTTP method, a path, a status code, and a JSON response body.

Forge API can support common REST methods such as GET, POST, PUT, PATCH, and DELETE. The method you configure must match the method used when calling the public endpoint.

Yes, provided they use different HTTP methods. For example, GET /users and POST /users can exist as separate endpoints within the same project.

Yes. You can update an endpoint's path, method, response status, and JSON response body from the dashboard.

Yes. You can delete resources from the dashboard. Deleting a project also removes the endpoints that belong to that project, so make sure you no longer need them before confirming deletion.

Forge API expects endpoint response bodies to contain valid JSON. Invalid JSON should be corrected before the endpoint is saved or published.

Use the public URL shown for your project and append the endpoint path. You can call it using fetch, Axios, Postman, curl, a mobile application, or any other HTTP client.

Yes. Forge API is designed to work with browser-based applications, including projects built with React, Next.js, Vue, Angular, Svelte, and plain JavaScript.

Yes. Public mock API responses are intended to be accessible from browser applications. This allows frontend projects running on another domain or localhost to request your mock endpoint.

Yes. Copy your public endpoint URL into Postman, select the correct HTTP method, and send the request.

Yes. Forge API can provide predictable JSON responses for integration tests, end-to-end tests, prototypes, demonstrations, and CI workflows.

Forge API returns an error response when the project, endpoint path, or HTTP method does not match a published endpoint.

An endpoint URL remains stable while its project key and endpoint path remain unchanged. Changing or deleting those values can make the previous URL stop working.

Forge API offers Free, Starter, Pro, and Pro Plus plans. Each plan includes different project, endpoint, request, and storage allowances.

The Free plan currently includes 1 project, up to 10 endpoints, and up to 500 requests within the applicable monthly usage period.

Each request made to a public Forge API endpoint counts toward the account's request usage. Dashboard activity does not count as a public API request.

Request allowances reset according to the account's usage or billing period. The current usage period and totals can be viewed in the dashboard.

If your existing projects, endpoints, or stored data exceed the new plan's limits, your account enters a grace period. Existing APIs continue working during that period, but creating new projects and endpoints is blocked until you upgrade or reduce your usage.

If the account remains over its plan limits after the grace period, public APIs may be suspended. If the account remains non-compliant through the additional retention period, project resources and usage records may be automatically deleted.

Yes. Upgrade to a plan that supports your current usage or remove enough resources to become compliant. Access can be restored once the account is within its plan limits.

No. Automatic resource cleanup is designed to remove projects, endpoints, and related usage records. Your authentication account, profile, and subscription history remain intact.

Yes. Paid Forge API plans are available with monthly and yearly billing options where billing is enabled.

Forge API uses Stripe to process subscriptions and payments securely.

Forge API does not directly store your full payment card details. Payment information is handled by Stripe.

Yes. You can move to a larger plan from the billing area when paid subscriptions are available.

Yes. A downgrade may place the account into a grace period if the current number of projects, endpoints, or stored resources exceeds the new plan's limits.

Yes. Subscription management is available through the billing section and Stripe Customer Portal. Cancellation timing depends on the subscription's billing settings.

You can access billing information and subscription management from the Forge API dashboard.

Public project endpoints can be accessed by anyone who knows their URL unless an additional access-control feature is provided for that endpoint. Do not place secrets or confidential production data in mock responses.

No. Mock responses should never contain real passwords, private keys, access tokens, payment details, or other sensitive information.

Dashboard access requires authentication. Database permissions and server-side checks are used to restrict users to their own Forge API resources.

Users should only be able to manage resources belonging to their own account. Ownership checks are enforced by the application and database.

Forge API is primarily a mock API platform. It is suitable for development, testing, demonstrations, and prototypes, but it should not be treated as a replacement for a full production database and backend system.

Use the sign-up page and follow the authentication steps. Once signed in, you can access the dashboard and create your first project.

Use the available login or password recovery options. If the issue continues, contact Forge API support and include the email address associated with your account.

Export capabilities may depend on the current Forge API feature set. You should keep a local copy of important mock response data used by your application or test suite.

Contact Forge API support with a clear description of the issue, the affected page or endpoint, the expected result, and any error message you received.

Use the contact or support option available on the Forge API website. Include as much relevant detail as possible so the issue can be investigated efficiently.