Errors

Pinecone uses conventional HTTP response codes to indicate the success or failure of an API request. In general, codes in the 2xx range indicate success, codes in the 4xx range indicate an error that failed given the information provided, and codes in the 5xx range indicate an error with Pinecone's servers.

For guidance on handling errors in production, see Error handling.

The request succeeded.

The request succeeded and a new resource was created.

The request succeeded, but there is no content to return.

The request failed due to an invalid argument.

The request failed due to a missing or invalid API key.

The request failed due to delinquent payment or account deactivation for non-payment. See Account deactivation for non-payment.

The request failed due to an exceeded quota or index deletion protection.

The request failed because the resource was not found.

The request failed because the resource already exists.

The request failed due to preconditions not being met.

The request failed because the server was unable to process the contained instructions.

The request was rate-limited. Implement retry logic with exponential backoff to handle this error.

An internal server error occurred. Implement retry logic with exponential backoff to handle transient errors.

The API gateway received an invalid response from a backend service. This is typically a temporary error. Implement retry logic with exponential backoff to handle transient errors.

The server is currently unavailable. Implement retry logic with exponential backoff to handle transient errors.

The API gateway did not receive a timely response from the backend server. This can occur due to slow requests or backend processing delays. Implement retry logic with exponential backoff to handle transient errors.