Know Errors For Script or Title Not Generating

1. Error:  Incorrect API key provided: Ym7p*****x**********ogsI. You can find your API key at https://platform.openai.com/account/api-keys.Retry

Symptoms: Stuck loading spinner, or no output after request.

Fix:

• Ensure your OpenAI API key is correctly entered in the API Integrations settings.

• Double-check if your API key has usage limits or quota restrictions on the OpenAI dashboard.

• Make sure that your OpenAI account has a balance.

2. Error: You exceeded your current quota. Please check your plan and billing details. For more information on this error, read the docs: https://platform.openai.com/docs/guides/error-codes/api-errors.

Symptoms: Stuck loading spinner, or no output after request.

OpenAI recently introduced $5 free trial credits for new API users, but these are:

• Limited to specific countries

• Time-limited (expires after 3 months)

• Capped at a spending threshold

If your credits are used up or you've reached your monthly spend cap, you will start receiving this 429 quota error.

Fix: 

1. Log in to your OpenAI Account

Go to https://platform.openai.com/account/usage to see how much of your quota you've used.

2. Check Billing Settings

Visit https://platform.openai.com/account/billing and verify:

• Your payment method is set up
• You have credits or a spending limit in place

3. Add More Credits or Increase Limits

If you've exhausted your quota, you’ll need to:

• Add a payment method
• Manually increase your monthly spending cap

Other error codes related to OpenAI Key that users might face:

Error 401 - Cause: Invalid Authentication

Solution: Ensure the correct API key and requesting organization are being used.

401 - Incorrect API key provided

Cause: The requesting API key is not correct.

Solution: Ensure the API key used is correct, clear your browser cache, or generate a new one.

403 - Country, region, or territory not supported

Cause: You are accessing the API from an unsupported country, region, or territory.

Solution: Please see this page for more information.

429 - Rate limit reached for requests

Cause: You are sending requests too quickly.

Solution: Pace your requests. Read the Rate limit guide

500 - The server had an error while processing your request

Cause: Issue on our servers.

Solution: Retry your request after a brief wait and contact us if the issue persists. Check the status page.

503 - The engine is currently overloaded. Please try again later

Cause: Our servers are experiencing high traffic.

Solution: Please retry your requests after a brief wait.

503 - Slow Down

Cause: A sudden increase in your request rate is impacting service reliability.

Solution: Please reduce your request rate to its original level, maintain a consistent rate for at least 15 minutes, and then gradually increase it.