Terms and Conditions

These Terms and Conditions govern your access to and use of Forge API, including the website available at getforgeapi.com, the Forge API dashboard, hosted mock API endpoints, subscriptions and related services.

Forge API currently operates from the United Kingdom under the trading name Forge API.

In these terms, “Forge API”, “we”, “us” and “our” refer to the operator of the Forge API service. “You” and “your” refer to the person or organisation using the service.

By creating an account, purchasing a subscription or using the service, you agree to these terms.

Forge API is a cloud-based developer platform for creating mock REST API projects and endpoints.

The service may allow users to:

• Create one or more mock API projects.
• Create endpoint paths within a project.
• Choose an HTTP request method.
• Configure an HTTP response status.
• Store a JSON response body.
• Receive a generated public API URL.
• Call the generated URL from a website, mobile application or other software.
• Monitor project and request usage.
• Manage account and subscription details.

Forge API is intended primarily for development, prototyping, demonstrations and testing while a production backend is unavailable or under development.

You must be at least 18 years old and legally capable of entering into a contract.

When creating an account, you must provide accurate and current information. You are responsible for keeping your account information up to date.

You must not:

• Create an account using false or misleading information.
• Create an account using another person’s identity without permission.
• Use automated account registrations or bots.
• Create multiple accounts to bypass service limits.
• Allow unauthorised persons to access your account.

Email verification may be required before you can access all features.

You are responsible for:

• Keeping your password secure.
• Protecting access to your email account.
• Protecting your generated project keys and endpoint URLs.
• Reviewing activity associated with your account.
• Informing us promptly about suspected unauthorised access.

A generated project key forms part of a public mock API URL. It should be treated as a public project identifier rather than as a confidential password.

A Forge API project may contain multiple mock API endpoints.

A generated URL may look similar to:

Anyone who knows or discovers a generated URL may be able to call it. You must not place confidential, secret or production information in a mock response.

We may allow project keys to be regenerated. Regenerating a project key may cause integrations using the previous URL to stop working.

“User Content” includes project names, endpoint paths, HTTP methods, response status codes, response headers, JSON response bodies and other information submitted through your account.

You retain ownership of your User Content.

You grant us a limited, worldwide, non-exclusive licence to host, copy, process, transmit and back up your User Content only as reasonably necessary to:

• Provide the Forge API service.
• Return your configured mock responses.
• Maintain system backups.
• Prevent fraud and abuse.
• Investigate technical or security incidents.
• Comply with legal obligations.

You confirm that you have all necessary rights and permissions to submit and use your User Content.

You must not upload, store or return content that:

• Is unlawful, fraudulent, defamatory, threatening or abusive.
• Contains malware, malicious scripts or harmful code.
• Facilitates phishing, credential theft or impersonation.
• Contains real passwords, private keys or production access tokens.
• Contains complete payment-card information.
• Contains confidential production credentials.
• Contains sensitive personal information without a valid legal basis.
• Exposes real patient, child, employee or customer information where dummy data could be used.
• Infringes intellectual-property, privacy or other legal rights.
• Supports illegal goods, services or activities.

Mock data should be fictional, anonymised or appropriately pseudonymised.

We may remove prohibited content or disable access without prior notice where reasonably necessary to protect users, third parties or our infrastructure.

You must not:

• Attempt to overload, disrupt or damage the service.
• Attempt to bypass account, project or request limits.
• Use multiple accounts to evade plan restrictions.
• Probe or exploit vulnerabilities without written authorisation.
• Use Forge API as a production content-delivery network.
• Use Forge API as the sole backend for a critical production system.
• Resell or copy the service without permission.
• Use generated endpoints for unlawful or abusive automated traffic.

Current plan prices and allowances are displayed on the Forge API Pricing page.

Monthly request limits reset at the beginning of each calendar month using UTC.

We may change plan features, allowances or pricing by providing reasonable advance notice where practical.

A request is generally counted when Forge API infrastructure receives a call to a valid generated endpoint.

A request may still count where:

• The calling application closes the connection after the request reaches us.
• The caller retries a request.
• The caller does not process the response.
• A client library repeats a request automatically.
• The request returns an error caused by plan or usage restrictions.

Internal Forge API health checks and monitoring requests may be excluded.

Where a paid plan includes “unlimited endpoints”, this means unlimited endpoints within each permitted project, subject to reasonable technical and abuse-prevention controls.

Unlimited endpoints do not permit the creation of excessive, automated or abusive numbers of records intended to affect platform stability or evade plan limits.

The Pro Plus plan currently includes up to 1,000,000 API requests per calendar month.

References to “unlimited” or high-volume usage do not mean technically unrestricted or infinitely available usage.

We may temporarily rate-limit or suspend traffic where:

• Usage exceeds the published monthly fair-use allowance.
• Traffic creates unusual or excessive infrastructure load.
• Traffic appears fraudulent, malicious or automated in an abusive way.
• Usage affects availability for other customers.
• The service is being used as a production backend or CDN.
• A customer attempts to evade usage limits.

Reasonable per-second or per-minute rate limits may apply to all plans to protect service stability.

Custom response delay is a paid-plan feature.

The available delay range may depend on the customer's current plan. Delay settings are intended for development and testing loading states, timeout handling and slow-network behaviour.

We may limit delay values or disable the feature where needed to protect platform performance.

Paid subscriptions are billed in advance at the price shown during checkout.

Payments may be processed by Stripe or another payment provider. Forge API does not normally receive or store your complete payment-card number.

Unless otherwise stated:

• Subscriptions renew automatically each month.
• Prices are shown in pounds sterling.
• Applicable VAT or other taxes may be added where required.
• The selected plan becomes available after successful payment confirmation.
• A failed or reversed payment may result in restricted access.

You may cancel a paid subscription using the available billing controls or by contacting:

Cancellation normally prevents future renewal. Paid access may continue until the end of the current billing period.

After cancellation or downgrade, you may need to remove projects or endpoints that exceed the new plan limits.

Except where required by law, subscription payments are not automatically refundable once a billing period has begun.

We may consider refunds where:

• A duplicate charge occurred.
• You were charged an incorrect amount.
• A prolonged Forge API service failure materially prevented use.
• Applicable law requires a refund.
• Exceptional circumstances justify a discretionary refund.

We do not normally refund:

• Unused subscription time.
• Failure to cancel before renewal.
• Usage that reached published plan limits.
• Suspension caused by prohibited use.
• Errors caused by User Content.

If you purchase Forge API as a UK consumer rather than wholly for business purposes, statutory consumer rights may apply.

Nothing in these terms excludes or restricts rights that cannot legally be excluded.

We aim to provide a reliable service, but we do not guarantee uninterrupted or error-free availability.

The service may be unavailable because of:

• Planned maintenance.
• Emergency maintenance.
• Hosting or infrastructure failures.
• Internet or third-party service outages.
• Security incidents.
• Denial-of-service activity.
• Circumstances outside our reasonable control.

Unless agreed separately in writing, no guaranteed uptime or service-level agreement applies.

Forge API is designed for development and testing.

You must not rely on it as:

• The sole source of important business data.
• A permanent production database.
• A critical authentication system.
• A payment-processing backend.
• A medical, emergency or safety-critical service.
• A guaranteed high-availability production API.

You are responsible for keeping your own copies of project configurations and JSON responses.

We aim to return the method, status, headers and JSON response configured by the project owner.

Responses may be affected by:

• Browser CORS restrictions.
• Network conditions.
• Malformed requests.
• Unavailable or disabled projects.
• Unavailable or disabled endpoints.
• Plan limits.
• Rate limits.
• Account suspension.
• Scheduled or emergency maintenance.

You are responsible for testing how your application handles failed, delayed or unexpected responses.

The Forge API website, platform, software, documentation, branding and underlying technology are owned by us or our licensors.

These terms do not transfer ownership to you.

You may not:

• Copy or resell the Forge API service.
• Remove proprietary notices.
• Use Forge API branding without permission.
• Reverse engineer the service except where law expressly permits.
• Systematically extract the service to create a competing product.

You may submit feedback, ideas or feature requests.

You grant us permission to use that feedback without restriction or compensation, provided we do not publicly identify you without permission.

Forge API currently relies on third-party providers including:

• Supabase for authentication, database and backend services.
• Vercel for application hosting and deployment.
• Stripe for payment and subscription processing when enabled.
• Resend or another email provider for transactional email when enabled.

Third-party services are governed by their own terms and privacy practices.

We may suspend or terminate an account where:

• These terms are breached.
• Payment remains overdue.
• The account creates a security risk.
• Usage is unlawful, fraudulent or abusive.
• Usage threatens platform stability.
• A legal authority requires us to act.

Where practical, we will provide notice and an opportunity to resolve the issue. Immediate action may be taken for serious legal, security or abuse concerns.

After termination:

• Generated endpoints may stop working immediately.
• Dashboard access may be removed.
• User Content may be scheduled for deletion.
• Outstanding charges remain payable.
• Information may be retained where legally necessary.
• Backup copies may remain temporarily until normal backup rotation completes.

The service is provided on an “as available” basis.

To the maximum extent permitted by law, we do not guarantee that:

• The service will meet every technical requirement.
• Mock behaviour will exactly match a future production API.
• All defects will be corrected immediately.
• The service will always be uninterrupted.
• User Content will never be lost.

Nothing in these terms excludes rights or warranties that cannot legally be excluded.

Nothing in these terms excludes liability for:

• Death or personal injury caused by negligence.
• Fraud or fraudulent misrepresentation.
• Liability that cannot legally be excluded.

Subject to the above and where legally permitted, we will not be liable for indirect or consequential losses, including loss of profit, revenue, opportunity, goodwill, anticipated savings or data.

Where legally permitted, our total liability relating to Forge API will not exceed the greater of:

• The amount you paid Forge API during the 12 months before the event giving rise to the claim.
• £100.

If you use Forge API for business purposes, you agree to compensate us for reasonable losses, claims and expenses arising from:

• Your unlawful User Content.
• Your infringement of third-party rights.
• Your misuse of the service.
• Your material breach of these terms.

This does not apply to the extent that the loss was caused by our own breach or negligence.

We may add, remove or modify features.

Where a material change negatively affects a paid plan, we will try to provide reasonable notice where practical.

We may update these terms to reflect changes to the service, pricing, security, legal requirements or business operations.

The updated date will appear at the top of this page.

Material changes affecting existing paid customers will be communicated where reasonably practical.

These terms are governed by the laws of England and Wales.

If you are a consumer, you may also benefit from mandatory legal protections in the country where you live.

The courts of England and Wales will have jurisdiction except where applicable consumer law provides otherwise.

If any part of these terms is found to be unenforceable, the remaining sections will continue to apply.

A delay in enforcing a right does not waive that right.

These terms, together with the Privacy Policy, Pricing page and checkout information, form the agreement governing your use of Forge API.

Questions regarding these Terms and Conditions may be sent to: