Pinecone 403: quota exceeded or deletion protection blocked you

TL;DR: 403 Forbidden covers two different situations: you exceeded a quota, or deletion protection refused a delete. Read which one before acting; the fixes are opposites. Fix: delete unused resources, request a limit increase from support, or restructure (namespaces instead of indexes). Fix: disable deletion protection on the index first, then delete.

The fix

TL;DR: 403 Forbidden covers two different situations: you exceeded a quota, or deletion protection refused a delete. Read which one before acting; the fixes are opposites. Fix: delete unused resources, request a limit increase from support, or restructure (namespaces instead of indexes). Fix: disable deletion protection on the index first, then delete.

The fix

1. Quota. Project or organization limits on indexes, pods, or usage. Creating beyond the cap 403s. Fix: delete unused resources, request a limit increase from support, or restructure (namespaces instead of indexes).
2. Deletion protection. The index has deletion protection enabled and a delete call was refused. Fix: disable deletion protection on the index first, then delete. This is a safety feature doing its job; do not script around it blindly.
3. Never auto-retry a 403. It is not transient.
4. Never disable deletion protection as a drive-by step in a cleanup script. That flag exists so a script cannot nuke production. Require explicit human confirmation naming the index.
5. After any quota fix, verify with list_indexes or the relevant describe call before re-running the original operation.

When to use this

• This covers exactly what the title says: Pinecone 403.
• You are setting this up for the first time, or auditing an existing setup.
• You want the key gotchas in one place before you start.

When not to use this

• You are doing a different workflow with Pinecone; these steps are specific to the title above.
• You need the full reference docs; this is the short path, not the manual.

Compatibility

• Not pinned to a specific version; follows current Pinecone behavior.

Pinecone's error-handling guide defines 403 as quota exceeded or deletion protection hit. Verified against live docs 2026-09-26.