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, revoking the acceptance link. Returns 202; the invite is then no longer returned by get requests (returns 404).
Deleting an already-accepted (processed) invite returns 409; the underlying user is unaffected. To remove an accepted user, use DELETE /admin/users/{user_id} instead. Deleting an invite that does not exist in your organization returns 404.
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.
Was this page helpful?
⌘I