---
title: "Delete an invite"
method: DELETE
path: "/admin/invites/{invite_id}"
tags: ["Invites"]
---

# Delete an invite

`DELETE /admin/invites/{invite_id}`

Delete a pending or expired invite and its role bindings; to remove an accepted user, delete the user instead.

## Path parameters

- `invite_id` string, uuid, required

## Headers

- `X-Pinecone-Api-Version` string, required

## Response `202`

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.

## Other responses

- `401` — Unauthorized. Possible causes: Invalid API key.
- `403` — Forbidden
- `404` — Not found
- `409` — Conflict. The request conflicts with the persisted state of the resource. Common causes include invariant violations (e.g., removing the last `OrgOwner`), lifecycle-state mismatches (e.g., resending an invite that is not pending), and constraint violations checked against persisted data.
- `500` — Internal server error.
- `4XX` — Unexpected error on request.

---

[API](https://skmtc.dev/pinecone/apis/pinecone-admin-api.md) · [All operations](https://skmtc.dev/pinecone/apis/pinecone-admin-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/pinecone/pinecone-admin-api/revisions/8210e9d414c2/schema)