PINECONE_ACCESS_TOKEN="YOUR_ACCESS_TOKEN"
PINECONE_INVITE_ID="YOUR_INVITE_ID"
curl -X DELETE "https://api.pinecone.io/admin/invites/$PINECONE_INVITE_ID" \
-H "X-Pinecone-Api-Version: 2026-04" \
-H "Authorization: Bearer $PINECONE_ACCESS_TOKEN"
Invites
Delete an invite
Delete a pending or expired invite and its role bindings; to remove an accepted user, delete the user instead.
DELETE
/
admin
/
invites
/
{invite_id}
PINECONE_ACCESS_TOKEN="YOUR_ACCESS_TOKEN"
PINECONE_INVITE_ID="YOUR_INVITE_ID"
curl -X DELETE "https://api.pinecone.io/admin/invites/$PINECONE_INVITE_ID" \
-H "X-Pinecone-Api-Version: 2026-04" \
-H "Authorization: Bearer $PINECONE_ACCESS_TOKEN"
PINECONE_ACCESS_TOKEN="YOUR_ACCESS_TOKEN"
PINECONE_INVITE_ID="YOUR_INVITE_ID"
curl -X DELETE "https://api.pinecone.io/admin/invites/$PINECONE_INVITE_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
Invite ID
Response
Invite deletion request accepted. The invite and its role bindings are removed immediately; the invite then returns 404, and repeating the request returns 404 as well.
Was this page helpful?
⌘I