PINECONE_ACCESS_TOKEN="YOUR_ACCESS_TOKEN"
PINECONE_USER_ID="YOUR_USER_ID"
curl -X DELETE "https://api.pinecone.io/admin/users/$PINECONE_USER_ID" \
-H "X-Pinecone-Api-Version: 2026-04" \
-H "Authorization: Bearer $PINECONE_ACCESS_TOKEN"
Users
Remove a user from the organization
Remove a user from the organization and revoke their role bindings; their Pinecone account is not deleted.
DELETE
/
admin
/
users
/
{user_id}
PINECONE_ACCESS_TOKEN="YOUR_ACCESS_TOKEN"
PINECONE_USER_ID="YOUR_USER_ID"
curl -X DELETE "https://api.pinecone.io/admin/users/$PINECONE_USER_ID" \
-H "X-Pinecone-Api-Version: 2026-04" \
-H "Authorization: Bearer $PINECONE_ACCESS_TOKEN"
PINECONE_ACCESS_TOKEN="YOUR_ACCESS_TOKEN"
PINECONE_USER_ID="YOUR_USER_ID"
curl -X DELETE "https://api.pinecone.io/admin/users/$PINECONE_USER_ID" \
-H "X-Pinecone-Api-Version: 2026-04" \
-H "Authorization: Bearer $PINECONE_ACCESS_TOKEN"
Authorizations
An access token must be provided in the Authorization header using the Bearer scheme.
Headers
Required date-based version header
Path Parameters
User ID
Response
User removal request accepted. The user's role bindings are revoked immediately; the user then returns 404, and repeating the request returns 404 as well.
Was this page helpful?
⌘I