Troubleshooting

1. 1

   Confirm that you copied the complete endpoint URL from the correct project.

2. 2

   Confirm that the HTTP method matches the method configured on the endpoint.

3. 3

   Confirm that the endpoint is active.

4. 4

   Confirm that the project and account are active.

5. 5

   Include every required project and endpoint request header.

6. 6

   Check whether the monthly request allowance has been exhausted.

7. 7

   Test the same request using cURL or Postman to separate frontend problems from endpoint problems.

Check the URL structure:

https://apis.getforgeapi.com/abc12/products

These are different endpoint definitions:

GET /products
POST /products
DELETE /products

If the endpoint is configured as POST /login, opening the URL in a browser sends a GET request and will not match the POST endpoint.

Common JSON mistakes include:

• Missing commas between fields
• Trailing commas after the final item
• Single quotes instead of double quotes
• Unquoted property names
• Unclosed arrays or objects
• JavaScript values such as undefined or NaN

Invalid example:

{
  "name": "Polo Shirt",
  "price": 10,
}

Corrected example:

{
  "name": "Polo Shirt",
  "price": 10
}

Send the exact header name and secret value configured in the dashboard:

curl \
  -H "x-api-key: your-secret-value" \
  https://apis.getforgeapi.com/abc12/products

Check for:

• An incorrect header name
• An incorrect secret value
• Leading or trailing whitespace
• A header added to the wrong request
• A project-level header that was included while an endpoint-level header was omitted

Try these steps:

1. 1

   Reopen the endpoint and confirm that the updated JSON is visible in the editor.

2. 2

   Confirm that the save action completed without an error message.

3. 3

   Copy the public URL again from the endpoint or project page.

4. 4

   Test the URL directly using cURL or a private browser window.

5. 5

   Confirm that your application is not using an older environment variable or hardcoded URL.

6. 6

   Check whether the application is displaying previously cached data from its own state-management or request library.

Check:

• The complete endpoint URL is correct
• The endpoint exists and is active
• The method is supported by that endpoint
• Required request headers are included
• The browser is not blocking mixed HTTP and HTTPS content
• The request is going directly to Forge API rather than through a failing local proxy

Before calling response.json(), check the status code and whether the response is expected to have a body.

const response = await fetch(
  "https://apis.getforgeapi.com/abc12/products"
);

if (!response.ok) {
  const errorBody = await response.text();

  console.error({
    status: response.status,
    statusText: response.statusText,
    body: errorBody,
  });

  throw new Error(
    `Forge API request failed with status ${response.status}`
  );
}

const data = await response.json();

console.log(data);

For example, a 1,500 millisecond delay does not guarantee that the complete request finishes in exactly 1.5 seconds. The total time also includes:

• Client network latency
• DNS and TLS connection time
• Forge API request processing
• Browser or application processing

Review the dashboard and check:

• The current project count
• The maximum projects allowed by the active plan
• The account status
• Whether paid access has ended

The Free plan limits endpoints per project. Paid plans may provide unlimited endpoints per project, subject to other account limits.

You can:

• Delete an unused endpoint
• Reuse and edit an existing endpoint
• Upgrade to a plan with a higher allowance

Open the Usage page and compare:

• Requests used in the current period
• The active plan’s request allowance
• The usage period start and end dates

Access returns when the usage period resets or the account upgrades to a plan with a larger allowance.

Reduce the response size by:

• Removing repeated fields
• Reducing the number of sample records
• Using shorter placeholder strings
• Splitting one large response across several endpoints
• Upgrading to a plan with a larger response limit

When an account is paused:

• Dashboard access may redirect to the paused-account page
• New projects and endpoints cannot be created
• Protected server actions reject the account
• The contact page remains available for support

Try:

1. 1

   Sign out and sign in again.

2. 2

   Confirm that the browser allows cookies for Forge API.

3. 3

   Try a private browsing window.

4. 4

   Confirm that you are using the correct Forge API domain and environment.

5. 5

   Use the password-reset flow when the password is no longer known.

Check:

• You returned to Forge API using the successful Checkout flow
• The Billing page after waiting briefly
• The subscription status in Stripe
• Recent Stripe webhook deliveries
• Whether webhook deliveries returned a successful response

After scheduling cancellation:

1. 1

   Return from the Stripe Customer Portal to Forge API.

2. 2

   Refresh the Billing page.

3. 3

   Confirm that Stripe shows a cancellation date rather than an immediate cancellation.

4. 4

   Review recent webhook deliveries when the local state remains unchanged.

If the displayed currency looks incorrect:

• Disable any VPN or proxy and reload the page
• Confirm the deployment is receiving country information
• Confirm that pricing, Checkout and subscription-status routes use the same currency helper
• Confirm that both GBP and USD Stripe Price IDs are configured in the deployment environment

Review:

• Supabase URL and publishable-key values in the affected environment
• Stripe secret, webhook and Price ID variables
• Vercel deployment protection settings
• Which Git branch the deployment was built from
• The domain assigned to the current deployment
• Recent build and function logs

curl -i https://apis.getforgeapi.com/abc12/products

For a protected endpoint:

curl \
  -H "x-api-key: your-secret-value" \
  https://apis.getforgeapi.com/abc12/products

For a POST endpoint:

curl -i \
  -X POST \
  https://apis.getforgeapi.com/abc12/login

• The email address associated with the account
• The affected project name
• The endpoint method and path
• The final HTTP status code
• The response body or error message
• The approximate time the problem occurred
• The environment: localhost, Preview or Production
• Steps required to reproduce the issue