Error codes

• You are using a revoked API key.
• You are using a different API key than the one assigned to the requesting organization.
• You are using an API key that does not have the required permissions for the endpoint you are calling.

To resolve this error, please follow these steps:

• Check that you are using the correct API key and organization ID in your request header. You can find your API key and organization ID in your account settings.
• If you are unsure whether your API key is valid, you can generate a new one. Make sure to replace your old API key with the new one in your requests and follow our best practices guide.

• There is a typo or an extra space in your API key.
• You are using an API key that belongs to a different organization.
• You are using an API key that has been deleted or deactivated.
• An old, revoked API key might be cached locally.

To resolve this error, please follow these steps:

• Try clearing your browser's cache and cookies, then try again.
• Check that you are using the correct API key in your request header.
• If you are unsure whether your API key is correct, you can generate a new one. Make sure to replace your old API key in your codebase and follow our best practices guide.

• You have left or been removed from your previous organization.
• Your organization has been deleted.

To resolve this error, please follow these steps:

• If you have left or been removed from your previous organization, you can either request a new organization or get invited to an existing one.
• To request a new organization, reach out to us via help.openai.com
• Existing organization owners can invite you to join their organization via the Members Panel.

• You are using a loop or a script that makes frequent or concurrent requests.
• You are sharing your API key with other users or applications.
• You are using a free plan that has a low rate limit.

To resolve this error, please follow these steps:

• Pace your requests and avoid making unnecessary or redundant calls.
• If you are using a loop or a script, make sure to implement a backoff mechanism or a retry logic that respects the rate limit and the response headers. You can read more about our rate limiting policy and best practices in our rate limit guide.
• If you are sharing your organization with other users, note that limits are applied per organization and not per user. It is worth checking on the usage of the rest of your team as this will contribute to the limit.
• If you are using a free or low-tier plan, consider upgrading to a pay-as-you-go plan that offers a higher rate limit. You can compare the restrictions of each plan in our rate limit guide.

• You are using a high-volume or complex service that consumes a lot of credits or tokens.
• Your limit is set too low for your organization’s usage.

To resolve this error, please follow these steps:

• Check your current quota in your account settings. You can see how many tokens your requests have consumed in the usage section of your account.
• If you are using a free plan, consider upgrading to a pay-as-you-go plan that offers a higher quota.
• If you need a quota increase, you can apply for one and provide relevant details on expected usage. We will review your request and get back to you in ~7-10 business days.

• There is a sudden spike or surge in demand for our services.
• There is scheduled or unscheduled maintenance or update on our servers.
• There is an unexpected or unavoidable outage or incident on our servers.

To resolve this error, please follow these steps:

• Retry your request after a brief wait. We recommend using an exponential backoff strategy or a retry logic that respects the response headers and the rate limit. You can read more about our rate limit best practices.
• Check our status page for any updates or announcements regarding our services and servers.
• If you are still getting this error after a reasonable amount of time, please contact us for further assistance. We apologize for any inconvenience and appreciate your patience and understanding.

We apologize for any inconvenience and we are working hard to resolve any issues as soon as possible. You can check our system status page for more information.

If you encounter an APIError, please try the following steps:

• Wait a few seconds and retry your request. Sometimes, the issue may be resolved quickly and your request may succeed on the second attempt.
• Check our status page for any ongoing incidents or maintenance that may affect our services. If there is an active incident, please follow the updates and wait until it is resolved before retrying your request.
• If the issue persists, check out our Persistent errors next steps section.

Our support team will investigate the issue and get back to you as soon as possible. Note that our support queue times may be long due to high demand. You can also post in our Community Forum but be sure to omit any sensitive information.

If you encounter a Timeout error, please try the following steps:

• Wait a few seconds and retry your request. Sometimes, the network congestion or the load on our services may be reduced and your request may succeed on the second attempt.
• Check your network settings and make sure you have a stable and fast internet connection. You may need to switch to a different network, use a wired connection, or reduce the number of devices or applications using your bandwidth.
• If the issue persists, check out our persistent errors next steps section.

We impose rate limits to ensure fair and efficient use of our resources and to prevent abuse or overload of our services.

If you encounter a RateLimitError, please try the following steps:

• Send fewer tokens or requests or slow down. You may need to reduce the frequency or volume of your requests, batch your tokens, or implement exponential backoff. You can read our Rate limit guide for more details.
• Wait until your rate limit resets (one minute) and retry your request. The error message should give you a sense of your usage rate and permitted usage.
• You can also check your API usage statistics from your account dashboard.

If you encounter an APIConnectionError, please try the following steps:

• Check your network settings and make sure you have a stable and fast internet connection. You may need to switch to a different network, use a wired connection, or reduce the number of devices or applications using your bandwidth.
• Check your proxy configuration and make sure it is compatible with our services. You may need to update your proxy settings, use a different proxy, or bypass the proxy altogether.
• Check your SSL certificates and make sure they are valid and up-to-date. You may need to install or renew your certificates, use a different certificate authority, or disable SSL verification.
• Check your firewall rules and make sure they are not blocking or filtering our services. You may need to modify your firewall settings.
• If appropriate, check that your container has the correct permissions to send and receive traffic.
• If the issue persists, check out our persistent errors next steps section.

An InvalidRequestError indicates that your request was malformed or missing some required parameters, such as a token or an input. This could be due to a typo, a formatting error, or a logic error in your code.

If you encounter an InvalidRequestError, please try the following steps:

• Read the error message carefully and identify the specific error made. The error message should advise you on what parameter was invalid or missing, and what value or format was expected.
• Check the API Reference for the specific API method you were calling and make sure you are sending valid and complete parameters. You may need to review the parameter names, types, values, and formats, and ensure they match the documentation.
• Check the encoding, format, or size of your request data and make sure they are compatible with our services. You may need to encode your data in UTF-8, format your data in JSON, or compress your data if it is too large.
• Test your request using a tool like Postman or curl and make sure it works as expected. You may need to debug your code and fix any errors or inconsistencies in your request logic.
• If the issue persists, check out our persistent errors next steps section.

If you encounter an AuthenticationError, please try the following steps:

• Check your API key or token and make sure it is correct and active. You may need to generate a new key from the API Key dashboard, ensure there are no extra spaces or characters, or use a different key or token if you have multiple ones.
• Ensure that you have followed the correct formatting.

We apologize for any inconvenience and we are working hard to restore our services as soon as possible.

If you encounter a ServiceUnavailableError, please try the following steps:

• Wait a few minutes and retry your request. Sometimes, the issue may be resolved quickly and your request may succeed on the next attempt.
• Check our status page for any ongoing incidents or maintenance that may affect our services. If there is an active incident, please follow the updates and wait until it is resolved before retrying your request.
• If the issue persists, check out our persistent errors next steps section.