Delete vectors

For guidance and examples, see Delete data.

# To get the unique host for an index,
# see https://docs.pinecone.io/guides/manage-data/target-an-index
PINECONE_API_KEY="YOUR_API_KEY"
INDEX_HOST="INDEX_HOST"

curl "https://$INDEX_HOST/vectors/delete" \
  -H "Api-Key: $PINECONE_API_KEY" \
  -H "Content-Type: application/json" \
  -H "X-Pinecone-Api-Version: 2025-10" \
  -d '{
    "ids": [
      "id-1", 
      "id-2"
    ],
    "namespace": "example-namespace"
  }
'

{}

POST /vectors/delete

curl --request POST \
  --url https://{index_host}/vectors/delete \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "ids": [
    "id-0",
    "id-1"
  ],
  "deleteAll": false,
  "namespace": "example-namespace",
  "filter": {}
}'

{}

• Authorization (header, string, required) — Bearer authentication header of the form Bearer <token>.

• X-Pinecone-Api-Version (header, string, required) — Required date-based version header

• ids (body, string[]) — Vectors to delete.
• deleteAll (body, boolean) — This indicates that all vectors in the index namespace should be deleted.
• namespace (body, string) — The namespace to delete vectors from, if applicable.
• filter (body, object) — If specified, the metadata filter here will be used to select the vectors to delete. This is mutually exclusive with specifying ids to delete in the ids param or using delete_all=True. See Delete data.

• 200 — A successful response.
• 400 — Bad request. The request body included invalid request parameters.
• 4XX — An unexpected error response.
• 5XX — An unexpected error response.