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. Does not delete the user’s Pinecone account.
Returns 202. The user’s role bindings are revoked immediately, so the user no longer appears in get or list requests and instead returns 404. A repeat request for the same user returns 404.
Returns 409 when removing the last OrgOwner in the organization.
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.
Was this page helpful?
⌘I